Command of the Message, live on the call.
The value-messaging standard behind most enterprise sales enablement. It works when the conversation stays anchored to the buyer's outcomes. Kairos listens for the drift to features and fires the question that pulls it back.
If this works the way you want, what changes for your team by the end of the year?
A discipline for talking about value instead of product.
Command of the Message is Force Management's framework for articulating value in the buyer's terms. It gives every rep the same structure: positive business outcomes the buyer wants, the required capabilities to get there, metrics that prove it, and how you do it differently. On top sits the 'why' sequence: why change, why now, why you.
It is a messaging framework. It makes the whole team say the same true thing about why a customer buys. It does not, by itself, tell a rep when to say it on a live call, which is where the discipline usually breaks.
Teams that run it well can draw the value framework on a whiteboard and the buyer recognizes themselves in it. Teams that run it badly have the framework in a slide and a conversation about features.
The five components.
| Component | Abbrev. | What must be true | How reps miss it | What Kairos fires |
|---|---|---|---|---|
| Positive business outcome | PBO | The buyer has named the business result they want, in their words, not yours. | Rep announces the outcome. Buyer never confirms it matters to them. | "If this works the way you want, what changes for your team by the end of the year?" |
| Required capability | RC | The buyer agrees on what they must be able to do to reach the outcome. | Rep jumps from outcome to feature, skipping the capability the buyer would own. | "To get there, what would your team need to be able to do that it can't today?" |
| Metrics | M | Current state and desired state are both quantified. | Desired state is a feeling. Current state was never measured. | "What does that look like today, in numbers? And where does it need to be?" |
| Differentiation and proof | D | The buyer understands what is different about how you deliver the capability, with evidence. | Differentiation is a feature list. Proof is a logo slide. | "Would it help to hear how a team your size got from there to here, and what they did differently?" |
| Why change · why now · why you | Why | All three have been established, in that order, by the end of the sales cycle. | 'Why you' is strong. 'Why now' was never asked, and the deal has no urgency. | "What's driving the timing on this? What happens if it waits a quarter?" |
Where reps break it.
The feature drift.
The call opens on outcomes and is a feature demo by minute ten. Every question about 'can it do X' pulls the rep further from value. Nobody notices until the proposal reads like a spec sheet.
The outcome the rep said.
The rep states the positive business outcome fluently, because enablement drilled it. The buyer never says it back. A value framework the buyer hasn't endorsed is a pitch, not a plan.
Why now, never.
Why change and why you are usually covered; the deck handles them. Why now is a question only the buyer can answer, and it gets skipped because asking it risks hearing 'no reason.'
The pull back to value, at the minute the drift starts.
Kairos tracks the value anchor across the call: whether an outcome has been named by the buyer, whether a capability has been tied to it, how many minutes have gone to features without returning to the outcome, and whether why-now has been established. When the conversation drifts past the point a senior leader would tolerate, it surfaces the question that returns it.
It is quiet while the conversation is on value. The feature drift is gradual, and the move is to catch it early with one question, not to interrupt a demo that is working.
If this works the way you want, what changes for your team by the end of the year?
Before you show it: ask what their team would need to be able to do to get that outcome. Let them name the capability.
What's driving the timing on this? What happens on your side if it waits a quarter?
Command says what to say about value. Pair it with how and whether.
Command of the Message is usually layered on top of a qualification framework and sometimes a conversation framework. Kairos runs all of them and tags each move with its source.
Command + MEDDPICC
Metrics map to Metrics; required capabilities map to Decision Criteria. The two frameworks were built to run together.
Command + Challenger
Teach the insight, then anchor it to the positive business outcome. Challenger opens the door; Command walks through it.
Command + your playbook
Your actual value framework, your proof points, your differentiators by segment.
Command of the Message with Kairos.
The Command of the Message coverage checklist.
One page. The five components, the buyer-confirmed test for each, the question that gets it, and the drift signals that mean you've left the value anchor. Built from the captured judgment behind Kairos. Print it, pin it, run it on your next call.
Hold the value anchor on the call, not in the deck.
Free for individual reps. A demo for teams.