Build a Business Case for Change Using MEDDICC + Deal Management

Most deals don’t die because your solution is bad.

They die because the buyer can’t defend the change when you’re not in the room.

The team below leadership is excited about features and workflows.
Leadership needs priorities, impact, consequences, risk, and a return they can believe.

That gap is where deals stall.

This post shows how to blend MEDDICC and Deal Management to build a business case that actually gets approved, and then gets signed.

Download the Business Case Template (Free) →

Table of Contents

1. What a business case is really for
2. Why MEDDICC alone is not enough
3. The inputs: what MEDDICC should collect
4. The output: what Deal Management adds
5. How to write the Executive Summary
6. How to write the Current State
7. How to make Cost of Delay real
8. How to build the Financial Justification
9. Portability: the test that predicts approval
10. Download the template

What a business case is really for

A business case is not a spreadsheet exercise.

It’s a decision asset.

It exists for one reason: so an executive sponsor can answer the inevitable internal questions:

What is this?
Do we really need it?
Why now?
What happens if we wait?
What changes in measurable terms?
When can we expect a return?
Why this vendor versus alternatives?
What is the risk?

If the buyer can’t answer those questions cleanly, the default outcome is predictable:

• they expand the evaluation, or
• they do nothing

A business case prevents both.

Why MEDDICC alone is not enough

MEDDICC is great at collecting the raw material:

• metrics
• economic buyer realities
• decision criteria
• decision process
• champion strength
• competition

But most teams stop there.

They treat MEDDICC like a set of fields to complete, then hope the buyer “gets it.”

Deal Management’s view is simple:
data is not a decision. packaging is.

If you don’t package the evidence into a narrative that can travel internally, you didn’t build a business case. You built notes.

The inputs: what MEDDICC should collect

Think of MEDDICC as your evidence-gathering system for the business case. Here’s what each element needs to contribute.

Metrics

You need a baseline and a believable improvement. Without that, ROI is fiction.

Economic Buyer

You need budget reality: budgeted vs unbudgeted, approval thresholds, and what the EB needs to feel safe sponsoring it.

Decision Criteria

You need the buyer’s definition of “good”, and what they will actually use to judge the investment.

Decision Process

You need the steps and the forums where the business case gets debated.

Champion

You need someone willing to carry the narrative upward and fight for it.

Competition

You need the real alternatives, especially status quo, and why “do nothing” is no longer acceptable.

When those inputs are weak, business cases become vague. When they’re strong, business cases become inevitable.

The output: what Deal Management adds

Deal Management adds three things to a business case that MEDDICC doesn’t enforce:

1) Connect the dots

Pain to gain, gain to priorities, priorities to consequences of delay.

2) Make cost of delay explicit

If you don’t quantify the cost of waiting, waiting feels safe.

3) Package it into something portable

A business case, a value pyramid, a one pager, a PRFAQ, something that can travel without you.

That’s the difference between a business case that gets discussed and one that gets approved.

And that’s exactly what your Business Case Template is built to produce.

Download the Business Case Template (Free) →

The template walkthrough

Your template follows the structure leadership expects, and it forces the right thinking:

• Executive Summary
• Current State
• Cost of Delay
• Financial Justification for Change
• One Time Costs (Implementation)
• Total Costs, Cost and ROI

Below is how to write each section using MEDDICC inputs, and Deal Management rules.

Executive Summary

The Executive Summary is not a recap. It’s the forwardable conclusion.

If an executive sponsor copies and pastes one section into an internal email thread, it should be this.

Your template’s example shows the right shape:

• what the business believes today
• what is failing
• what investment enables
• why it matters now
• what success looks like

A strong Executive Summary should answer, in plain language:

• what is broken
• what changes
• why it matters
• what we get
• what decision is required

It should sound like a business decision, not a tool purchase.

Current State

Current State is where most business cases lose credibility.

Because sellers use vague pain statements:

• “manual process”
• “inefficient”
• “people are frustrated”

Executives will not fund adjectives.

They fund baselines, constraints, and measurable consequences.

Your template models the right approach: short bullets, clear claims, and numbers when possible.

Use MEDDICC Metrics and Implicated Pain to write Current State like this:

• what is happening today
• what it costs
• how it impacts results
• what it prevents the business from achieving
• who is affected

Keep it tight. If it takes a paragraph to explain a bullet, you don’t have a bullet yet.

Cost of Delay

This is the section that turns “good idea” into “priority.”

Your template nails the point: delay isn’t neutral. It’s a recurring cost plus growing downside.

When you write Cost of Delay, quantify it in the buyer’s language:

• dollars
• time
• risk exposure
• lost capacity
• missed revenue
• margin leakage
• operational incidents
• reputation damage

Then tie it to a real forcing event:

• board meeting
• renewal
• audit
• peak season
• hiring plan
• product launch
• fiscal year

If you want the buyer to act, you must make waiting more expensive than acting.

Financial Justification for Change

This is where business cases often get rejected, not because the math is wrong, but because it’s not believable.

Two rules keep this clean:

Rule 1: Separate hard costs from soft costs

The template makes this explicit:

• Hard cost is fixed operating expenses (headcount, tools, tech)
• Soft costs are estimates and non guaranteed outcomes (morale, turnover, market share gains, revenue lifts)

Executives accept soft benefits, but they do not fund soft benefits alone.

Rule 2: Derisk the model

A savvy executive will derisk the business case. They would rather approve a believable improvement that clears the bar than a heroic projection that creates political risk.

So your job is not perfection. Your job is agreement.

Directionally accurate, based on the best available data, and aligned across the people who will be asked to defend it.

What to include in this section

• Current hard cost spend
• Future hard cost spend
• Current soft cost spend
• Future soft cost spend
• One time implementation costs
• Total cost
• ROI by year (or by payback period)

If you can’t defend a line item, downgrade it, simplify it, or label it as an assumption.

Portability

This is the test that predicts approval.

Before the decision meeting, your executive sponsor should be able to explain the deal without you in the room:

• what the locked criteria is, and why
• what outcomes it drives
• what it costs to delay
• what success looks like
• what risks exist and how they’re mitigated
• why this vendor versus alternatives

If they can’t do that, the business case is not done. It’s still a draft.

That’s why the best business cases get written, then sent back to the buyer with one simple request:

“Edit this. Make it sound like you.”

When the buyer starts selling internally with your words, you’re winning.

Download the Business Case Template

If you want the exact format I use to build portable business cases (Executive Summary, Current State, Cost of Delay, and Financial Justification), download the template here:

Download the DealDoc Business Case Template (Free) →

Final note

MEDDICC gives you the inputs.
Deal Management gives you the output.

When you blend them, you stop hoping the proposal will do the heavy lifting, and you start engineering a decision that can survive internal scrutiny.

That is what creates predictable approvals, and predictable revenue.

The full method for building business cases that survive internal scrutiny is in my book, Deal Management: The Hidden Reasons Sales Stall and the Evidence-Based System to Win More.