Command of the Message: the value framework, the Mantra and a worked example

This page is for sales leaders and enablement teams deciding whether to adopt Command of the Message, for marketers building a messaging framework with sales, and for reps who've been through the training and want a worked example. It covers what the method is, each part of the value framework, a filled-in framework for a services company, a call that uses it, and how it fits with MEDDICC.

What Command of the Message is and where it came from

Command of the Message is a sales methodology from Force Management, a B2B sales consultancy whose founder and president is John Kaplan. Force Management defines it as "being audible-ready to define your solutions to customer problems in a way that differentiates you from your competitors and allows you to charge a premium for your products and services." The firm says more than 100,000 people have completed its sales and manager training, and in December 2024 it launched certifications in Command of the Message alongside MEDDICC, Command of the Sale and Value Negotiation.

The definition has four working parts:

• Audible-ready. Like a quarterback changing the play at the line, reps adapt to what the customer says without going off message. Force Management stresses that this comes from practice, not improvisation.
• Solutions to customer problems. Start with the problem, not the demo. Force Management's line is "The person who owns the problem owns the customer," and "It's difficult to commoditize a problem."
• Differentiation. Know your strengths as they relate to competitors' weaknesses, and connect them to what the customer cares about, without bad-mouthing anyone.
• Charging a premium. Value that's understood and proven supports price.

Force Management describes the method as one layer of three: value comprehension (understanding markets, customers and value drivers, usually owned by marketing), value offering (products built to drive specific outcomes) and value engagement (how sales and services deliver that value to customers). Command of the Message lives in the last.

The value framework

The working document is the value framework. Force Management says it should set out the reasons a customer buys, categorize what makes you different, give reps discovery questions to quantify pain and its negative consequences, and organize case studies and success metrics so reps can match them to the buyer's issues. The terms below are the ones Force Management's own material uses.

Required capabilities are the hinge. If the buyer agrees that any solution must do something you do uniquely well, the evaluation tilts your way before you've pitched.

How to build a value framework

1. Pick one buyer and one offer. A framework for "everyone" says nothing. Start with your best segment and the persona who owns the problem.
2. Mine recent wins. Pull your last 10 to 20 won deals. For each, write the before scenario, what it cost the customer and why they chose you, in the customer's words.
3. Group the problems into value drivers. Most offers solve three to five recurring problems. Each becomes a column of the framework.
4. Write the required capabilities for each driver. Phrase them as what any solution must do, not as your feature names.
5. Attach differentiators and proof. For each capability you meet better, add a proof point with a before, an after and a measured result, and get permission to use it.
6. Write the questions. Discovery questions for each before scenario, and a trap-setting question for each differentiator.
7. Practice until it's audible-ready. Role-play the framework in deal reviews and call coaching until reps can use it without notes.

Worked example: a filled-in value framework

Illustrative example. The companies, people and figures are invented to show the method.

The seller: Meridian Climate Services (meridianclimate.example), a commercial HVAC and refrigeration service firm. The segment: multi-location restaurant groups with 20 to 60 sites. The persona: the vice president of operations.

VALUE DRIVER: Keep every location open and serving

BEFORE SCENARIO:
Equipment is fixed when it breaks. Each general manager calls their own contractor. Head office learns about closures after the fact.

NEGATIVE CONSEQUENCES:
Location-days lost to HVAC or refrigeration failures; spoiled food; overtime and emergency call-out rates; guest complaints in peak season.

POSITIVE BUSINESS OUTCOMES:
Fewer unplanned closures; predictable maintenance spend; one view of every site's equipment.

REQUIRED CAPABILITIES:
1. Planned maintenance on a schedule that avoids service hours
2. Guaranteed response time at every location, including outlying sites
3. One report across all sites showing equipment condition and open issues

METRICS:
Unplanned closure days; spoilage incidents; emergency calls per site; average response time

DIFFERENTIATORS:
Technicians trained on both HVAC and walk-in refrigeration, so one visit covers both; overnight maintenance windows; a single portfolio report

PROOF POINT:
A 32-site group (permission on file) went from 14 closure days to 5 in its first year, with response times logged in the shared report.

DISCOVERY QUESTIONS:
How do you hear about an equipment failure at a location? How many days did locations close last year because of HVAC or refrigeration? What did that cost?

TRAP-SETTING QUESTION:
When a walk-in cooler and a rooftop unit fail at the same site, how many contractors do you call?

The trap-setting question is honest because the difference is real: Meridian's technicians handle both systems. A trap-setting question built on a claim you can't back up is just a trap for yourself.

Using it in a conversation: the Mantra

Force Management's Mantra is "a saying that we use to ensure the sales team is aligned to the buyer around their current state." It covers the negative consequences the buyer is experiencing, the positive business outcomes they want, and the required capabilities to get there. It is not an elevator pitch. It changes every meeting as you learn more, and you open each follow-up by playing back what you heard and asking whether anything has changed.

The account: Oakline Restaurant Group (oakline.example), 40 locations. After the first discovery call, the rep's Mantra read:

"You told me that last year 19 location-days were lost to HVAC and refrigeration failures, and 11 cooler failures spoiled food. You want closures cut in half and maintenance spend you can budget for. To get there, you said any provider would need to maintain equipment outside service hours, guarantee response at all 40 sites, and give head office one report. Has anything changed since we spoke?"

Metrics, worked through with Oakline's CFO:

The agreement saves about $38,720 a year (10%) while halving closures. The 70% contribution figure is the CFO's: food and packaging run about 30% of sales. Because she supplied the inputs, she defended the result to the owners herself.

What made this work:

• The rep never described Meridian's services until the buyer had agreed on the three required capabilities.
• Two of the three capabilities matched Meridian's differentiators, which the trap-setting question had surfaced.
• The proof point matched the buyer's segment and size and used the same metric (closure days) that the buyer cared about.

A self-check for your team

Run this in a deal review or a coaching session. Each "no" is a gap in the framework or in practice.

• Can every rep state your top three customer problems in the customer's language, without slides?
• For each required capability, can reps name the differentiator and a proof point with a number?
• Does every proof point have a before, an after, a metric and permission to use it?
• In your last five deal reviews, did each opportunity record the before scenario, the outcomes and the agreed required capabilities?
• Is each trap-setting question built on a difference you can prove?
• Do marketing and sales use the same words for the same value drivers?

A deal-level rule of thumb (our guidance, not Force Management's): don't send a proposal until the buyer has agreed the required capabilities in writing, such as in a recap email they replied to.

When it fits and when it doesn't

How it compares with other methods

Before scenarios for a specific account are partly research. Recent news, hiring and expansion often tell you which value driver to lead with, and account research covers where to look; at volume, Bebop researches each account in a list and suggests the angle.

Common mistakes

• Writing the framework in product language. Required capabilities phrased as your feature names fool nobody. Phrase them as what any solution must do.
• Proof points without numbers. "Customers love us" isn't proof. A before, an after and a metric are.
• Training once and stopping. Audible-ready comes from repetition: role-plays, call reviews, deal inspection.
• Trap-setting questions that mislead. If the difference isn't real, the question backfires when the buyer checks.
• Reciting the Mantra as a script. It's a playback of what the buyer told you, and it changes every meeting.
• Leaving marketing out. A framework sales owns alone drifts away from the website and campaigns within a quarter.

Next step: pair the message with qualification using the MEDDPICC guide.