Ask how a comparable purchase is made and which roles need to resolve questions before approval. Build the proposal around that decision process, including scope, implementation and review requirements. Work with your contact to coordinate the next step rather than assuming enthusiasm is purchasing authority.
Learn the process from a recent purchase
A job title rarely tells you the full authority of a prospective customer. A department head might control a small budget but need approval for a recurring contract. Ask how the organisation bought a similar service, which steps were involved and what made the decision difficult. Use that account to form a working map rather than assuming your purchase will follow exactly the same route.
Distinguish known requirements from anticipated ones. Your contact may know the budget owner while being unsure whether a technical review is necessary. Write down that uncertainty and agree how to resolve it. A proposal sent before these questions are understood can be well written yet unusable by the people who must approve it.
Identify questions by role
The user may care about task effort, the manager about team adoption and finance about total cost. Technical, security or procurement reviewers may need evidence about integration, access or supplier arrangements. Some purchases involve only two roles; others involve several people performing overlapping functions. Avoid imposing a complicated committee model where the actual process is simple.
For each relevant role, note the question they need answered, the evidence available and who can provide it. Do not promise a certification, integration or contractual term merely to keep the deal moving. An unresolved requirement should remain visible until someone competent has assessed it. This protects both the customer and the supplier from commitments based on assumptions.
Build a decision pack people can reuse
Keep the central proposal concise: problem, scope, deliverables, customer responsibilities, price, timing and meaningful exclusions. Add supporting material for specific reviewers rather than burying every concern in a long sales document. Consistent facts across these materials matter; different prices or implementation dates create avoidable doubt.
Help your contact explain the offer internally. A clear summary of the intended use and an honest list of open questions can be more useful than promotional claims. Label material that is provisional or illustrative. When a requirement cannot yet be met, describe the gap plainly and discuss whether the purchase should change scope, wait or stop.
Agree a next decision without bypassing your contact
Ask which step would move the decision forward and who should participate. An introduction, shared review or clarification may be more helpful than another revised quotation. Treat your contact as a partner in coordination. Do not imply that they are unimportant because somebody else signs the agreement, or contact colleagues behind their back to accelerate approval.
Track the stage honestly. A successful demonstration, technical acceptance, budget approval and signed contract are distinct events. If progress pauses, identify the unresolved question and whether a useful action is available. Repeated reminders cannot replace missing evidence or create a budget. A respectful pause can be the correct outcome when the organisation is not ready to decide.
Fictional example: a learning platform reaches the review stage
A fictional scenario to explain the method, not a customer result or a market benchmark.
In a fictional sale, a department lead likes a learning platform after a demonstration. The supplier prepares a proposal immediately, assuming the next step is a signature. A planning conversation reveals that procurement needs supplier details, IT needs an access explanation and finance needs a full annual cost including setup.
With the lead's agreement, the supplier prepares one short commercial proposal and separate supporting notes for each reviewer. It marks an integration question as unresolved and proposes a joint review rather than claiming the integration already works. The lead coordinates the meeting because she understands the organisation's process. The sale remains unapproved until those questions are resolved. This invented scenario illustrates a more usable proposal process; it makes no claim that a buying-group map guarantees a contract.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Ask how a comparable purchase was approved.
- Separate known reviewers from roles that still need confirmation.
- Map each reviewer to a question and credible evidence.
- Keep price, scope and dates consistent across documents.
- Agree introductions and next steps with your existing contact.
Common questions.
Should I refuse to send a proposal until every role is known?
Not always. A clearly labelled preliminary scope can help discovery, provided unresolved approval and implementation questions are explicit and it is not presented as a final commitment.
What if the user will not introduce the budget owner?
Respect the boundary. Ask what information would help the user assess the offer internally and whether a realistic next step exists. Do not assume hidden access is necessary or authorised.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse AccelerateLink.
Found an error or a missing qualification? Send an editorial correction.
Find my next move.
Use a practical tool to turn this idea into a clearer starting point.
Find my next move