Buyer Approval Gaps: A Guide to Deal Risk in Complex B2B Sales

What an approval gap is

A purchase moves through people, reviews and thresholds. An approval gap is any of those steps that the selling team has not confirmed with the person responsible: an approver nobody has met, a review with no date, or a price change that quietly moves the signature to someone else. Gaps are rarely hidden on purpose. They are simply invisible from the conversation you have most often.

Reported is not the same as approved

The single most useful distinction in this guide: when a champion says “finance is fine”, you have confirmed a report, not an approval. The statement is real and worth recording, with its source and date. The approval itself is still unresolved until finance says so, a document shows it, or the champion can describe what finance actually agreed to.

Worked example: one opportunity, two calls

Consider an example opportunity to replace a mid-market company's reporting process, forecast to close this month.

1. Call one (champion, operations lead). She says the CFO “loves the idea” and that IT will need a security review. The rep logs: CFO sentiment reported; security review required, not scheduled.
2. Call two (champion plus IT manager). The IT manager confirms he will run the review and expects it to take two weeks once he receives the questionnaire. The rep updates: security review confirmed as a step, waiting on our questionnaire.
3. Between calls. The rep sent the questionnaire. Nobody has replied. Silence is not completion: the review stays waiting, owned by IT, with a dependency on the questionnaire being read.
4. Contradiction. In call two the champion mentions that purchases above a threshold go to a procurement committee. The proposal is above it. The earlier assumption — CFO signs — is now contradicted, and the approval path changes.

On paper this deal still says “commit, end of month”. In evidence it has one confirmed step, one waiting dependency, one reported sentiment and one newly discovered approval with no date. That is not a lost deal; it is a deal whose close date needs a conversation.

Step-by-step: mapping the approval path

1. List every step the buyer has mentioned: approvers, reviews, committees, thresholds.
2. For each, record who said it, when, and whether it is confirmed, reported, inferred or unresolved.
3. Attribute ownership correctly: which steps are the buyer's to complete and which are yours (for example, sending documentation).
4. Mark dependencies — a review that cannot start until something arrives is waiting, not in progress.
5. Ask the champion to walk through the last comparable purchase, and update the map where it differs.
6. Revisit the map after every conversation, and note what changed and why.

Diagnostic questions

• “Walk me through the last time your team bought something at this price. Who signed?”
• “Has finance seen numbers, or heard about the project?”
• “Does this amount change who needs to approve?”
• “Who reviews security, and what do they need from us to start?”
• “What would make your manager say ‘not this quarter’?”

Common failure modes

• Treating a confident champion's report as the approver's decision.
• Marking a review complete because no objections arrived.
• Logging a buyer task as done when the seller completed their half.
• Keeping the original approval path after a pricing or scope change.
• Forecasting on stage alone, without looking at which approvals are still open.

Evaluating deal-risk tooling

• Does it distinguish confirmed, reported, inferred and unresolved status — and show the source for each?
• Does it attribute statements and tasks to the right side (buyer or seller) and person?
• Does it treat silence as waiting rather than completion?
• Does it surface contradictions between conversations, and between conversations and the CRM?
• Can a manager see why a deal is flagged without trusting an opaque score?
• Do people review and approve record changes and buyer-facing messages?

Related products

• Forecast
• Deal Rooms
• Revenue Intelligence