The glossary

Glossary

What are required capabilities in sales?

Required capabilities are the minimum things a solution must do to solve a buyer's business problem and reach the outcomes the buyer wants. The term comes from Force Management's Command of the Message method.

Force Management's own definition is "the minimum solution requirements that are needed to solve the business problem and achieve the positive business outcomes." Two words in it carry the meaning. Minimum, because required capabilities are the floor any vendor must clear. Solution, because they describe what has to be possible, written in neutral terms, before anyone names a product.

How required capabilities work in a sales team

Required capabilities sit in the middle of a Command of the Message value framework. On one side is the business: the Before Scenario (what is going wrong today) and the positive business outcomes the buyer wants. On the other side is the technical evaluation: the features, integrations and terms the buying group will compare. Force Management describes required capabilities as the link between those two sides.

That position is why they matter in a competitive deal. Force Management notes that a seller's success depends on how well they can shape these requirements with their solution's value and differentiation. Elite sellers, in its words, help buyers define their own decision criteria, using trap-setting questions so the seller's differentiators become part of the criteria.

Force Management's John Kaplan gives the timing: identify required capabilities early and validate them throughout the sales process. A list agreed in the first meeting and never revisited goes stale as new stakeholders join.

A working process for a rep usually runs in four steps:

  1. Start from the outcome. Confirm the positive business outcome the buyer wants, in their numbers. Required capabilities written before the outcome is known end up as a feature list.
  2. Ask what has to be true. With the buyer, list what any solution must do to deliver that outcome. Keep the language neutral, so the buyer would sign off on it whoever they buy from.
  3. Shape the list. Where your company delivers a capability in a way others cannot, ask the question that makes the buyer weigh it, so it becomes a requirement.
  4. Validate as the deal grows. Play the list back to each new stakeholder, and to the economic buyer before the proposal. Note who agreed and when.

Example

This example is illustrative. A rep sells warehouse labor planning software to Arrowmere, a 600-person logistics firm. The positive business outcome, stated by the operations director, is to stop paying overtime to cover peak weeks the firm could have predicted.

The required capabilities the rep and the director agree on:

  • A forecast of labor demand per shift, at least two weeks ahead
  • Shift plans that update when the forecast changes
  • A view of overtime cost per site that finance can read

None of those names a product. The third came from a trap-setting question about who in finance signs off on overtime. The rep's product reports cost per site and a competitor's reports only hours, so the rep asked the director how finance would see the savings. The director added it to the list.

In a deal review, the manager asks two things about required capabilities: did the buyer state each one, and who else has confirmed the list? "The director agreed all three, finance added the cost view last week" is a strong answer. "They need forecasting, scheduling and reporting" is a guess written from the pitch.

Required capabilities and decision criteria

The two terms overlap without meaning the same thing. Required capabilities come from Command of the Message and describe what a solution must do to reach the outcome. Decision criteria come from MEDDPICC and describe the standards a buyer uses to compare options, which can include price, terms and vendor relationship as well as capability. Many teams that run both treat required capabilities as the capability part of the decision criteria.

Related terms

Teams that run Command of the Message or a house method can check a deal's required capabilities with Caty, our AI sales expert, by voice or video on a call, in their own vocabulary. See coaching your own methodology on live deals.

FAQ

What are required capabilities in Command of the Message?

Required capabilities are the minimum solution requirements needed to solve the buyer's business problem and achieve their positive business outcomes. Force Management places them between the business outcomes and the technical evaluation.

What is the difference between required capabilities and features?

Required capabilities describe what any solution must be able to do, in neutral terms, while features describe how one product does it. A buyer should agree with the capability list before seeing a demo.

How do you validate required capabilities?

Play the list back to each stakeholder as they join the deal, and to the economic buyer before the proposal. Force Management advises identifying them early and validating them throughout the sales process.

What is a trap-setting question?

A trap-setting question is a discovery question that helps a buyer see the value of a capability where your solution is strong. Force Management uses it to bring differentiators into the buyer's decision criteria.

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