Forecasting with Gap Selling means placing each deal by the evidence the buyer has given about their problem, the gap and the decision, and ignoring how confident the rep feels. A sales manager does it weekly with each rep, and a revenue leader rolls it up into one number. It takes about an hour a week per team once the stage definitions are written down.
This is the forecasting job in Gap Selling's vocabulary. For the method in context, read the sales methodology guide; for deal risk across methods, the deal risk guide; for the term, What is Gap Selling?.
What forecasting with Gap Selling means
Gap Selling holds that the gap between the buyer's current state and future state is the deal: the wider the gap the buyer has confirmed, the stronger their reason to buy. A forecast built on that idea asks two questions of every deal: how big is the gap, in the buyer's numbers, and how much of it has the buyer confirmed?
The evidence is Buyer Input Data (BID): problem, impact, root cause, future state and success measure, each stated by the buyer (more on our Gap Selling page). A Sales Growth Company (ASG), the company Keenan founded around the method, lists inaccurate forecasting as a direct effect of reps who never uncovered the buyer's motivation to change (A Sales Growth Company).
Stages built on buyer evidence
Most CRM stages record what the seller did: demo given, proposal sent. A Gap Selling forecast records what the buyer has confirmed. A deal moves when the evidence changes. An illustrative stage model:
| Stage | Exit criteria (buyer-confirmed) |
|---|---|
| 1. Problem | The buyer named a problem from your Problem Identification Chart (PIC) in their own words |
| 2. Impact | The buyer gave the cost of the problem in a number and a time period, and agreed the root cause |
| 3. Gap | The buyer described a measurable, dated future state, and said what happens if nothing changes |
| 4. Decision | The buyer mapped who decides, how, by when, and on which criteria |
| 5. Commit | All five forecast conditions below are confirmed |
Write the exit criteria as a bar a second manager would apply the same way. ASG recommends a written Green, Yellow and Red definition per element for this reason (A Sales Growth Company). Even trained experts marking against a written scorecard disagreed on 18% of scores in our call-scoring research, and that was with the standard written down (field guide).
Discovery questions that produce forecastable evidence
A forecast is only as good as the discovery behind it. Each line of Buyer Input Data comes from a question the rep asked and an answer the buyer gave, and the forecast can use it only if the answer is specific enough to write down.
| BID line | A question that gets it | An answer the forecast can use | An answer it cannot |
|---|---|---|---|
| Current state | "Walk me through how a month-end close runs today, step by step." | "Nine days, three people, most of it reconciling two systems by hand." | "It's a bit manual." |
| Problem | "What about that is the part you most want fixed?" | "The reconciliation. It's where the errors come from." | "Everything, really." |
| Impact | "What does that cost you each month, in hours or money?" | "About 60 hours of overtime and one late filing last quarter." | "A lot of time." |
| Root cause | "Why does it still run that way?" | "The two systems were never connected after the acquisition." | "We just haven't gotten around to it." |
| Future state | "If this were fixed, what would month-end look like, and by when?" | "Five days, no overtime, before the audit in September." | "Faster." |
| Success measure | "How would you know, six months on, that it worked?" | "Close days and overtime hours, from the finance dashboard." | "People would be happier." |
The right-hand column is what most reps write in the CRM. It reads like progress and gives the forecast nothing to stand on, so a deal with those answers belongs at the Problem stage, whatever the rep thinks.
Symptom or root cause, and why the forecast cares
A buyer usually opens with a symptom: errors in the reports, deals slipping, staff leaving. Gap Selling asks the rep to go one level down to the root cause before proposing anything. For the forecast, the difference shows up late in the cycle.
A deal sold against a symptom tends to stall at the decision. Finance asks why the problem exists, nobody on the buyer's side can say, and the purchase waits for an internal project to find out. A deal sold against an agreed root cause carries its own answer to that question. So the Impact stage in the table above requires the buyer to agree the root cause as well as the cost. When reviewing a late deal, ask the rep: "If the CFO asked why this problem keeps happening, what would our champion say?" If the rep cannot answer, the deal is at Problem or Impact, and the forecast should say so.
The commit gate: five conditions
ASG's forecast layer, from its book Gap Revenue Performance, gates late-stage deals on five conditions, each confirmed by the buyer (A Sales Growth Company):
| Condition | What the buyer has shown |
|---|---|
| Clarity | They can state the problem, impact and root cause in their own words, unscripted |
| Control | They know how the decision gets made internally and are driving it |
| Consensus | Every stakeholder who touches the decision is engaged and aligned, beyond the champion |
| Commitment | They have acted: budget allocated, people assigned, time blocked |
| Competition | Every alternative is resolved, including building it themselves and doing nothing |
ASG sorts deals by how many conditions hold. Five of five is Commit, three or four is Projected, one or two is Upside, and the number a revenue leader reports is Commit plus Projected. Upside is shown as headroom and never planned against. ASG reports historical close rates of roughly 80% for five conditions, 55% for four, 30% for three and 10% to 15% for one or two (A Sales Growth Company). Use your own history once you have a quarter of it.
The procedure: seven steps
1. Write the stage exit criteria
Use the table above as a start and fit it to your PIC. Good looks like: a one-page standard every manager signs off on.
2. Re-stage every open deal on evidence
Go through the pipeline with each rep and place each deal at the last stage the buyer has confirmed. Say: "Which of these did the buyer tell you, and which did we work out?" Good looks like: some deals moving backwards, with nobody arguing about it.
3. Size the gap
For each deal past Impact, write the gap in one line: current state, future state, cost of the distance. Good looks like: a line the buyer would recognize, for example "close in nine days to five, 60 hours of overtime a month."
4. Test late deals against the five conditions
For every deal the rep calls commit, check each condition. If one fails, the deal does not go into Commit. ASG allows no partial credit and no override for experience (A Sales Growth Company). Good looks like: a Commit list that is shorter than the rep's, with a reason for each deal that left it.
5. Turn each failed condition into coaching
A failed condition routes the deal back a category and becomes that deal's coaching agenda; ASG calls this the Kick-Back Loop. Clarity fails: get the buyer's own statement of the problem. Consensus fails: reach the stakeholders the champion speaks for. Good looks like: one named condition per deal, with the question that would confirm it.
6. Run the weekly rhythm
ASG's cadence is Monday deal scoring, Tuesday aggregation into Commit, Wednesday coaching on deals that lost ground, Thursday the revenue leader's review, Friday the report (A Sales Growth Company). Good looks like: Commit rising week by week, and a flat Commit for two or three weeks treated as a signal to investigate.
7. Look across reps for the same failed condition
When the same condition fails for several reps in a quarter, ASG reads it as a training gap. Good looks like: one team session on that condition, then the next week's scores.
Worked example
This example is illustrative. A manager reviews three deals a rep has marked commit, for a $400,000 quarter target.
| Deal | Value | Rep's call | Conditions confirmed | Category |
|---|---|---|---|---|
| Logistics firm | $120,000 | Commit | All five | Commit |
| Hospital group | $150,000 | Commit | Clarity, Control, Commitment (missing Consensus, Competition) | Projected |
| Retailer | $90,000 | Commit | Competition only | Upside |
The hospital deal: the champion, a director of patient access, has the problem in her own words and a budget line. Nobody has heard from the clinical lead who will run the rollout, and the buyer has not said whether they would extend their current vendor. The retailer: the buyer said "we love it" on the demo and explained why the other two vendors fell short, but gave no number for the problem, and no decision process has been mapped.
The rep's commit of $360,000 becomes a Commit of $120,000, with $150,000 Projected and $90,000 Upside. The manager does not argue about which number is right. The hospital deal goes to Wednesday's coaching call. The retailer goes back to the Problem stage, and the rep's next call asks what the problem costs.
The question to ask for each condition
On a forecast call, each condition comes down to one question the rep should be able to answer with something the buyer said or did.
| Condition | Ask the rep | Evidence that counts | Evidence that does not |
|---|---|---|---|
| Clarity | "What would the buyer say the problem costs, if I called them now?" | A figure and a cause, in the buyer's words | "They know it's a problem" |
| Control | "Walk me through the steps between yes and a signature." | Named steps, owners and dates the buyer gave | "Procurement should be quick" |
| Consensus | "Who else has told us this matters?" | Other stakeholders on calls, confirming the problem | The champion speaking for everyone |
| Commitment | "What has the buyer done, beyond agreeing?" | Budget assigned, a project lead named, time on calendars | Positive feedback on a demo |
| Competition | "What else could they do, including nothing?" | The buyer has said why each alternative falls short | "We're the only vendor in" |
If the rep answers with their own view, ask the question again with "what did the buyer say?" on the front. The answer either changes or it does not, and both tell you where the deal sits.
How a weekly deal check sounds (illustrative)
This exchange is illustrative and continues the hospital deal from the worked example.
Manager: "You have Clarity, Control and Commitment. Tell me about Consensus." Rep: "The director is fully behind it. She's told me the clinical team will be fine." Manager: "Has anyone on the clinical side said that to us?" Rep: "Not directly." Manager: "Then it stays in Projected. What would get the clinical lead on a call?" Rep: "The director mentioned the clinical lead is worried about training time. I could offer a 20-minute call on what the rollout looks like for their staff." Manager: "Good. Say the ask the way you'll put it to the director."
The deal does not move this week. The rep leaves with one ask, the reason the clinical lead would take the call, and a line rehearsed out loud.
Rolling up the number
A revenue leader reports Commit plus Projected, with Upside shown separately. Two habits keep that number honest across teams, on top of checking each category against what closed once a quarter.
First, every manager applies the conditions the same way. A calibration session once a quarter, where managers score the same five or six deals and compare, catches the manager who reads Consensus more generously than the rest.
Second, track movement as well as totals. A deal that moved from Projected to Commit this week should have a new piece of buyer evidence behind it, and the leader can ask what it was. A deal that slid back should have a named condition that failed.
How this differs from a MEDDPICC forecast
A MEDDPICC forecast and a Gap Selling forecast both gate commit on evidence from the buyer. They start from different evidence. MEDDPICC checks the parts of the buying process: metrics, the economic buyer, decision criteria and process, paper process, the pain, the champion and the competition. Gap Selling starts from the size of the gap and whether the buyer has confirmed it, then checks the decision through the five conditions.
In practice the two overlap more than they differ. Clarity covers much of what MEDDPICC calls metrics and pain; Control covers the decision and paper process; Consensus and Competition line up with the champion and competition checks. A team moving from one to the other can keep its forecast categories and rewrite the exit criteria in the new method's words. The MEDDPICC forecasting guide covers the other side.
Renewals and expansion
The same conditions apply to an existing customer, with different evidence. Clarity for a renewal is the customer stating the value they got, in their words. Consensus includes the users, who may have changed since the first sale. Competition includes the customer building the capability in house or cutting the budget line. An expansion deal needs its own gap: a new problem, with its own cost, owned by a team that may never have bought from you.
Where it goes wrong
Stages that record seller activity. "Proposal sent" tells you what the rep did. A deal can sit in that stage for a month with nothing confirmed by the buyer.
Commit as a feeling. If a senior rep can override the conditions, every deal of theirs becomes commit and the forecast inherits their hopes for the quarter.
The gap never written down. A deal with confirmed stakeholders and no quantified impact can look healthy and still stall when finance asks what it is worth.
Scoring with no coaching. A failed condition flagged on Monday and not discussed until the next forecast call is a lost week. ASG puts coaching on Wednesday for this reason.
A risk score with no next step. A red flag tells the rep a deal is at risk without saying which condition failed or what to ask the buyer. Our post a risk score is not a fix covers this gap.
Forecasting every deal
A manager can re-stage a pipeline once a quarter. Doing it every week, deal by deal, is where the method breaks down for teams with more deals than review time.
Keenan, our AI sales expert built on Gap Selling with A Sales Growth Company, finds the gap in each deal from the buyer's evidence, says what it is missing, and is one click away for a call to prepare the next conversation. He scores the discovery against Gap Selling and tells the rep which BID line is missing before the deal goes into the forecast. The rep talks the deal through by voice and leaves with the question for the buyer; typing works when they cannot talk. Managers see the team's missing conditions through Bryce, the manager coach. The Gap Selling page shows how the method runs on the platform, and the Gap Selling deal review covers the weekly review.
To see which BID line one of your commit deals is missing, talk it through with Keenan.
FAQ
How do you forecast with Gap Selling?
Forecast with Gap Selling by staging each deal on Buyer Input Data, sizing the gap in the buyer's numbers, and gating commit on buyer-confirmed conditions. A Sales Growth Company uses five: Clarity, Control, Consensus, Commitment and Competition. Deals that pass all five go in Commit; deals that pass three or four are Projected.
What are the 5 C's in Gap Selling forecasting?
The 5 C's are A Sales Growth Company's forecast conditions: Clarity, Control, Consensus, Commitment and Competition. Each one tests something the buyer has said or done, such as allocating budget or mapping the decision. They come from the company's book Gap Revenue Performance and are applied late in the cycle, after discovery has produced Buyer Input Data.
What is the difference between Commit, Projected and Upside?
In A Sales Growth Company's model, Commit is deals with all five conditions confirmed, Projected is deals with three or four, and Upside is deals with one or two. The forecast a revenue leader reports is Commit plus Projected. Upside is reported as headroom and never counted toward the plan.
How often should a Gap Selling forecast be updated?
A Gap Selling forecast should be updated weekly. A Sales Growth Company recommends a fixed weekly rhythm, from deal scoring on Monday to the report on Friday, with aggregation, coaching and the revenue leader's review in between. A monthly update misses deals that lose a condition mid-month.
Why did a deal drop out of commit?
A deal drops out of commit when one of the buyer-confirmed conditions fails or was never confirmed, for example when only the champion has spoken to you. The failed condition is the coaching agenda: find the question that would confirm it, ask the buyer this week, and restage the deal on their answer.