All field notes

How-to ·

How to build a sales value framework

A sales value framework maps buyer problems to outcomes, required capabilities, proof and differentiators. How to build one, a template row and an example.

A sales value framework is a shared document that maps each buyer's business problems to the outcomes they want, the capabilities a solution needs, how success is measured, and why your company delivers it best, with proof.

What a value framework is

A value framework is the reference every customer-facing team uses to talk about value the same way. Force Management, whose Command of the Message method popularized the term, says it "isn't a script." It calls it "a repeatable framework that guides the customer conversation," whether that conversation happens in person, on the phone or in writing.

Force Management describes five things a good framework does. It sets out the buyer's priorities, so sellers start from what the buyer cares about. It gives reps "the talking points that clearly explain your company's differentiation." It is a discovery tool for uncovering quantifiable business pain. It organizes proof points (case studies, metrics, references) so reps can find the right one. And it is used across sales, marketing and services, so the message holds from the first ad to the renewal.

The phrase has other meanings. Bain's Elements of Value is a model of what customers value in general, and the ValueSelling Framework® from ValueSelling Associates is a separate sales method with its own vocabulary. This piece covers the Command of the Message sense: the internal document a team builds about its own offer.

Who builds it and how long it takes

A value framework is built by a small cross-functional group and owned by one person. Force Management puts the foundation in alignment: marketing, services, product and sales agreeing on the value drivers and differentiators that matter to key buyers. In practice, product marketing or enablement usually holds the pen, with two or three strong reps and a sales leader in the room.

A first version takes a few weeks of part-time work: interviews with reps and customers, two or three working sessions to draft, and a round of testing on live deals. After that it needs a review each quarter, because competitors, products and buyer priorities move.

What goes in a value framework

Each row of a value framework follows one buyer problem from the situation today to the proof that you solve it. The terms below are Force Management's, from its published material.

One row of a value framework
  1. 01Before ScenarioThe problem today, and what it costs
  2. 02Positive Business OutcomeThe business result the buyer wants
  3. 03Required CapabilitiesWhat any solution must do
  4. 04MetricsHow the buyer will measure success
  5. 05Differentiators and proofWhy you, and the evidence
  • Before Scenario. The buyer's situation today: what is going wrong and what it costs. Force Management describes the seller's job as moving the customer "from the Before to the After Scenario."
  • Positive Business Outcomes (PBOs). Force Management defines these as "the tangible benefits that result from a buyer implementing your solutions." They are business-level goals an economic buyer would move money to reach.
  • Required Capabilities. "The minimum solution requirements that are needed to solve the business problem and achieve the positive business outcomes."
  • Metrics. How the customer will measure success, expressed as KPIs. Force Management's advice: "don't overcomplicate it!"
  • Differentiators. How your way of delivering the capabilities differs from the alternatives, in terms that connect to the outcomes.
  • Proof points. Case studies, customer metrics and references that back each claim.
  • Discovery questions. Questions that uncover the Before Scenario and the PBOs, including trap-setting questions, which help the buyer define decision criteria where your differentiators matter.
Before Scenario Positive Business Outcome Required Capabilities Metrics Differentiator Proof point Discovery question
The problem today, in the buyer's words The business result the buyer wants What any solution must do to get there How the buyer will measure it How you do it differently A customer result or reference The question that surfaces the problem

How to build one in seven steps

  1. Pick the buyers. List the two to four roles that decide most of your deals, such as a VP of operations, a CFO and an IT lead. One framework per role is easier to use than one framework for everyone.
  2. Interview before you write. Talk to five or six of your best reps and, if you can, a few customers. Ask what was going wrong before they bought and what changed afterward. The Before Scenarios come from these conversations.
  3. Write the Before Scenarios in the buyer's words. One problem per row, stated the way a buyer would say it on a call. "Our dispatchers re-key every order" beats "manual processes create inefficiency."
  4. Link each problem to an outcome. For every Before Scenario, write the Positive Business Outcome the buyer would report upward. Test it against Force Management's bar: would an economic buyer reallocate money to reach it? If not, dig to the business issue underneath.
  5. Define the Required Capabilities. Write the minimum a solution must do to reach the outcome, in neutral terms. Then mark which of those capabilities you deliver differently from the alternatives.
  6. Attach metrics and proof. Add how the buyer would measure success, and the case study or reference that shows you have done it. Leave a cell empty when there is no proof; an empty cell tells marketing what to go and find.
  7. Write the discovery questions last. For each row, write the question that gets a buyer to describe the Before Scenario, and one trap-setting question that brings a differentiator into their decision criteria. Then test the framework on live deals for a month before calling it finished.

