Quick answer: A business case the economic buyer receives from a seller is a vendor claim. A business case the economic buyer helped construct is their own analysis. Most revenue teams are presenting claims and wondering why deals keep stalling at the executive review. The fix is not more MEDDICC training. It's changing who builds the value story.
Why do well-qualified deals keep stalling at the executive review?
Your reps have MEDDICC. They qualify deals rigorously. They identify the economic buyer early. They run discovery that maps pain to value drivers.
And deals still stall at the executive review.
Not because the product isn't worth the price. Not because the champion isn't engaged. But because when the economic buyer asks for the business case -- the one your AE spent a week building -- they treat it with the same skepticism they apply to every other vendor's ROI claim.
The issue is not the framework. It's who built the business case.
Why do seller-built value cases fail at the executive review?
A seller-built business case arrives at the economic buyer as a finished document. Polished. Comprehensive. Professionally formatted.
And fundamentally untrustworthy.
1. Assumptions don't match the buyer's internal model
The AE builds the ROI calculation using industry benchmarks. Generic cost savings numbers. Standard productivity multipliers.
The economic buyer reviews those assumptions and immediately spots gaps. "Our cost structure doesn't look like that." "That productivity number is too high for our environment." The moment an assumption doesn't match their internal view, they discount the entire document.
2. Objections weren't surfaced during construction
When the economic buyer sees the finished business case for the first time in the executive review, they surface objections in real time. The AE isn't in the room. The champion can't answer. The deal stalls while someone schedules a follow-up to address questions that should have been surfaced weeks earlier.
3. The champion can't defend numbers they didn't help create
The champion becomes a messenger, not an advocate. When finance asks follow-up questions about the ROI calculation, the champion forwards them to the AE. They can't defend the case because they didn't participate in building it.
4. Externally-constructed ROI is treated as marketing
Economic buyers review hundreds of vendor business cases every year. They know what seller-built ROI looks like. Even when the math is rigorous and the assumptions are defensible, the economic buyer applies a skepticism discount. "This is what the vendor wants us to believe."
The credibility problem isn't the quality of the analysis. It's the process.
What does this pattern cost?
Deals stalling six weeks at the executive review -- not because the economic buyer rejected the proposal, but because they asked follow-up questions nobody could answer
Discount pressure at the final stage -- the economic buyer won't approve at list price without a business case they trust, so the AE discounts to close before quarter-end
Sales cycles lengthening quarter over quarter -- executive review loops adding 4 to 6 weeks of back-and-forth
Champions losing credibility internally -- when the champion can't answer basic questions about the assumptions, their internal influence weakens
None of this happens because the product doesn't deliver value. It happens because the value case was built without the people who have to approve it.
What is co-creation and how does it fix the executive review problem?
Co-creation means the champion and economic buyer participate in building the value story, not just receiving it. This is not a relationship technique. It's a process discipline.
The AE generates a credible starting point. They bring it to a joint discovery session with the champion. They walk through the assumptions together: "Does this cost savings number match your internal cost structure?" "Is this productivity benchmark realistic for your team?" "What would you adjust?"
The champion validates what's accurate. The economic buyer flags what doesn't match their view. The AE updates the model based on their input. The final business case reflects the buyer's assumptions, not the seller's estimates.
Here's what changes:
Assumptions get validated before the executive review. The economic buyer spots mismatches during construction. By the time it reaches the executive review, the assumptions have already survived scrutiny.
Objections surface when the AE is still in the room. Concerns raised during the collaborative build process get addressed immediately. No surprise objections six weeks later.
The champion can defend numbers they helped create. They co-authored the case. When finance asks follow-up questions, they can answer confidently.
The economic buyer treats it as their own analysis. They didn't receive a vendor's ROI claim. They constructed a business case using their own assumptions. It's not marketing anymore. It's their own internal justification.
Where does co-creation break down?
Co-creation works when the AE walks in with a credible starting point.
Not a blank template. Not a generic calculator. A draft value case built from the buyer's industry, company size, and stated pain -- rigorous enough to invite serious engagement, specific enough to validate, open enough to absorb the buyer's input.
Without something to validate and refine, the joint discovery session is just another stakeholder interview.
Building a credible business case manually takes 3 to 5 days. At deal velocity with five active deals, three of which need business cases, that's not realistic. By the time the first one is ready for a joint session, the other two have already moved to the executive review without it.
This is the infrastructure gap. Co-creation as a process discipline requires infrastructure that produces a credible starting point in minutes, not days.
How does valueIQ make co-creation possible at deal speed?
The AE pastes in deal context: company name, deal size, industry, use case. The value case engine produces a cited, structured value case in minutes. Industry-benchmarked assumptions. Quantified value drivers. Risk-adjusted ROI. Payback period calculations.
The AE brings the draft to a joint discovery session. The champion validates operational assumptions. The economic buyer validates financial assumptions. The AE updates the model based on their input. The final case reflects the buyer's expertise, not just the seller's estimates.
Steven Forth, one of our co-founders and a recognised expert in B2B pricing strategy, wrote about this methodology in his Ibbaka article: ["Jointly Creating Value Stories with the Economic Buyer and Sales Champion: Making MEDDICC Even More Powerful."] The methodology describes how value stories should be built. valueIQ is the layer that makes it executable on every deal -- not just the ones where the AE has three weeks to prepare.
Seller-built vs. co-created value stories
Dimension | Seller-built value story | Co-created value story |
|---|---|---|
Who builds it | AE alone or with enablement support | AE, champion, and economic buyer collaborate |
Assumptions | Industry benchmarks and vendor estimates | Buyer-validated numbers and internal cost structure |
When objections surface | Executive review, 6 weeks later | Joint discovery session, during construction |
Champion's role | Messenger delivering vendor's case | Co-author who helped build and can defend it |
Economic buyer's view | Vendor marketing claim to be discounted | Their own analysis using their assumptions |
Typical outcome | Stalls at executive review or requires discount | Advances through approval or surfaces misalignment early |
Time to build | 3 to 5 days manually | Starting point in minutes, refined in one session |
Deal velocity impact | Adds 4 to 6 weeks to sales cycle | Compresses cycle by surfacing issues earlier |
valueIQ as the infrastructure response
The starting point is what valueIQ generates.
An AE pastes in deal context: company name, deal size, industry, use case. The value case engine produces a cited, structured value case in minutes. Industry-benchmarked assumptions. Quantified value drivers. Risk-adjusted ROI. Payback period calculations.
The output is built to survive economic buyer scrutiny because it's grounded in proprietary value methodology, not AI-generated guesses or generic templates.
This is what makes co-creation possible at deal speed.
The AE brings the draft to a joint discovery session. The champion validates operational assumptions. The economic buyer validates financial assumptions. The AE updates the model based on their input. The final case reflects the buyer's expertise, not just the seller's estimates.
The process was always designed to work this way. The methodology has been refined over 15 years and 100+ B2B SaaS pricing engagements: connecting value drivers to quantified outcomes, citing assumptions, and adjusting for risk.
What's new is the infrastructure to support it.
Steven Forth, one of our co-founders and a recognised expert in B2B pricing strategy, wrote about this exact approach in his Ibbaka article: "Jointly Creating Value Stories with the Economic Buyer and Sales Champion: Making MEDDICC Even More Powerful."
The methodology describes how value stories should be built. valueIQ is the layer that makes it executable on every deal, not just the ones where the AE has three weeks to prepare.
FAQ: Co-creation, economic buyers, and value cases
Q: What is an economic buyer in B2B sales?
The economic buyer is the person who can approve the purchase budget unilaterally. In MEDDICC, this is the "E" -- the individual with final financial authority over the deal. They are often a CFO, CRO, COO, VP, or Division Head, depending on the company size and deal scope. The economic buyer is typically not the day-to-day champion. They enter the deal late, review the business case, and either approve, stall, or kill it.
Q: Does co-creation mean AEs need to schedule more meetings with economic buyers?
Not necessarily. The joint discovery session can be a single 30-minute working call. Many AEs already have champion calls and economic buyer check-ins on their calendar. This is about changing what happens in those conversations: bringing a draft value case to validate instead of asking discovery questions without a model to build on.
Q: What if the economic buyer won't engage until they see a finished business case?
Start with the champion. Run the joint discovery session with them first. Use their input to refine the model. Send the updated case to the economic buyer with a note: "This reflects [Champion Name]'s input on cost structure and timeline. I'd value 15 minutes to validate the financial assumptions before the executive review." Most economic buyers engage when they see the champion has already participated.
Q: Won't this slow down deals if we're adding a collaborative step?
The opposite. Deals slow down when the executive review surfaces objections nobody anticipated. Co-creation surfaces those objections during construction, when the AE can address them immediately. The collaborative step compresses the sales cycle by eliminating the 4 to 6 week executive review stall loop.
Q: Can this work on smaller deals, or is it only for enterprise?
Co-creation applies to any deal with an economic buyer gate. If the deal requires CFO or finance sign-off, the process is the same. The difference is stakeholder complexity -- smaller deals may only need one iteration with the champion, while enterprise deals may require multiple sessions with procurement, finance, and executive stakeholders.
Q: How do I know if my team has the infrastructure to do this at scale?
Ask: can every AE on your team generate a credible, cited value case from deal context in under 10 minutes? If the answer is no, you have an infrastructure gap. If business case creation requires manual work, spreadsheet builds, or enablement support, co-creation is possible but not scalable.
