Command of the Message: Force Management's Framework Explained

Marisol had a great plant visit. The maintenance lead at a dairy co-packer walked her down the line, and she spent an hour on her case packer's changeover speed, servo drives and touchscreen. Two weeks later, the plant manager emailed: "Thanks. We're going with the cheaper quote." (Marisol is a composite, built from situations field reps describe, not a real person.)

Marisol didn't lose on product. She lost because nobody at the plant could explain why her machine was worth more. She'd talked about the machine. She never wrote down what the plant was losing every week without it.

That gap is what Command of the Message is built to close. It's the selling methodology from the sales training firm Force Management. This guide covers what it is, the Value Framework behind it, the six-part Mantra with a worked example, how it pairs with MEDDICC, and a one-page note to fill in after every meeting.

What is Command of the Message?

Force Management defines Command of the Message 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." That's from its own explainer of the term.

Each phrase in that sentence does a job:

• Audible-ready. Like a quarterback changing the play at the line: adapt to what the buyer says without going off message.
• Solutions to customer problems. Start with the buyer's problem, not your features. "The person who owns the problem owns the customer."
• Differentiates you. Tie your strengths to what matters to this buyer, which "does not mean bad-mouthing competitors."
• Charge a premium. When the value is clear, the buyer can defend the spend and you don't discount to win.

So it isn't a script or a pitch deck. It's a shared way for a whole team to talk about value in the buyer's terms.

Want the buyer's exact words on hand when you write it up? Try ParrotNotes free on your next customer visit.

The Value Framework behind it

In a Force Management engagement, sales, marketing and product leaders build a Value Framework together in a facilitated workshop. The firm's FAQ is blunt: "A Value Framework isn't a script." It's a repeatable guide for the customer conversation, built on agreed value drivers and differentiators.

It starts with essential questions. Force Management lists them in its MEDDIC article as:

1. What problems do we solve?
2. How do we solve them?
3. How are we different?
4. What's the impact?

The answers become the parts of the framework. Force Management's list of what a sales messaging framework needs includes:

• Value drivers: the main reasons a customer buys from you
• Differentiators: how you solve those problems better and differently than the competition
• A way to quantify business pain: discovery questions that help the buyer see the cost of the problem
• Measurable outcomes and proof points: customer evidence that you do what you say
• Use across the organization, plus reinforcement from leaders and managers

Discovery questions uncover the pain (our discovery questions guide has 50 of them). Trap-setting questions "help you steer a discovery session toward your differentiators," as Force Management puts it in its post on trap-setting questions. They lead the buyer to value only you provide.

Your company owns the framework. You, the rep, own the Mantra for each deal.

The Command of the Message Mantra: six parts

The Mantra is how the framework shows up in a single deal. Force Management describes it as "a saying that we use to ensure the sales team is aligned to the buyer around their current state, what they're trying to achieve with a solution (Positive Business Outcomes) and what's required to get there (Required Capabilities)." It adds that the Mantra is "not your elevator pitch." It's a story about one specific customer, in their words, that keeps growing (source).

Force Management names its six components: before scenario, after scenario, negative consequences, required capabilities, PBOs and metrics.

One rule matters most: write each part in the buyer's words. "Changeover takes 90 minutes and we lose a shift's output on Fridays" is a before scenario. "Inefficient changeovers" is a guess. And build one Mantra per person: Force Management advises treating each decision maker like a separate buyer.

A worked Mantra from one field deal

Here's Marisol's second attempt at a different plant, a cheese packer, written as the Mantra she kept for the operations director. (A composite example. The numbers are illustrative, said by the buyer, not industry benchmarks.)

• Before scenario: "We change over between retail and food-service packs three times a week. Each change takes about 90 minutes, and two people stand around waiting."
• Negative consequences: "We've turned down two food-service orders this quarter because we couldn't fit the runs in. And I'm paying Saturday overtime to catch up."
• After scenario: "Changeover in under 30 minutes, done by the line operator, no maintenance call."
• Positive business outcomes: "Take the food-service business we're turning away and stop the Saturday shifts."
• Required capabilities: "Recipe-based changeover the operator can run from the screen. Parts available in 48 hours. Fits the existing footprint."
• Metrics: "Changeover time under 30 minutes by the end of Q2. Saturday overtime to zero."

Notice what's missing: servo drives, the touchscreen, the brochure. Those appear later, only as proof against a required capability. When her quote came in above a rival's, the director had his own numbers to defend it.

