How to get access to the economic buyer
Make the introduction useful to the buyer. Start with a problem the customer has confirmed, ask your contact to help prepare the investment discussion, and test who can approve or reject the purchase. A senior title or a forwarded proposal does not establish authority.
A practical way to approach it
Give the meeting a purpose
Use the confirmed problem to explain which investment decision needs discussing. Ask your contact what would make that conversation worth the buyer’s time.
Prepare the introduction together
Keep your contact involved. Agree the problem, the open questions and who should join. A promise to introduce you is useful evidence of support; it is not a booked meeting.
Test authority on this purchase
Ask about approval scope and who could still reject the spending decision. When authority is established, move to the buyer’s criteria instead of repeating the access question.
Meet the fictional deal.
Acme is evaluating software to reduce approval delays. Julien has confirmed the problem and measured lost time. You are preparing a proposal, but nobody has confirmed who can authorize the purchase.
Software purchase · Multiple stakeholders. The declared context guides method selection; it does not prove any part of the buying decision.
- Julien
- Operations lead
- Owns the daily problem. His role does not prove buying authority or internal influence.
- Maya
- Finance lead
- A fictional participant. Her title alone does not prove that she can approve this purchase.
- You
- Software seller
- Preparing a proposal. You choose what to ask and send.
See what changes the strategy.
Fictional deal. These states are calculated with the same evidence checks and strategy rules as 3xrep. A source match does not independently verify the speaker or the truth of a claim.
The problem and its impact are documented. Buying authority and internal support remain unconfirmed.
Declared stage: proposal. This is the seller’s stage, not proof that the buyer is ready.
- Buying authorityUnknown
- Decision criteriaUnknown
- Internal supportUnknown
- Buyer deadlineAssumed
- Decision processAssumed
- Measured impactSupported
- Buyer problemSupported
Put this strategy to work in your AI chat.
From your deal to your next move.
Fictional Acme deal. Your assistant brings the context; 3xrep builds the strategy.
Uses the notes or connected sources you make available.
View this fictional deal’s context
Acme · proposal · seller-declared stage
“We lose 6 hours per week chasing approvals; the time records confirm those 6 hours.”
Checks the evidence. Finds the gap.
Builds a strategy for this deal.
- Buying authority
- Unknown
- Measured impact
- Supported
- Buyer problem
- Supported
Priority gap: Buying authority
Use the confirmed problem as the reason for an introduction. First test whether the contact will help prepare it; their internal support remains unconfirmed. Propose this validation before sending a proposal.
You said: “We lose 6 hours per week chasing approvals; the time records confirm those 6 hours.” To check whether this merits an investment, who can discuss the spending decision with us?
You review the wording and decide what to send.
All arrows stay visible. No prospect is contacted.
Apply this strategy to your own deal.
Bring your notes or the buyer’s exact words into your assistant. Ask 3xrep to check the evidence, choose a next move and prepare for possible replies. Add the new evidence after your next conversation to review the strategy.
Show the request to copy into your assistant
Help me prepare access to the person who can authorize this purchase. Separate the evidence, assumptions and unknowns. Suggest the next move and what to do if my contact declines the introduction.
Enrollment does not guarantee a selected free-forever place.
The evidence file
- Buying authority Unknown
- No accepted proof for this point.
- Decision criteria Unknown
- No accepted proof for this point.
- Internal support Unknown
- No accepted proof for this point.
- Buyer deadline Assumed
- No accepted proof for this point.
- Decision process Assumed
- No accepted proof for this point.
- Measured impact Supported
“We lose 6 hours per week chasing approvals; the time records confirm those 6 hours.”
- Buyer problem Supported
“Our approval delays are a problem: the team misses customer deadlines.”
Read the fictional source passages
pain
Rep: What problem does your team face? Julien: Our approval delays are a problem: the team misses customer deadlines.
impact
Rep: How have you measured the impact? Julien: We lose 6 hours per week chasing approvals; the time records confirm those 6 hours.
Your next move
Use the confirmed problem as the reason for an introduction. First test whether the contact will help prepare it; their internal support remains unconfirmed. Propose this validation before sending a proposal.
Before the proposal or contract
Priority gap: Buying authority
The follow-up needs a purpose; prepare the invitation now.
Evidence you can use
“We lose 6 hours per week chasing approvals; the time records confirm those 6 hours.”Measured impact
“Our approval delays are a problem: the team misses customer deadlines.”Buyer problem
How you could ask
You said: “We lose 6 hours per week chasing approvals; the time records confirm those 6 hours.” To check whether this merits an investment, who can discuss the spending decision with us?
What would count as progress
Identify who authorizes the spending, test their authority and get an introduction or meeting accepted.
Still missing
- The contact’s internal support is unconfirmed.
If the buyer replies…
Hypothetical replies, not predictions or new evidence. Exploring a reply leaves the evidence file unchanged.
Why these methods appear here
The engine selected MEDDIC + SPIN from the declared buying context and the current objection. Selection and priority are 3xrep rules, not a universal prescription.
The links below show how each open or supported point relates to a method. A method name does not establish a proof.
- Buying authority
- MEDDIC: Economic Buyer · MEDDPICC: Economic Buyer · BANT: Authority · BEBEDC: Decision-makers
- Decision criteria
- MEDDIC: Decision criteria
- Internal support
- MEDDIC: Champion · MEDDPICC: Champion
- Buyer deadline
- BANT: Timeline · BEBEDC: Deadline
- Decision process
- MEDDIC: Decision process · MEDDPICC: Decision process
- Measured impact
- MEDDIC: Metrics · MEDDPICC: Metrics · BEBEDC: Stakes · Cost of inaction: Number
- Buyer problem
- MEDDIC: Identify pain · BANT: Need · BEBEDC: Need
Limits of this next move
- Do not invent a person, number, date or quotation.
- Never send the suggested message automatically.
- Do not just ask for “the decision-maker.” Distinguish the finance owner, user and signatory.
Scenario and calculation provenance
Scenario sources are invented for this public example. The diagnostic, evidence states, gaps and actions are calculated by the product engine. Surrounding explanations and reviewed English translations are editorial.
- engine
6d8b03a442f1bdb351c4ddfffe95c54954dab77033ee313492d6aaaf7761e40f- scenario
e3a249d201ae718076254a611fcd5a818791be82081f0ef467201fe91ada8e6c- output
9f238bb32657d18cecc53712b36e4eaa074554c6c1a83c2e9c62993200464dff- presentation
d03ac294ca71d85b0b72080199b53212f3817ba7682a2954eb62483ab62c69c3- rule
impact-to-access
Where this approach has limits
Buying authority depends on this purchase. Some organizations split budget approval, technical acceptance and signature. The example does not establish a universal buying process or guarantee access.