You closed the deal twelve months ago. The business case was tight: reduced setup times, optimized inventory, fewer quality defects. Your champion believed it. The CFO signed off. Everyone shook hands.

Now it's renewal season, and your expansion target is twice the original contract.

Here's the question most sales teams aren't ready for: Can you prove what you promised?

Because here's what happens in most expansion conversations: The AE pulls up the original business case — the one that projected $450K in savings — and the customer's first question is: "Did we actually get that?" And the AE has no idea. The value story that won the deal evaporated the moment the contract was signed. The projections lived in a slide deck that nobody updated. The proof lives in someone's head, or worse, in a spreadsheet that was never maintained.

The best sales teams treat land and expand as chapters in the same story — one where the business case evolves from projection to proof to expansion. When they do it well, that second conversation isn't a pitch. It's a continuation.

Here's what that looks like in practice, told through the lens of a manufacturing deal from first touch to expansion — and the Minoa features that make each step repeatable.

The Land: Building a Business Case That's Designed to Last

Let's say you're selling into a mid-sized manufacturer. Eighty employees on the production floor, six production lines, a plant manager who's been there for twenty years and has seen every vendor promise under the sun.

Your first challenge isn't convincing anyone your product works. It's convincing them you understand their math.

Start with Their Language, Not Yours

Manufacturing buyers think in shifts, not hours. They think in production lines, not licenses. They think in defect rates and changeover times and yield percentages — and they'll tune out the moment you start talking about "efficiency gains" or "productivity improvements" in the abstract.

This is where most value conversations go sideways. A well-meaning AE walks in with a generic ROI calculator and starts talking about "time saved per employee per week." The plant manager checks out. The math isn't wrong — it just doesn't connect to anything that matters to them.

A mature value-selling org. will have templated use cases built around how specific industries actually operate. For manufacturing, that means use cases like:

Reduce Production Setup Time: calculate hours saved × hourly rate × shifts
Minimize Quality Defects: calculate defect reduction × cost per defect × volume
Optimize Inventory Levels: calculate carrying cost reduction across warehouses

Each use case comes with inputs that mirror how a manufacturing buyer actually thinks: number of production lines, shifts per day, average changeover time, defect rate per thousand units. When your AE opens a business case and it already speaks the customer's language, something shifts. The conversation moves from "let me show you our ROI model" to "let's fill in your numbers and see what this looks like." You're building with them.

Let the Conversation Do the Work

Here's something the best AEs know intuitively but most organizations don't systematize: the richest inputs for a business case are already sitting in your call recordings.

When a plant manager says "we lose about two hours per shift on changeovers," that's a data point worth thousands of dollars in annualized savings. When the VP of Operations mentions they scrapped three full batches last quarter due to quality issues, that's a calculation waiting to happen.

The problem is that these golden nuggets get buried in call notes, forgotten between meetings, or lost entirely when an AE moves to a different deal.

Minoa's Input Scout solves this by automatically extracting metrics from call transcripts — identifying when someone mentions downtime, waste, defect rates, or headcount — and pre-populating those values directly into the business case. The AE doesn't have to remember what was said on the third call six weeks ago. Input Scout catches it, surfaces it, and reduces manual data entry to almost nothing.

Help the AE Pick the Right Value Story

Here's a pattern that shows up in almost every value-selling deployment: a company invests months building a comprehensive value framework with fifteen or twenty use cases, launches it at SKO with great fanfare, and three months later discovers that 80% of business cases use the same three use cases.

It's not laziness. It's cognitive overload. An AE juggling thirty deals doesn't have time to study the entire framework and reason through which use cases apply to each deal. They default to what they know.

Minoa's AI-powered use case suggestions change this dynamic entirely. Instead of asking the AE to browse a library and guess, the system analyzes what it already knows about the deal:

Call transcripts mentioning downtime, waste, or quality issues
Account research showing industry-specific pressures
Company context pulled from public filings and their website
Competitive signals from Salesforce and conversation data

For a manufacturer with high changeover times and quality concerns, "Reduce Production Setup Time" and "Minimize Quality Defects" surface immediately — with explanations for why they were recommended.

The Value Engineering team still controls everything behind the scenes. They can add internal notes to each use case — "strong when prospect mentions lean manufacturing initiatives" or "use when competing against [Competitor X]" — that guide the AI's recommendations. Their expertise scales through the system, even when they can't be in the room.

Make the Inputs a Collaboration

There's a fine art to collecting business case inputs from a customer. Ask too many questions and you feel like an auditor. Ask too few and your numbers won't be credible.

The best approach is tiered:

Must-haves: Number of production lines, shifts per day, average changeover time, current defect rate. If someone can't answer these, you're either too early in the conversation or talking to the wrong stakeholder.
Should-gets: Cost per defect, annual maintenance budget, inventory carrying costs, overtime rates. These sharpen the model, but you can use industry benchmarks as starting points and refine later.
Nice-to-learns: Planned capital expenditures, energy costs per production hour, supplier lead time variability. These unlock the most sophisticated value stories, but they require trust and often come through a survey rather than a live conversation.

