Command of the Message: Building the Business Case That Wins

Ask five reps from the same company what they sell and you'll often get five different products. One leads with features, one with a customer story, one with the competitive comparison, one with the pricing model, and one with whatever the last prospect happened to respond to. None of them are wrong, exactly. But a buyer who talks to two of them hears two different companies, and a sales leader can't coach, forecast, or scale something that changes from rep to rep.

Command of the Message was built to fix that. The core idea: every seller should be able to explain the customer's problem, what it costs the business, the capabilities needed to solve it, and how the seller's offering delivers those capabilities differently from any alternative. And they should all do it in the same structured way, using a framework the whole company shares. It is a messaging framework and a selling methodology in one.

Where it came from

Force Management, a sales consultancy founded in 2003 by John Kaplan and Grant Wise, both former sales leaders, created Command of the Message. Force Management's roots go back to the Parametric Technology Corporation (PTC) sales culture of the 1990s, the same lineage that produced MEDDIC. Kaplan and Wise built Command of the Message as the conversation-and-messaging counterpart to that qualification discipline, and Force Management sells the two together as Command of the Sale.

The framework spread through enterprise software in the 2010s, mostly through companies whose sales leaders had come up in the PTC lineage. What sets it apart is that it gets taught as a company-wide program rather than a rep-level skill. Product marketing, sales enablement, and sales leadership build the messaging together, and the whole go-to-market org gets trained on it. MongoDB, Snowflake, and many others have publicly credited Force Management programs with shaping their sales cultures.

Where it fits best

Command of the Message was designed for B2B technology sales where:

• The product is differentiated but the differentiation is hard to put into words, especially against "good enough" alternatives.
• Many sellers need to tell one consistent story across a large team, several segments, or many regions.
• Deals need a business case that holds up with stakeholders who never see the demo.
• Sales and marketing messaging have drifted apart and the company needs one narrative back.

It matters less in transactional sales where nobody needs a business case. And it's heavy for very early-stage companies still working out what their differentiation is, though building the framework often forces that discovery, which can turn out to be the most useful part of the exercise.

How the methodology works

There are two layers. The Value Framework is a messaging structure the company builds once and maintains. The customer conversation is how reps use it in deals.

The Value Framework

The company writes a structured document that answers four connected questions for each target persona and use case. Force Management teaches these as a grid that reads left to right:

Element	Question it answers
Business problem / positive business outcome	What is the customer trying to achieve, and what problem stands in the way?
Required capabilities	What does a solution have to do to achieve that outcome?
How we do it	How does our product deliver each required capability?
Proof points	What evidence (metrics, customer results, references) shows we've delivered it before?

The framework also spells out differentiators: what the seller does that alternatives don't, framed in terms of the required capabilities, so that differentiation is about outcomes rather than a feature list. And it captures the cost of inaction, what the customer loses by staying with the status quo. In enterprise deals the status quo is the competitor that beats you most often.

The discipline is in the upkeep. The Value Framework gets built with product marketing, checked against real customer language, and kept current. Once it exists it becomes the source of truth for pitch decks, discovery guides, competitive positioning, and onboarding. If it goes stale, reps quietly stop using it and drift back to their own versions.

The customer conversation

Reps use the framework through a conversation structure Force Management sums up as "What, So What, Now What," with most of the weight on the middle. It runs roughly like this.

The seller starts with the positive business outcome. Discovery opens by understanding what the customer is trying to achieve at a business level, as opposed to what they want from a tool. "Reduce customer churn by five points this year" is an outcome. "Get a better support platform" is a request, and it tells you almost nothing.

Next come the problems and their impact. For each outcome, the seller identifies what's blocking it and works with the customer to size the cost: revenue at risk, money spent, time lost, exposure to risk. This is where Command of the Message overlaps with value selling and with SPIN's implication questions. The impact is what makes the outcome urgent instead of merely interesting.

Then the seller defines the required capabilities with the customer. What must any solution do to reach the outcome? This step is where the strategy lives. If the seller has done the work, the capabilities the customer writes down will line up with the seller's differentiators, and the decision criteria are shaped before the formal evaluation even starts.

Only now does the seller show how they deliver each capability, with proof. Product gets connected to capabilities one at a time, each with a proof point. The demo is organized around required capabilities, never around a feature tour.

Last, the seller differentiates and puts a number on inaction. They make explicit what the alternatives can't do against the required capabilities, and what the customer loses each quarter they wait. Those two things together are what defend price and create urgency.

Command of the Sale: pairing with MEDDICC

Force Management pairs Command of the Message with MEDDICC-style qualification so that the business case and the deal mechanics get managed together. The metrics from the impact step become the M in MEDDICC. The required capabilities become the decision criteria. The champion is whoever can carry the business case internally. Pipeline reviews check both sides.

A worked example

A seller of observability software for engineering teams meets the VP of Engineering at a fintech.

• Positive business outcome: Ship features faster while keeping uptime above 99.95 percent, because a recent outage cost a major client.
• Problems and impact: Engineers spend roughly 30 percent of their time diagnosing incidents across four monitoring tools; mean time to resolution is over two hours; the last outage cost an estimated $800,000 in credits and lost business.
• Required capabilities (defined with the VP): a single view across infrastructure, applications, and logs; automated correlation of anomalies to root cause; alerting that reaches the right engineer without noise.
• How we do it, with proof: The seller walks through each capability in turn, with a reference customer that cut MTTR by 60 percent.
• Differentiation and cost of inaction: The incumbent tools cover the first capability partially and the second not at all. Every month of delay is another month of 30 percent diagnostic overhead, roughly $200,000 in engineering time by the VP's own numbers.

Every rep at the company would run this conversation the same way, because the Value Framework for the "VP of Engineering, reliability outcome" case is written down and everyone has been trained on it.

Strengths and limitations

Command of the Message gives you consistent messaging, stronger business cases, pricing that holds, and a shared language between sales, marketing, and leadership. Onboarding gets faster too, because a new rep learns one framework instead of absorbing five senior reps' habits over six months. The limitations: it's a big organizational investment. It can produce sellers who recite the framework instead of adapting it, and buyers can hear the script. And it needs ongoing upkeep as the product and market move. Like MEDDIC, it's most often adopted by companies past the early stage that need to scale a sales org, and that's where we'd recommend it.

Key takeaways

• Command of the Message is a shared messaging framework and a selling method at once, built so every rep tells the same story.
• Force Management, founded in 2003 by John Kaplan and Grant Wise, created it out of the PTC sales lineage that also produced MEDDIC.
• The Value Framework connects business outcomes, required capabilities, how you deliver them, and proof. It only works if someone keeps it current.
• Define required capabilities with the customer before the evaluation starts, so the decision criteria favor what you do best.
• Pair it with MEDDICC so the business case and the deal mechanics get reviewed together.

A Value Framework only helps if reps can see, in the moment, which outcome and which proof point fit the account in front of them. Surfacing the right message at the right stage, based on what the account has actually done, is what turns a static playbook into dynamic orchestration.