A prospect loves the demo, asks for pricing, and says they want to move quickly. Your salesperson puts the deal in the forecast. Two weeks later, you discover that finance has never heard of the project, security needs a review, and the person evaluating your product cannot approve the spend. The enthusiasm was genuine. The path to a signed agreement was still largely unknown.
For an early-stage founder, one useful sales improvement is to require buyer evidence before advancing a deal. Each stage should represent something the buyer has confirmed or completed. That gives you a practical way to combine discovery, qualification, closing, and coaching without introducing a complicated sales process. It also gives CRM automation and AI assistants a clear job: surface supporting evidence, identify missing information, and help the seller prepare the next conversation. Start with the opportunities already expected to close this month.
Evidence
Sales methodologies give teams a shared language for understanding opportunities. You can borrow questions about pain, business impact, approval authority, and buying process from an established framework, then translate them into observable requirements. For example, knowing the name of the budget owner is useful. Having that person confirm the spending criteria gives you stronger grounds to forecast a decision. The important operating choice is deciding which buyer action earns each stage change.
For a small team selling a considered B2B purchase, the following stage requirements are an illustrative starting point. Adjust them to your contract size and buying motion. A straightforward purchase may need one conversation to establish several facts. A purchase involving sensitive data may require a separate technical review. Keep the requirements small enough that sellers can remember them during a call:
- Qualified: The buyer has described a specific problem, its consequences, and a reason to address it now.
- Evaluating: The buyer has agreed on success criteria and who will assess whether your product meets them.
- Approving: The buyer has confirmed the commercial approver, required reviews, and the route to a decision.
- Contracting: Commercial terms are agreed, remaining contract issues have owners, and the signature process is confirmed.
Store the evidence beside the stage: a dated buyer email, a call timestamp, or an agreed evaluation document. Give sellers somewhere to record uncertainty as well. “Finance approval unknown” is useful information that should prompt a question. Review stage changes against these requirements, and allow a deal to move backward when new facts weaken the original qualification. A clean pipeline makes the next action easier to choose.
Discovery
Discovery should produce evidence that the buyer has a problem worth spending money and attention to solve. Start with a recent instance: “Walk me through the last time this happened.” Then ask who did the work, where it slowed down, and what happened as a result. Recent events are easier to examine than broad claims about efficiency. They also expose whether your product addresses the expensive part of the problem or a minor inconvenience beside it.
Consider an illustrative sale of account reconciliation software. The buyer says eight analysts each spend five hours a month preparing reconciliation files. That gives you 40 hours of preparation work to investigate, rather than an automatic savings claim. Ask which steps your product could actually remove, which checks must remain, and whether preparation delays the monthly close. Then ask, “If those hours became available, what work would the team do instead?” The answer helps distinguish a modest productivity benefit from a business priority. Let the buyer validate the inputs before using them in a proposal.
Finish by testing urgency and decision criteria: “What happens if this stays the same through next quarter?” and “What would you need to see to approve a change?” Send a short recap describing the current workflow, the consequence, and the outcome the buyer wants. Ask them to correct it. If the problem remains vague or the buyer has no reason to act, agree on a future trigger and move the opportunity out of the near-term forecast. Your team can then spend its time on buyers with an active decision to make.
Approval
A strong internal supporter can explain the problem and still struggle to get a purchase approved. Help them map the actual route. Ask who owns the budget, who can approve the spend, who can block the purchase, and who signs the agreement. These responsibilities sometimes sit with the same person, but you should confirm that directly. Also establish where the money will come from and whether the purchase fits an existing budget or requires a new request.
Use a specific question to uncover the mechanics: “Think about the last software purchase of roughly this size. What happened between choosing a vendor and getting the agreement signed?” Follow the sequence they describe. If procurement becomes involved after a security review, capture that dependency. If a department head must present the business case at a monthly meeting, learn the submission deadline. You now have something concrete to plan around. A seller-selected close date becomes much more credible once the buyer confirms the steps leading to it.
Equip your supporter for the next approval conversation. For a finance discussion, send a concise business case using buyer-validated assumptions, the proposed cost, and the consequences of waiting. For a security review, send the relevant documentation and offer access to the person who can answer technical questions. Ask, “Would it help to walk through these assumptions together with your finance lead?” When direct access is unavailable, agree on what your supporter will present and how you will learn the result. Record secondhand information as secondhand until the relevant stakeholder confirms it.
Commitment
Every late-stage meeting should end with a buyer-owned action that advances the purchase, paired with the work your team owes them. “Send a proposal” usually describes a seller task. A stronger next step establishes what the buyer will do with that proposal, who will review it, and when the group will discuss the result. For example: “I’ll send the revised scope on Tuesday. Can you review it with your operations lead on Thursday, then join us Friday to resolve any concerns?” Leave room for the buyer to offer a workable alternative.
Build the closing schedule backward from the buyer’s intended start date. In an illustrative deal targeting a December 1 kickoff, you might agree to finish security review by November 13, settle commercial terms by November 18, and complete signature by November 24. Those dates become useful only when the people responsible accept them and the sequence allows enough time for implementation preparation. Keep the shared schedule short: task, owner, due date, dependency, and status. Use it in follow-up conversations so both sides can see what changed.
When a date slips, diagnose the reason before offering a discount. An unanswered legal question needs an answer. A missing budget allocation needs an approval conversation. A buyer whose priorities changed needs space to reconsider the purchase. Ask, “What changed, and what does that mean for the start date we discussed?” Then update the schedule and forecast together. If a concession could genuinely resolve a commercial issue, tie it to an explicit exchange, such as a longer commitment or narrower scope. Confirm that the person requesting it can secure the corresponding agreement.
Coaching
Use deal reviews to inspect the quality of evidence and rehearse the next conversation. Choose one late-stage opportunity and ask the seller to show the buyer’s stated reason to act, the approval path, and the latest agreed action. Look for the gap with the greatest effect on closing. If nobody has confirmed funding, another product walkthrough may add little. If the technical evaluator has raised an unresolved concern, access to the budget owner alone will leave that concern open. Coach the seller toward the conversation that resolves the uncertainty.
CRM assistants can make this preparation faster when they have access to appropriate records. Use approved tools and check the underlying material before changing stages or forecasts. A useful prompt is: “Review this opportunity’s emails, notes, and call transcripts. Extract buyer statements about urgency, funding, approval authority, required reviews, and next actions. Include the speaker, date, and source for each statement. Mark missing information as unknown and flag contradictions. Keep seller assumptions separate from buyer statements.” This produces a review aid that a human can verify, including whether an older statement has been superseded.
Spend the coaching time practicing one question rather than rewriting the entire sales approach. For example, have the seller rehearse: “You mentioned that your CFO approves purchases at this level. What will they need to see, and when can we review that together?” Play the buyer and give a realistic objection, such as limited executive availability. Help the seller respond with a useful alternative. Save the strongest phrasing and relevant approval materials in a shared enablement folder. Over time, the team accumulates examples connected to actual selling situations, with clear guidance on when to use them.
Execution
This week, select five opportunities expected to close soon, or all of them if your pipeline is smaller. Spend 45 minutes reviewing the evidence with the people selling them. For each opportunity, identify the most consequential unanswered question and assign a buyer-facing action to resolve it. Keep the output simple: the question, the seller responsible, and the date of the next conversation. Use this review to correct close dates immediately where the buyer’s process cannot support them.
Next, add a small set of fields to your CRM: reason to act, approval path, next buyer action, action date, and evidence link. Ask sellers to update them after meaningful conversations. Have whoever owns RevOps configure a reminder for overdue actions and a report showing forecasted deals with missing evidence. Introduce stage requirements gradually, starting with the move into approval. You can tighten other transitions once the team has tested whether the requirements reflect how your buyers actually purchase.
At the end of the week, review which unknowns became confirmed facts, which actions happened, and which deals need a different forecast. Keep one 20-minute coaching session focused on the question sellers found hardest to ask. The immediate result should be a clearer allocation of effort: active closing work for buyers progressing toward approval, targeted help for buyers facing a specific obstacle, and follow-up tied to a real trigger for buyers whose timing has changed. That gives you a repeatable way to improve deal execution with the team and opportunities you already have.