A proposal often stalls because the team starts writing before it agrees on what the buyer is trying to decide. A complete CRM record should help the next person continue the conversation without making the buyer repeat everything. It should also expose unanswered questions before the team prices a solution.
Record the problem in the buyer's terms
Capture the present situation, desired outcome, business effect, and reason for acting now. Separate a direct statement from a salesperson's interpretation. “The operations lead reported a three-day reporting delay” is stronger than “They urgently need our automation.” The second sentence adds an unverified solution and urgency.
Document which facts were confirmed, which were estimated, and which still need evidence. A discovery note is useful when another team member can understand both the opportunity and its uncertainty.
Make scope assumptions visible
Before pricing, list the locations, users, records, integrations, deliverables, and responsibilities that affect the work. Mark anything the buyer has not confirmed. If the proposal depends on clean source data or internal staff time, state that dependency rather than leaving it inside the delivery team's assumptions.
In a fictional reporting project, discovery confirms one department but leaves three possible data sources unresolved. A proposal for a fixed implementation scope should explain how those sources will be verified, what is included, and how added work would be handled. An attractive price does not resolve an undefined input.
Map the decision process
Record who uses the solution, who evaluates it, who controls budget, and who signs. These roles may belong to different people. Ask about procurement, security, legal review, and timing where relevant. Avoid treating access to a friendly contact as proof that the purchase process is understood.
Include the buyer's comparison criteria. If the buyer is deciding between improving an internal process and hiring an outside firm, a feature-heavy proposal may miss the real decision. Explain the tradeoffs the buyer actually raised.
Finish with an owned next step
The handoff should name the next action, person responsible, due date, and intended output. “Send proposal” is incomplete if nobody knows who will review it or what question that review should answer. Confirm the next step with the buyer through the normal sales conversation.
Salesforce's discovery-call guidance describes discovery as understanding fit and motivation and emphasizes setting the next step. The packet below is an editorial workflow for preserving that context as an opportunity moves between people.
Use a readiness gate
Before drafting, ask the proposal owner to summarize the buyer's problem, proposed scope, decision path, and open questions. If the owner cannot explain those from the record, return for a focused clarification. That small pause can prevent a lengthy document that answers the wrong question.
Explore the episode library for related sales discussions. This guide is a practical resource, not an episode transcript or a claim about a particular guest's advice.
Download the working checklist
Download the sales handoffs: what to record before writing a proposal worksheet (CSV). Fill it with verified information; blank cells identify work still to be done.