What Does a Value-Led Forecast Look Like, and Why Doesn't Your Stage-Based Forecast Tell You What You Need to Know?
The stage-based forecast measures whether deals are moving through the process. It does not measure whether the deals that are moving will close, because it cannot see the quality of the business case the deal is built on, whether the economic buyer has validated the financial logic, or whether the discovery motion produced the intelligence that makes the case defensible. A value-led forecast changes the input from pipeline stage to deal quality, and deal quality is a function of the governed discovery motion that produced the case.
Key takeaways
- Stage gates record what the rep did (uploaded a proposal, logged a next step). They don’t record what the buyer decided.
- Two deals at the same pipeline stage can carry completely different risk profiles, and a stage-based system has no way to tell them apart.
- CROs already run an informal value-led forecast in their heads during pipeline review. The system just isn’t capturing the signals they’re already looking for.
- A value-led forecast doesn’t replace the stage gate. It adds a quality dimension built from the governed discovery motion that produced the case.
- The quality signals a value-led forecast needs are a byproduct of how discovery is run, not an extra reporting task for the rep.
Why this matters now
Every CRO has a version of the same frustration. The pipeline review shows the deal at 80%. The CRO looks at it and feels nothing, not confidence, not urgency, just the mild unease of a number that carries no information about what is actually happening in the deal. They have been doing this long enough to know that the 80% deals are the ones that surprise them, the ones that were supposedly moving and then died at procurement, or stalled in the CFO review, or came back to life three months after they were supposed to close.
The stage gate recorded a process transition. The CRO needs a quality signal, and no amount of CRM discipline produces a quality signal from a process compliance system.
What is the stage-based forecast actually measuring?
Process compliance: did the rep complete the activities the methodology requires at each stage? Uploaded the proposal, logged a next step, recorded a decision date. The stage gate is a record of what the rep did, not what the buyer decided. A buyer who attended a demo and then went silent can appear at stage three in a stage-based system if the rep has completed the required activities. A buyer who has engaged deeply with the financial case, validated the ROI argument with their finance team, and briefed the champion on the internal approval path may appear at the same stage.
Those two deals are not in the same position, but the stage-based forecast treats them as if they are. The forecast accuracy problem follows directly: the system that was supposed to tell the CRO which deals will close is giving the same signal to deals that are genuinely progressing and deals at risk of dying without ever generating a warning.
Why does the CRO not believe the stage-based forecast?
The stage-based forecast is built on a foundational assumption: that deals which have completed stage gates are more likely to close than deals that have not. This assumption holds for deals where the stage gates capture something real about buyer commitment. It breaks down when stage gates are defined by seller activity rather than buyer behaviour, when moving from stage three to stage four requires the rep to upload a proposal and log a next step rather than demonstrate that the economic buyer has engaged with the financial logic of the case.
The CRO who has been doing pipeline reviews long enough has built an internal model of which stage-three deals will close and which will not, and that model isn’t based on the stage. It’s based on a set of quality indicators the CRO has learned to look for: whether the economic buyer has been in a meaningful conversation, whether the business case makes sense, whether the champion can defend the financial argument without the rep in the room. The CRO is already running a rough value-led forecast in their head, and they don’t trust the stage-based system because it isn’t measuring what they know matters.
What is the stage-based forecast actually measuring?
Process compliance: did the rep complete the activities the methodology requires at each stage? Uploaded the proposal, logged a next step, recorded a decision date. The stage gate is a record of what the rep did, not what the buyer decided. A buyer who attended a demo and then went silent can appear at stage three in a stage-based system if the rep has completed the required activities. A buyer who has engaged deeply with the financial case, validated the ROI argument with their finance team, and briefed the champion on the internal approval path may appear at the same stage.
Those two deals are not in the same position, but the stage-based forecast treats them as if they are. The forecast accuracy problem follows directly: the system that was supposed to tell the CRO which deals will close is giving the same signal to deals that are genuinely progressing and deals at risk of dying without ever generating a warning.
What would a value-led forecast measure instead?
Deal quality indicators drawn from the governed discovery motion. Not whether the rep uploaded a proposal, but whether the value case exists and what quality it is. Whether the business case was built from discovered intelligence or assembled from benchmarks. Whether the economic buyer has engaged with the narrative and numbers in a way that indicates they own the financial logic rather than passively receiving it. Whether the champion can defend the financial argument independently of the vendor’s presence, the real test of whether the case has been co-constructed rather than presented.
A value-led forecast does not replace the stage gate. It adds a quality dimension the stage gate cannot produce. The deal at stage three with a validated, economic-buyer-owned value case is a different forecast entry from the deal at stage three with a rep-assembled case the champion hasn’t read, and a CRO who can see that distinction in the pipeline review is working from a different quality of information than one who sees two identical stage-three entries.
What does a forecast you actually believe look like, and what does it require upstream?
A forecast the CRO believes is one where the quality indicators are generated by the deal motion itself, rather than inferred from stage compliance. The governed discovery motion that captures, structures, and preserves the intelligence from buyer conversations produces a deal record containing quality signals: the first version of the business case, built from validated discovery intelligence; the economic buyer’s engagement with the financial logic; the champion’s demonstrated capacity to carry the argument internally. Those signals sit in the deal record because the governed motion put them there, not because a rep was asked to assess deal quality subjectively in a pipeline review field.
What this requires upstream is a discovery motion designed to produce quality signals as a byproduct of its execution. The rep who runs a governed discovery process doesn’t file an additional quality report. The quality evidence is in the case they built, the buyer interactions they captured, and the progression of the economic buyer’s engagement with the financial argument. The forecast is a read of that record, not an assessment of the rep’s confidence.
Frequently Asked Questions
Why do CROs not trust stage-based sales forecasts?
Stage-based forecasts measure seller activity rather than buyer commitment. The stage gate records that the rep completed required activities at each phase; it doesn’t record whether the economic buyer has engaged with the financial logic, whether the champion can defend the case without the vendor present, or whether discovery produced validated intelligence rather than assembled assumptions. The CRO’s internal model of which deals will close is already tracking those signals. The stage-based system isn’t.
What is a value-led forecast and how is it different from a pipeline stage forecast?
A value-led forecast uses deal quality indicators drawn from the governed discovery motion as its primary input, rather than pipeline stage. Those indicators include whether the business case was built from validated discovery intelligence, whether the economic buyer engaged with the narrative and numbers, and whether the case was co-constructed with the buyer rather than presented to them. The result is a forecast where two deals at the same pipeline stage can carry different quality signals instead of appearing identical.
What does deal quality mean in the context of a sales forecast?
Deal quality is the degree to which the business case was built from validated discovery intelligence and co-owned by the economic buyer, rather than assembled from vendor benchmarks and assumed pain points. It’s the variable a stage-based forecast can’t see, because stage gates track process completion, not the substance of what was built and validated along the way.
Can a stage-based CRM be adapted to capture value-led forecast signals?
Stage-based CRMs can be extended with custom fields attempting to capture quality indicators, economic buyer engagement, business case completion, champion readiness, but those fields are only as good as the discipline behind them, which depends on the rep’s self-assessment rather than the deal record’s evidence. A value-led forecast draws its signal from the deal record the governed discovery motion produces, not from the rep’s assessment of their own deal, and the CRO already knows which of those they trust.
What would a value-led forecast require from the sales team?
The governed discovery motion that produces the deal record’s quality signals doesn’t require additional reporting from the rep. The quality evidence is a byproduct of how the rep runs discovery, whether the business case was built from captured, structured intelligence, whether the economic buyer’s engagement is in the record, whether the first version of the case was refined with the champion rather than delivered to them. A discovery motion designed to produce those signals generates the forecast inputs as part of its normal execution, not as a separate administrative task.
If the forecast you are building from does not tell you which deals have a validated, economic-buyer-owned value case and which have a rep-assembled one on a BVE’s laptop, the forecast is missing the variable that most predicts procurement-stage outcomes. See what a value-led forecast methodology looks like in practice, and what the governed discovery motion needs to produce to make it possible.
