# Command of the Message in Pipedrive: three deal fields instead of a workshop https://salesbond.app/blog/command-of-the-message-pipedrive/ Published: 2026-10-08 · Updated: 2026-10-08 Command of the Message is a sales methodology from Force Management that trains reps to describe the buyer’s situation before and after your solution, in measurable terms the buyer agrees with. A small Pipedrive team can run a slice of it with three deal fields: the buyer’s “before”, a Positive Business Outcome stated as a number, and two or three Required Capabilities. Below: which part of the method survives when there are five of you and no consultants, how we’d build the three fields, and the one deal-review question that tells you whose number is in the Outcome field. ## The deal where the buyer could not repeat our pitch The deal below is a composite of two we lost, but the shape is exact. Mid-size logistics company, three calls in, a proposal out, a champion who liked us. The rep’s notes were good: the buyer’s ops team was rekeying orders from email into their system, two people spent most of Monday on it, and the champion wanted it gone. Then the champion took it to her director and the director asked what they would actually get. She said “it automates the order entry.” He asked what that was worth. She didn’t know. The deal went quiet, and two months later they bought a cheaper tool that did half the job, because half the job was all anyone upstairs had been told to expect. We had the pain. We never got the buyer to say, in her own words and with a number, what Monday looks like after. So when the pitch had to travel without us, it traveled as a feature. Command of the Message exists for exactly that gap. ## What Command of the Message actually asks of a rep Command of the Message is Force Management’s method for being audible-ready: able, at any moment in a conversation, to explain how your solution solves the customer’s problem in a way that sets you apart from the alternatives and justifies your price, with the value framed as the difference between the buyer’s before and after, in the buyer’s terms ( [Force Management: what’s the meaning of Command of the Message](https://www.forcemanagement.com/blog/whats-the-meaning-of-command-of-the-message)). A full rollout of the Command of the Message framework carries a lot more than that; Oliv lists the CRM fields a typical implementation adds as Economic Buyer, Negative Consequences, PBOs, Required Capabilities, Differentiation and Proof Points ( [Oliv: Command of the Message](https://www.oliv.ai/blog/command-of-the-message)). We take three things from it: the before scenario, the outcome and the required capabilities. Force Management measures the effect of a rollout by how well reps talk about value in a live conversation. It calls this Value Engagement. Strip the training away and a rep is being asked to hold three things in their head about every deal. First, the before scenario: what the buyer’s world looks like today, told in the buyer’s language, with whatever it costs them attached. Not “manual process” but “two people lose Monday to rekeying orders”. Second, the after: the Positive Business Outcome (Outcome, for short). A measurable improvement, in the buyer’s terms, that the buyer has agreed is the point of the purchase. “Monday back for two people” is an outcome. “Automated order entry” is a feature. Third, the required capabilities: the specific things a solution has to do for that outcome to happen. If the orders arrive as PDFs, “reads PDF attachments” is a required capability, and a tool that only parses structured email is not a fit. Force Management also says that in a team running the methodology, this vocabulary ends up in deal reviews and in CRM fields ( [same page](https://www.forcemanagement.com/blog/whats-the-meaning-of-command-of-the-message)). That’s the part we care about. The method’s own words are what you type into Pipedrive. ## The slice that fits in a five-person team Most of Command of the Message is a company program, and only three parts of it fit a small team. Oliv, one of the vendors writing about the method, says its a poor fit for transactional deals under $10K closed in one call and for sales teams smaller than ten people ( [Oliv](https://www.oliv.ai/blog/command-of-the-message)). Their answer to the long field list is AI that fills it in. Ours is a shorter list. We’d read their size warning narrowly. What doesn’t fit a five-person team is the program: a company-wide Value Messaging Framework built in workshops, differentiation work against each named competitor, pricing strategy tied to the message. That is consulting work, and it produces documents rather than deal fields. What does fit is the discipline of the three things above, written down per deal. A rep on a $20,000 deal (say) with four stakeholders needs the buyer to be able to repeat the outcome upstairs just as much as an enterprise rep does. So we take Before, Outcome and Capabilities. Differentiation and Proof Points stay as things reps say on calls rather than fields they fill, and the Economic Buyer lives in the deal’s participants list, which we covered in finding the economic buyer in Pipedrive. Negative Consequences, the cost of not acting, we fold into the Before field by asking for the cost in the same sentence. Fewer fields that get filled beat more fields that get skipped; we made the same trade in [MEDDIC for small sales teams](https://salesbond.app/blog/meddic-small-sales-teams-pipedrive/). ## Before, Outcome, Capabilities: the three fields in Pipedrive Pipedrive lets you add custom deal fields with a description that tells the team what goes in them, and lets you show or hide each field per pipeline. A field can be marked required, which blocks saving the deal until it has a value, or important, which highlights the gap without blocking the save ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). We went through when to use which in [required fields in Pipedrive](https://salesbond.app/blog/required-fields-pipedrive/). The three we’d add: 1. Before. One or two sentences in the buyer’s words, with the cost attached. Field description: “What happens today, in their words, and what it costs them. Example: ‘Two people rekey orders from email every Monday, about 12 hours a week.’ If all you have is our description of their problem, leave it empty.” Mark it important. The rep should be filling it from the first call, which is where the [discovery call](https://salesbond.app/blog/discovery-call-small-team-pipedrive/) earns its keep. 2. Positive Business Outcome, a number field with the unit in the description. Description: “The measurable improvement the buyer said they want. A number and a unit, confirmed by the buyer, not calculated by us. If they haven’t said it, it’s a hypothesis. Put the hypothesis in a note, not here.” Important, never required. A required field here invites a rep to type their own estimate just to get past the save, and then the field looks like the buyer’s number when it isn’t. 3. Required Capabilities, three items at most. Description: “The two or three things any solution must do for the outcome above to happen, as the buyer named them. If we don’t do one of them, say so in the deal before the proposal goes out.” Important. Not a pick list of our own features: a pick list gets picked. Keep all three on the new-business pipeline only. A renewal does not need a Before scenario; the customer already lives in the after. ![Deal detail panel with Before, Positive Business Outcome and Required Capabilities fields, each tagged with who said it](https://salesbond.app/wp-content/uploads/2026/10/command-of-the-message-pipedrive-2.png) One rule we deliberately don’t have: “Outcome must be filled before Proposal Sent.” We’d rather see the blank at Proposal Sent and talk about it than see a number a rep typed to move the deal. ## Whose number is it? The manager’s check in deal review Filled is not the test. The rep on the logistics deal could have typed “12 hours a week” into Outcome from his own notes and passed any completeness check. The check that catches it is about provenance, and it takes a minute per deal. - Who said the number in Positive Business Outcome, and on which call? If the answer starts with “I worked it out from”, move the number to a note and leave the field empty until the buyer confirms it. - Read me the Before field. Would the champion recognize the sentence as hers? - Of the required capabilities, which one did the buyer bring up without prompting? A list where every item is something we happen to do well was written by us. - Which capability are we weakest on, and does the buyer know? - If the champion had to explain this deal to her director tomorrow with us not in the room, which of the three fields would she get wrong? The last question is the one we’d keep if we could only keep one. We run this inside the the normal deal review, not as a separate ritual; the questions slot in after the next-step question from our post on [deal review questions that end in a buyer action](https://salesbond.app/blog/deal-review-questions-buyer-action/). In the first month a lot of Outcome values will move back into notes. That is the method working. An honest blank tells you more about a deal than a number nobody can trace. Then reps start asking the confirming question on calls, because they know the field will be read out loud on Thursday. That’s the behavior change the method is after, and nobody attended a workshop for it. The mechanical half we automate for ourselves. SalesBond’s Deal Health applies more than 20 rules to every deal, among them whether the fields your process depends on are filled and fresh, so an empty Outcome shows up without anyone building a report. The “who said it” question is still yours. [Check your CRM with SalesBond](https://salesbond.app/) if you’d rather not chase the blanks by hand. ## Next to SPICED, MEDDIC and Gap selling: one methodology per team If you’ve read our posts on [SPICED](https://salesbond.app/blog/spiced-sales-framework-pipedrive/), [MEDDIC](https://salesbond.app/blog/meddic-small-sales-teams-pipedrive/) or [Gap selling](https://salesbond.app/blog/gap-selling-pipedrive/) in Pipedrive, you’ve seen three fields before. Same article, new labels? No. The difference is the axis. SPICED, MEDDIC and Gap selling all start from what you have found out about the buyer: their pain, their metrics, the event that forces a decision, the distance between where they are and where they want to be. Command of the Message starts one step later, from how the rep says it back. Its test is whether the buyer can hear your value as the difference between before and after, in thier own terms, and repeat it without you in the room. Gap selling is the closest neighbor, and the line between them is this: Gap selling measures the gap between current state and future state and sells the size of that gap, while Command of the Message asks the buyer to confirm the future state as a number and to name the capabilities without which it will not arrive. Gap selling has no field for Required Capabilities. That is what this method adds. Which is why we’d still say one methodology per team (how to choose is in [sales methodology for Pipedrive teams](https://salesbond.app/blog/sales-methodology-for-pipedrive-teams/)). If your deals die for lack of urgency, the Critical Event in SPICED is the field you are missing. If they die in the hands of a champion who can’t carry the pitch upstairs, as ours did, the Outcome and Capabilities fields are. So pick the one that matches how your deals actually die, build three fields, and read them out loud on Thursdays. The reading out loud is the part no methodology does for you.