Command of the Sale

Command of the Sale was developed by Force Management (founded by John Kaplan and Carl Sewell) starting in the early 2000s. Force Management trained the GTM teams at companies like Salesforce, MongoDB, Cisco, and Veritas - many of the most rigorous enterprise sales orgs in tech.

The methodology centers on giving the rep command of the sales conversation: command of the message (what we say), command of the sale (how we control the deal), and command of the talent (how we coach reps). It pairs naturally with MEDDPICC and is often deployed alongside it.

The seller, not the buyer, drives the deal. Reps who let the buyer set the pace, the agenda, and the next step lose. Reps who proactively name the buying process, lock in the next step with a date, and push back on stalls win.

Two rules:
1. You don't close deals - you control them. Closing follows from controlling.
2. No call ends without a defined next step with a specific date. "I'll follow up next week" is a fail.

1. Command of the Message. Position your unique differentiation in language tied to the buyer's outcomes. Use the REC structure: Required → Evidence → Capability.

2. Command of the Sale. Map the buying process. Drive each meeting with a specific objective, agenda, and post-meeting commitment. Use deal qualification (MEDDPICC) to identify weak spots and run plays.

3. Command of the Plan. Build a mutual close plan with the buyer - joint timeline, joint accountability, joint signing date.

4. Command of the Talent. Force Management's coaching layer - managers reinforce the methodology rep-by-rep, deal-by-deal.

5. Maintain control of pace. Push back on "let me think about it." Drive next-step language. Don't accept vague timelines.

Best fit: - Enterprise B2B SaaS (>$100K ACV)
- Multi-stakeholder, multi-meeting cycles (90+ days)
- Sales orgs with disciplined forecast accuracy requirements
- Reps who need to push back on buyer-led sales cycles

Bad fit: - Velocity SMB sales where the buyer wants speed
- Categories where the rep has limited credibility to push back
- Self-serve / PLG motions

Setting agenda (control of meeting):

"Before we start, here's what I'd like to cover, what I'd like to walk away with, and what I think you'd want to walk away with. Sound right?"

Mapping buying process:

"Walk me through every step from today to a signed contract. Who's involved at each step? Roughly how long does each step take?"

Locking next step with date:

"Great - so the next step is a 60-min technical deep dive with you, your VP of IT, and our solutions architect. Looking at calendars: Thursday at 2 PM or Friday at 10 AM?"

Pushing back on stalls:

"I want to be honest - when buyers say 'let's revisit in a month,' usually that means it's not a priority right now. If that's true, no hard feelings - but I'd rather know now than chase you for 4 weeks. Is this still a priority?"

The mutual close plan:

"Let's build a joint timeline together. Today is [date], you want to be live by [date]. Working backward, we need contract signed by [date], legal review starts [date], procurement [date], technical eval [date]. Does this look realistic on your side?"

Scenario: AE running a strategic enterprise deal in week 6.

Rep: "Mike, before we wrap, let me make sure I understand the path forward. You said you want to be live by Q1 - that's [date]. To hit that, we need: contract signed by [date], procurement to start [date], technical eval to wrap by [date], and the security questionnaire submitted by [date]. Today, we're 3 weeks behind on the security questionnaire. What's the bottleneck - and how do we unblock it together this week?"
Buyer: "It's stuck in our InfoSec team's queue. They're slammed."
Rep: "OK. Let me push back gently - if we don't unblock it this week, the Q1 go-live slips by 4 weeks. Is that acceptable to you, or do we need to escalate to your CIO to prioritize this?"
Buyer: "It's not acceptable. Let me email my CIO today."
Rep: "Great. I'll send you a 1-pager you can attach showing the dependency chain. End of day Wednesday - let's regroup. Thursday 9 AM, 15-min call to confirm we're back on track. Calendar invite coming. Sound good?"
Buyer: "Yes."

Why this worked: Rep mapped the process ✓ Identified the bottleneck ✓ Pushed back on the stall ✓ Provided enabling artifact ✓ Locked next step with specific date and time. The deal moves forward because the rep, not the buyer, is driving.

1. Letting the buyer dictate pace. "We'll get back to you" is a fail. Always lock next step.
2. Vague next steps. "I'll follow up next week" is not a next step. "Tuesday at 2 PM, 30-min call to review the security feedback" is.
3. Avoiding pushback to be likeable. Reps who don't push lose deals to reps who do.
4. Skipping the mutual close plan. Without it, the deal hits a procurement wall and dies in week 11.
5. Command without empathy. Pushing too hard without warmth feels aggressive. Stay collaborative.

- Force Management's "Command of the Message" content (forcemanagement.com)
- The MEDDIC Sales Process - Andy Whyte (complementary qualification framework)
- Selling to the C-Suite - Nicholas Read & Stephen Bistritz
- The Challenger Sale - Dixon & Adamson
- Force Management Audible Ready Sales podcast