The four stages of Systemic Value Selling — Discover, Design, Justify, Align

Fourth in a short series on the Future of Selling. The previous articles set out the problem, the six dimensions of value, and the Layered Business Case. This one names the method that builds them — the four stages of Systemic Value Selling.


A framework is not a method. The six dimensions of value describe what B2B value has become. The Layered Business Case describes the structural artefact that lets multi-dimensional value be defended to a coalition. Neither of these tells a salesperson what to do, in sequence, in a live engagement with a buyer. Systemic Value Selling is the method that fills that gap.

It runs across four sequential stages: Discover, Design, Justify, Align. Each stage produces an artefact that feeds the next. Diagnosis informs design. Design informs justification. Justification informs alignment. The sequence is not an aesthetic choice; reversing any two stages collapses the work of the others.

1. Discover

Discovery in a multi-dimensional setting is not a list of questions. It is the work of identifying, across the six dimensions, where the buyer is currently leaking value — paying costs they cannot see, exposed to risks nobody has named, accumulating sacrifices in dimensions the financial case ignores. The salesperson is not yet pitching anything; they are mapping the terrain the buyer already lives in.

Three things have to come out of Discover. First, which dimensions of value are activated for this buyer at this moment. Second, who in the buying coalition weights each activated dimension most heavily. Third, where each stakeholder’s current state contains a hidden sacrifice — a cost they are paying without measuring, or a risk they are carrying without naming. The artefact at the end of Discover is a one-page summary of these three things. It is not yet a proposal.

The most common failure of Discover is rushing it. A salesperson with a quota to hit naturally wants to begin proposing as early as possible. The temptation is amplified when the buyer’s lead stakeholder seems to already know what they want — the financial case is implicit, the pain seems clear, why slow down? The answer is that the lead stakeholder almost always represents one dimension. The other dimensions, with their other stakeholders and their other risks, are exactly what Discover surfaces. Skipping it produces a flat business case that travels nowhere.

2. Design

Design is where the solution gets shaped, jointly with the buyer, against the dimensions the diagnostic has surfaced. The defining word is jointly. Solutions designed in isolation and presented for approval almost always miss something the diagnostic identified, because the buyer’s knowledge of their own constraints is finer-grained than any external observer’s. Solutions co-designed with the buyer become harder to reject — not because of psychological commitment, though that helps — but because they are demonstrably fitted to what the buyer actually faces.

Design also includes the work of shaping the proposition itself. Often the standard offer, as it sits on the supplier’s shelf, does not carry value across all the activated dimensions. The proposition itself may need to be redesigned for this deal — an additional service component, an evidence package, a measurement obligation accepted, a partner brought in. This is the boundary between Sell (Pillar 2) and Design (Pillar 1) of Value Engineering. Most engagements include some of both.

The artefact at the end of Design is a shared description of the solution in the buyer’s own language, with the activated dimensions visible inside it. Not a quantified business case yet — quantification is the next stage — but a structural articulation of what is being proposed and how it addresses each activated dimension.

3. Justify

Justify is the construction of the Layered Business Case. Each activated dimension becomes a named layer. Each layer gets FAB evidence in the units that dimension speaks. Each layer is assigned a stakeholder owner who can defend it inside the buyer’s organisation. Each layer carries a risk-of-inaction argument that names what the buyer is implicitly choosing if this dimension is left unaddressed.

Co-authoring is, again, the defining move. A Layered Business Case constructed by the supplier and presented to the buyer is fragile; one constructed jointly is owned by both sides. The buyer’s stakeholder owners contribute the evidence that matters to their internal audiences, surface objections that would otherwise appear later, and walk away with material they themselves helped build. The supplier’s expertise contributes structure, evidence from comparable deployments, and the discipline of keeping each layer in its own register.

The artefact at the end of Justify is a usable Layered Business Case. Not a slide deck designed to be presented; a working document that the buyer’s stakeholders will edit, defend, and circulate. The test of whether Justify has succeeded is not whether the supplier is happy with the document. It is whether the buyer’s stakeholders are willing to take their layer into rooms the supplier will not be in.

4. Align

Align is the work of bringing stakeholders not in the diagnostic on board. Every buying coalition includes stakeholders who were not present in Discover — sometimes because they entered the process late, sometimes because their dimension only became relevant once the Layered Business Case made it visible, sometimes because the original sponsors did not yet know they would be needed. Align is where these stakeholders are met, and where the message they receive is tailored to the dimension they weight most heavily.

The sub-message per stakeholder is not a different argument. It is the same Layered Business Case, with the layer relevant to that stakeholder placed in the foreground. The CFO sees the financial layer first, with the others as supporting context. The chief sustainability officer sees the Planet & Societal layer first, with the financial layer as proof that the case clears the basic economic test. The chief operating officer sees the Risk & Resilience layer first. The structure of the argument is constant; the entry point is tailored.

The artefact at the end of Align is not a document. It is a coalition. Every stakeholder who matters to the decision has heard the argument in their own register, has the layer they need to defend it internally, and has been linked to the stakeholder owner who is already invested in the case. The deal is then in a position to be made — not because the supplier has persuaded the buyer, but because the buyer has constructed, with the supplier’s help, a decision its own coalition can defend.


Why the sequence is not negotiable

The four stages are sometimes presented as parallel activities or as iterative loops. In live engagements they often are. But the dependency is real. Design without Discover produces solutions that are well-engineered for the wrong problem. Justify without Design produces business cases for a solution the buyer never actually agreed to. Align without Justify produces consensus around a deal that has nothing to defend. The sequence holds because each stage depends on the artefact the previous stage produced.

The four stages also do not end the work. The deal closes at the end of Align. The value still has to materialise. That is the post-sale work — Pillar 3 of Value Engineering, Value Capture — which is the subject of a future article. Without it, the value identified during the sale does not show up at the customer, and the supplier loses the next deal because the first one was never proven.

For the sales organisation, the four stages of Systemic Value Selling are the operational discipline that turns the framework and the structural device into something a salesperson can actually do, in a deal, over the weeks and months a complex B2B sale takes. The capability is learnable. It is also, on current evidence, scarce.


Previous in this series: What the Layered Business Case actually does. The Methodology page sets out the framework, the discipline, and the method in one place. The SVS course teaches the method as a working capability.


Comments

Leave a comment