Minoa's stakeholder surveys make that survey piece seamless. A lightweight questionnaire — maybe eight to ten questions — positioned as a way to "make sure the business case reflects your reality, not our assumptions." Because the survey sits inside the same platform where the business case lives, completed inputs flow directly into the calculations. No manual transfer. No version control nightmares. And response rates climb because it feels purposeful, not bureaucratic.

Don't Just Project — Phase It

A single, monolithic ROI number is easy to dismiss. "$1.2 million in annual savings" sounds great in a slide deck and suspicious in a CFO's office. The question is always: "When? How? In what order?"

Minoa's Value Timeline changes the conversation from "here's a big number" to "here's how this rolls out." For a manufacturing land deal, the phases might look like:

Months 1-3 (Pilot Phase): "Reduce Setup Time" on two production lines, delivering early measurable wins
Months 4-6 (Expansion Phase): "Optimize Inventory Management" with warehouse integration
Months 7-12 (Full Deployment): "Improve Quality Control Efficiency" across the full production floor

Each phase has its own investment, its own expected return, and its own milestone. You can add month-specific notes — "Month 3: First ROI review with plant manager" — that create natural checkpoints throughout the engagement. This matters enormously when you're twelve months out and planning the expansion conversation. Every milestone you hit becomes evidence for the next chapter.

Make Your Champion Dangerous

The AE won't be in the room when the plant manager presents to the CFO. The champion will be. And that champion needs materials they can actually use.

This means two things. First, the calculations need to be transparent — walkable, not hidden behind black-box formulas. "We assumed 50 employees, 2 hours saved per changeover, 3 changeovers per shift, at $35/hour fully loaded." When the CFO pushes on a number, the champion can explain it. They can even adjust it in real time.

Second, the outputs need to match the audience. Minoa's export and sharing options handle this cleanly:

One-page business case export for the CFO's executive review
Slide export for board presentations
PDF export for email sharing with stakeholders who prefer offline review
Full business case view for the plant manager who wants every detail

Minoa's collaboration features take this further. Invite the plant manager as an editor to co-build the inputs. Share with the CFO as a viewer to review the ROI summary. Use threaded comments to discuss assumptions, flag questions, and build consensus before the big meeting. The business case becomes a shared artifact that the buying team owns together.

And with tab visibility controls, you can fine-tune what each audience sees. Hide the detailed calculation tab from executives. Surface the high-level value summary for the CFO. Let the plant manager see everything. Everyone's looking at the same business case, through the lens that matters most to them.

Arm the Deal with Context

Before the first call even happens, Minoa's Account Research auto-populates company context from the prospect's website, industry research showing manufacturing trends, and financial data (for public companies) that reveals their strategic priorities.

The Resources tab gives you a single place to attach everything that supports the deal:

Case studies from similar manufacturers
Product demo videos relevant to their use cases
Implementation guides and onboarding timelines
White papers on manufacturing ROI

And call transcripts attached to the business case create a running context panel — every discovery call, every pain point, every metric mentioned — available to anyone who touches the deal. When an AE inherits a deal mid-cycle, they don't start from zero. The story is all there.

The Expand: From "We Projected" to "We Delivered"

Twelve months later. The original contract is up for renewal, and you're sitting across from the same plant manager — plus the VP of Operations and a sustainability manager who wasn't involved in the first deal.

This is where most expansion conversations fail. The AE has a new pitch deck. New use cases to sell. But zero connection to what happened since the last deal closed.

The best expansion conversations don't start with "here's what else we can do." They start with "here's what we've already done together."

Historic Scenarios: Your Most Powerful Expansion Tool

Imagine opening the expansion meeting by pulling up a side-by-side view. On the left: what was projected when the original deal closed — the use cases, the assumptions, the estimated savings. On the right: what was actually delivered over the past twelve months.

"We projected $450K in savings. Here's what we actually delivered. Setup time on your pilot lines dropped from 2.3 hours to 1.1 hours. Defect rates fell 34%. Inventory carrying costs decreased by $180K."

That's proof. And it changes the entire dynamic of the expansion conversation. The customer isn't evaluating whether your product works — they already know it works. They're evaluating where to deploy it next.

Minoa's Historic Scenarios make this possible by keeping the original business case alive after the deal closes. Here's what the side-by-side looks like in practice:

Historic Scenario (Months 1-12): Use cases activated, actual results from Year 1 implementation, original investment, delivered value
Future Scenario (Months 13-24): New use cases for expansion, projected value based on actual baselines, expansion investment required

The comparison view tells the whole story in a single frame: "You've already saved $450K. Now let's talk about adding $600K more."

The credibility gap that kills most expansion deals simply doesn't exist when you can show what you promised alongside what you delivered.

Build Expansion Use Cases on Actual Baselines

Here's a subtle but critical difference between land and expand business cases: the expand case should be built on real data, not industry benchmarks.

