"We love your product. But do we really need more of it?"

Every Account Executive running an expansion deal has heard some version of this question. You know your customer is getting value. You know expansion makes sense. But proving it? That's where things get tricky.

The challenge with expansion selling isn't that customers don't see value—it's that they can't see it clearly enough to justify increasing their investment. Future projections feel speculative. Past results feel forgotten or unquantified.

Today, we're introducing Historic Scenarios in Minoa—a new way to build expansion business cases that show both the value you've already delivered and the value that's possible next.

The Problem: Expansion Deals Lack Credibility

Let's be honest about what usually happens in expansion conversations.

Your champion knows things are going well. They've seen the impact. But when it's time to justify a bigger budget to procurement or finance, they're stuck trying to piece together evidence from memory, random emails, and scattered usage reports.

You, the AE, try to help by building a forward-looking business case. "Here's what you could achieve with expanded licenses, additional modules, or broader deployment." The math looks good. The opportunity is real.

But to the CFO reviewing this request, it's just another vendor promising the moon.

The missing piece? Proof of what you've already delivered.

From our research with Value Engineering teams and sales leaders, we kept hearing variations of the same insight:

"Expansion cases are so much easier when you can show both what we've done and what comes next."

"I need to prove ROI on the current contract before I can sell them on more."

"Our customers don't remember the value we delivered 12 months ago unless we put it in front of them."

The most successful expansion sellers weren't just projecting future value—they were anchoring it in demonstrated past results.

A Different Approach: Before and After, in One View

Historic Scenarios changes the expansion conversation by letting you show two stories at once:

The Historic Scenario (What You've Delivered):

Represents the current contract period
Shows value already realized from their existing investment
Uses actual data from what's been delivered
Includes the investment they've already made
Example: "Year 1 - Current Contract"

The Future Scenario (What's Possible Next):

Represents the expansion period
Shows potential value from the expanded scope
Uses projections based on the new deployment or usage
Includes the expansion investment
Example: "Year 2 - Expansion"

Together, these scenarios create a powerful narrative: Here's the ROI we've already proven. Here's what we can do next.

How It Works in Practice

Let's walk through a real expansion scenario.

Your situation: You're an AE at a security compliance platform. Your customer bought 50 licenses a year ago. They're happy, but you want to expand to 150 licenses across more teams.

Without Historic Scenarios:

You build a business case showing the value of 150 licenses over the next year. It projects cost savings of $750K and risk reduction worth another $500K. The numbers are solid, but the CFO's response is skeptical: "How do I know these projections are realistic?"

With Historic Scenarios:

You build two scenarios in the same business case:

Historic Scenario: "Year 1 - Initial Deployment"

50 licenses across legal and compliance teams
Actual time savings: 2,400 hours of manual audit work
Actual cost savings: $180,000 (based on customer survey data)
Investment: $100,000
Proven ROI: 180%

Future Scenario: "Year 2 - Full Deployment"

150 licenses across legal, compliance, IT, and finance
Projected time savings: 9,200 hours (3x more teams, more use cases)
Projected cost savings: $750,000
Expansion investment: $250,000
Projected ROI: 300%

Now when the CFO asks "How do I know these projections are realistic?", you point to the historic scenario. You've already delivered 180% ROI on a smaller deployment. The expansion is using the same methodology, just applied to more teams with more use cases.

The future projection isn't speculative—it's an extension of proven results.

Who This Is For

Account Executives running renewal and expansion deals who need to prove value delivered before asking for more investment.

Customer Success Managers building Quarterly Business Reviews that connect past results to future opportunities.

Value Engineers creating expansion frameworks that balance credibility (past results) with ambition (future potential).

Sales Leaders who want their teams to anchor expansion conversations in proven value, not just projections.

Real Use Cases

Beyond the expansion scenario above, Historic Scenarios work for:

Multi-year contract renewals: Show Year 1 results to justify Years 2-3 pricing and scope.

Upsell to new modules: Demonstrate value from Module A to build the case for adding Module B.

Account expansion across departments: Use results from the pilot team to justify rolling out company-wide.

QBRs that drive expansion: Frame quarterly check-ins as "here's what we've done, here's what's next" conversations.

How to Build Historic and Future Scenarios

Creating historic scenarios works just like building any business case in Minoa, with a few key differences:

1. Create Your Historic Scenario

Start a new business case and designate it as "Historic." This tells Minoa you're documenting value already delivered, not projecting future value.

Choose the use cases that were part of the original contract. Add customer inputs that reflect actual usage and results from that period. If you ran customer surveys during implementation or QBRs, those data points fit perfectly here.

Set the investment to match what the customer actually paid in the initial contract.

2. Create Your Future Scenario

Start a second business case for the same account and designate it as "Future" or "Expansion."

Select use cases relevant to the expansion—these might be the same as the historic scenario (more of what worked) or new ones (additional value drivers from expanded scope).

Input projections based on the expanded deployment. Minoa will help you scale from the historic scenario or use benchmark assumptions.

Set the investment to reflect the expansion cost.

3. View Them Side-by-Side

In your business case workspace, you can now view both scenarios together. Compare the ROI curves, see the value progression, and export both scenarios into a single presentation that tells the complete story.

Your customer sees: "This is what we delivered in Year 1. This is what's possible in Year 2."

The Psychology of Expansion Selling

Here's why this approach works so well:

Reduces perceived risk: Future projections feel risky. Historic results feel safe. Anchoring the expansion in proven results makes the future feel more certain.

Shifts the default: Instead of "Should we expand?", the question becomes "Given these results, why wouldn't we expand?"

Enables champion selling: Your internal champion can now show their leadership concrete proof of value delivered, making it easier for them to advocate for expansion.

Addresses buyer skepticism: CFOs and procurement teams are trained to discount vendor projections. Historic scenarios give them something they can't discount—actual results.

Getting Started

Historic Scenarios is available now for all Minoa customers.

To create your first historic scenario:

Go to Business Cases → New Business Case
Select "Historic Scenario" when prompted for scenario type
Choose use cases that reflect value delivered in the current contract
Add customer inputs based on actual usage and results
Set the investment to match the initial contract value
Generate outputs—you can use historic scenarios standalone or alongside future scenarios

Tips for success:

Run customer surveys to collect actual usage data for historic scenarios (you'll get more credible numbers than estimates)
Create historic scenarios as part of your QBR process, not just when expansion is imminent
Use consistent calculations between historic and future scenarios for easy comparison
Let Value Engineering teams set up historic scenario templates for common expansion patterns

Want a walkthrough? Book a 15-minute session with our team.

What This Changes

Historic Scenarios fundamentally shifts how expansion conversations happen.

Before, expansion cases were all projection—here's what we could deliver if you buy more.

Now, they're evidence-based—here's what we already delivered, and here's how that scales.

The difference matters. Projections require belief. Evidence requires consideration.

And in expansion deals where every dollar is scrutinized, that's the difference between "we'll think about it" and "let's move forward."

Last updated: Jan 30, 2026

The Expansion Playbook Just Got Easier: Introducing Historic Scenarios