A filled-in row

This example is illustrative. A vendor of fleet maintenance software builds a framework for operations leaders at mid-sized logistics firms such as Arrowmere, a 600-person logistics firm.

  • Before Scenario. "Trucks go off the road without warning. We find out when a driver calls in from the roadside."
  • Positive Business Outcome. Fewer missed deliveries caused by breakdowns, so the firm can hold its on-time commitments to its largest customers.
  • Required Capabilities. Maintenance alerts from vehicle data before a part fails, and scheduling that fits repairs around delivery routes.
  • Metrics. Unplanned breakdowns per month, and on-time delivery rate.
  • Differentiator. Repairs are scheduled into the gaps in each truck's route plan, so a truck is in the shop when it would have been idle.
  • Proof point. A reference customer of similar fleet size who agreed to take calls.
  • Discovery questions. "When a truck breaks down mid-route, what happens next, and who hears about it first?" Trap-setting: "How would you want repairs to fit around the routes you have already promised customers?"

The trap-setting question works because any vendor can send an alert, while fitting repairs around route plans is this vendor's strength. If the buyer agrees it matters, it enters their decision criteria.

Where it goes wrong

  1. It is written from the pitch deck. Rows that start from features ("real-time dashboards") produce a product brochure with extra columns. Start every row from a Before Scenario a buyer would recognize.
  2. The outcomes are too small. "Save time on reporting" will not interest an economic buyer. Force Management's test is whether the outcome is worth moving discretionary funds for.
  3. Nobody uses it on calls. A framework that lives in a shared drive changes nothing. It has to show up in deal reviews, call plans and CRM fields, where a manager can ask whether a field is in the buyer's words.
  4. It never changes. A framework built once and never revised drifts from what buyers say. Review it every quarter against recent wins and losses.

Using the framework in deal reviews

The framework is most useful when a manager holds a live deal against it. In a deal review, the questions are short: which Before Scenario has this buyer described, in their words? Which Positive Business Outcome has the economic buyer confirmed? Which Required Capabilities are in their decision criteria, and did we help put them there? The Command of the Message entry shows what a filled-in field sounds like.

Teams that run Command of the Message, or their own house method, can bring a deal to Caty, our AI sales expert, by voice or video on a call. Caty works in the team's own vocabulary and checks the deal against it. Replicate Labs has no partnership with Force Management. See coaching your own methodology on live deals or talk to us.

For how a value framework sits next to a qualification method like MEDDPICC, see the sales methodology guide. The terms each have their own entry: required capabilities, positive business outcomes and before and after scenarios.

FAQ

What is a value framework in sales?

A value framework is a shared document that maps buyer problems to the outcomes they want, the capabilities required, the metrics, and your differentiators and proof. Customer-facing teams use it to describe value consistently.

What is the Command of the Message value framework?

It is the value framework at the center of Force Management's Command of the Message method. Its terms include Before Scenarios, Positive Business Outcomes, Required Capabilities, Metrics, differentiators and proof points.

Who should own the value framework?

Product marketing or sales enablement usually owns the framework, with input from sales, services and product. Force Management puts cross-functional alignment at its foundation, so one owner gathers many voices.

How often should a value framework be updated?

Review the framework every quarter against recent wins, losses and competitor moves. A full rebuild is needed only when the product or the target buyer changes significantly.

Is a value framework a sales script?

A value framework is a reference for the conversation, which Force Management says "isn't a script." Reps use it to find the right problem, outcome and proof, then say it in their own words.

Put an expert on your deals.

Talk to Keenan about a live deal for free, or talk to us about experts for your team, your product or your coaching business.

Talk to us