In the land deal, you might estimate changeover time at 2 hours because that's the manufacturing average. In the expand deal, you know it's 1.1 hours on the pilot lines because you measured it. That's your new baseline.

Minoa lets you build custom use cases for the expansion that are rooted in Year 1 reality:

Predictive Maintenance — reduce unplanned downtime, calculated from the actual downtime numbers you now have
Supply Chain Optimization — reduce raw material waste based on real inventory data from the first year
Energy Efficiency — reduce utility costs using actual energy consumption patterns from deployed lines

You're no longer talking about "reducing downtime" in the abstract. You're talking about "extending the predictive maintenance model from Lines 1-2 to Lines 3-8, based on the 43% reduction in unplanned stops we achieved in the pilot." That kind of specificity closes deals.

Give the AI Your History

In the expansion conversation, Minoa's AI Value Agent becomes dramatically more useful. It draws from a full year of context:

Year 1 performance data and delivered results
Call transcripts mentioning new pain points or evolving priorities
Industry trends for manufacturing (predictive maintenance, sustainability targets)
The customer's latest earnings call or strategic announcements

Ask the system: "What use cases would drive the most value for expansion?" And the analysis might surface Energy Efficiency because the customer's sustainability manager has been included in recent calls, and the company's annual report highlights a commitment to reducing energy consumption by 20% by 2028.

The AE doesn't need to synthesize all of this manually. The AI surfaces the expansion opportunities most likely to resonate — and explains the reasoning behind each recommendation.

Scenarios: Let the Customer Choose Their Path

Expansion conversations often stall because the customer can't visualize the options. "We want to expand" is vague. Three specific options with different investment levels and different returns? That's actionable.

Minoa's Scenarios feature lets you build and compare side-by-side:

Scenario 1: Status Quo — just renew the current contract, no expansion, maintain the savings already being realized
Scenario 2: Production Line Expansion — add three more lines, moderate investment, predictable ROI based on pilot data
Scenario 3: Full Plant Deployment — all ten lines plus warehouse integration, larger investment, but a step-change in operational efficiency

Laying these side-by-side does something powerful. The renewal-only scenario suddenly looks like a missed opportunity. The full deployment looks ambitious but achievable given what's already been proven. Most customers land somewhere in the middle — which is exactly what you wanted. The point is to make the decision concrete rather than abstract. A concrete decision moves forward. An abstract one sits in limbo.

Phase the Expansion Like You Phased the Land

Just as the Value Timeline drove clarity in the original deal, it drives confidence in the expansion. A phased expansion timeline for Months 13-24 might look like:

Months 13-15: "Predictive Maintenance" pilot on 2 additional production lines
Months 16-18: "Supply Chain Optimization" with full warehouse integration
Months 19-24: "Energy Efficiency" across the entire plant

Each phase builds on the Year 1 foundation, and each has clear milestones tied to measurable outcomes. The customer can see exactly how the expansion unfolds, and the phased approach reduces the perceived risk of a larger commitment.

Re-engage Your Champions and Add New Ones

The plant manager who championed the original deal is still your advocate — and now they have twelve months of evidence to back them up. Re-invite them into the business case as a collaborator. Let them see the historic versus projected comparison. Let them add context and nuance that only someone on the inside would know.

But the expansion deal likely involves new stakeholders:

The VP of Operations who oversees multiple plants and needs the rollout timeline
The Sustainability Manager who cares about energy efficiency projections
A finance leader evaluating the next budget cycle who needs investment summaries and payback periods

Minoa's collaboration and sharing tools let you bring each of these people into the same business case with the right level of access and the right view. Stakeholder mapping tracks who's involved and what they care about. Tab visibility controls ensure each person sees the story through their lens. And threaded comments keep the conversation alive between meetings — "@VP Operations: can you confirm the headcount for Plant B?" — so momentum doesn't stall between calls.

The Connective Tissue: What Ties Land and Expand Together

The real insight here is about continuity.

When the business case from Day 1 survives through implementation, tracks actual results, and becomes the foundation for the expansion conversation, something fundamental changes in the customer relationship. You're a partner with a shared record of what was promised, what was delivered, and what comes next.

The Minoa features that make this work aren't standalone tools. They're the infrastructure of a value story that compounds over time:

Account Research keeps the context current across the entire relationship
Input Scout captures golden nuggets from every conversation, land and expand
Historic Scenarios bridge the gap between what you projected and what you delivered
AI Value Agent gets smarter as it accumulates more deal history
Collaboration and sharing keep champions engaged and bring new stakeholders in
Export options put the right level of detail in front of the right person at the right time

The manufacturing company that signed a $200K contract and expanded to $600K didn't do so because of a brilliant pitch deck. They did so because the value story was continuous — projections became proof, and proof became the foundation for the next chapter.

That's the difference between a sales team that lands deals and a sales team that grows them. It's not about closing harder. It's about building a value story that's designed to grow.

Last updated: Jan 27, 2026

The Land-and-Expand Playbook: How to Build a Value Story That Grows With Your Customer