Command of the Message and MEDDICC

Force Management teaches both. Its MEDDIC article says MEDDIC "is not a selling methodology." It's a qualification framework, and "its power multiplies when paired with a strong selling methodology like Command of the Message."

Founder John Kaplan, who sold at PTC in the 1990s where MEDDIC began, compares it to an X-ray: "You can't fix your deals or solve your forecasting issues without having both the x-ray to identify gaps and the treatment so you can fix them." MEDDICC (with the second C for Competition) finds the gaps. Command of the Message is how you talk to the buyer to close them.

In practice, the Mantra fills several MEDDICC letters for you. This mapping is our reading of how the two fit, not an official Force Management table:

If your team uses MEDDPICC, our MEDDPICC guide walks through every letter on one deal, and MEDDIC vs MEDDPICC explains which to pick. For the person who signs, see our guide to the economic buyer.

Using Command of the Message in a face-to-face meeting

Open with "what we heard"

Force Management teaches reps to begin every follow-on meeting with "what you heard." Try this opener, built from that advice:

"Before we start, let me play back what we heard last time. Changeovers take about 90 minutes, you've turned down two food-service orders, and Saturday overtime is the workaround. Has anything changed? What else have you discussed since we met?"

It checks the facts are still true and invites anyone new to add their piece.

Ask the discovery and trap-setting questions

Spend most of the meeting on the before scenario and negative consequences. Ask "So what?" when an answer stays vague: "Changeover is slow. So what does that cost you?" Then add one trap-setting question tied to a differentiator. For Marisol, whose parts ship in 48 hours: "When a machine went down in the past, how long did you wait for parts, and what did that week cost?"

See also customer pain points and our in-person discovery call plan.

Replay the Mantra and ask for the next step

Close by repeating the negative consequences, PBOs and required capabilities, then ask who else should weigh in.

Check the required capabilities

Before you leave the parking lot, run the three questions Force Management suggests. Do the required capabilities describe the minimum to get from before to after? Are they compelling enough to act on, since "no decision" is often your strongest competitor? Does your differentiation map back to them?

The Mantra note: write it after every meeting

Write the Mantra while the buyer's words are fresh. One note per buyer, after each meeting:

MANTRA NOTE
Account / buyer / role:
Date and meeting type:

Before scenario (their words):
Negative consequences (cost, in their numbers):
After scenario:
Positive business outcomes:
Required capabilities (their must-haves):
Metrics (number + date):

Trap-setting question asked, and the answer:
What changed since last meeting:
Gaps (which part is still empty?):
Next step, owner, date:

The "Gaps" line is the coaching hook: empty metrics after three meetings tell a manager where to help.

The hard part is memory. Between the plant floor and the car, "we turned down two food-service orders" becomes "they want faster changeover," and the argument for your price is gone.

ParrotNotes keeps the exact words. Record the meeting on your phone, with everyone's consent (rules differ by state; see our guide to one-party consent states), or speak a two-minute debrief in the car. You get a transcript, a summary and action items in the buyer's own phrasing.

You can run the built-in MEDDIC framework on the recording to sort what was said into its elements. On Pro, you can set up a custom insight template with the six Mantra headings, and AI search across your notes finds every time a buyer mentioned "overtime" over a six-month deal.

Sales frameworks run on 5 AI-powered recordings a month on the Free plan and without limits on Pro ($19.99/month, or $14.99/month billed annually). Download ParrotNotes free and fill in your first Mantra note from a real meeting.

Where reps get it wrong

• Writing the Mantra in your own words. If the buyer wouldn't recognize it, it won't persuade their boss.
• Treating it as a pitch. The Mantra is about the customer. Your product only appears as proof against a required capability.
• One Mantra per deal. Each decision maker has their own before scenario and metrics.
• Never updating it. Force Management says the Mantra is never "done."

For the wider idea of selling on value instead of price, see our guide to value-based selling. If someone inside the account starts repeating your Mantra to their team, you may have found a champion.

Own the buyer's story

Command of the Message comes down to one habit: describe the buyer's problem better than they can, in their words, and tie your difference to what they need. The Value Framework gives your team the shared answers, the Mantra tells one deal's story, and MEDDICC shows where that story has gaps.

You don't need a Force Management program to start. Open your next follow-up meeting with "what we heard," ask "So what?" until you get a number, and fill in a Mantra note before you drive away. Get ParrotNotes free so the words you need are already captured when you sit down to write it.