What is a commercial playbook, and how do you build one after an exit?

What is a commercial playbook?

The record of how a company actually wins and keeps customers, written so somebody who was not there can run it.

In practice that means two layers. The visible one is the shape of the sale: the stages a deal moves through, who owns each stage, what has to happen for a deal to move, and the numbers you judge it by. And that layer is not hard to produce. Most companies have a version of it already, scattered across a CRM and a shared drive.

The second layer is the reason any of it works. Which problem you lead with and why that one. What an objection is usually about, underneath the words the buyer uses. When a deal is real and when it is somebody collecting quotes. When to walk away. So a playbook that has the first layer and not the second is a description of your process rather than a transfer of it.

How is it different from a sales deck or an SOP?

Different audience, different question, different failure mode.

A deck faces outward and argues. An SOP faces inward and lists. A playbook faces inward and decides. The confusion is understandable, because all three are about communication. But a deck that wins one meeting tells you nothing about whether the next person can win the one after it.

Scroll the table sideways to see every column.

What actually goes in one?

One list, in two halves. The second half is the one people skip.

• Stage definitions, with what has to be true to enter and to leave each one.
• The triggers that actually move a deal, taken from real deals rather than from a template.
• Ownership and escalation. Who runs each stage, who gets pulled in, and at what point.
• The numbers per stage: win rate, cycle time, and whatever your business is really judged on.
• The rules. If this is true and that is not, do this, unless the following is also true.
• The named exceptions, with the reason each one exists.
• Segment variations, because an enterprise committee and a single technical buyer are not the same sale.
• The deals that broke the rules, and what that revealed.

The first four go on paper without much trouble. The last four are what separate a playbook from a filing exercise. And they are the ones that need the person who made those calls, which is why this work is so much harder six months after that person has left.

Why does a playbook need a drawing in it?

Because the parts that matter most are relationships, and a paragraph is a poor container for a relationship.

A rule written as prose has to be read, held in mind and applied under pressure, in a meeting, while somebody else is still talking. And that is the moment it fails. The same rule drawn as two axes with a line across them, or as three stages with the condition sitting on the arrow between the second and the third, comes back in the half second a seller actually has. So the drawing does more than decorate the text. It carries the rule in the form the rule gets used in.

There is a second reason, and it shows up in the room rather than on the page. A visual model is a third object. Two people can look at it and point, so a disagreement about the sale becomes a disagreement about one box on one page instead of two people describing different companies to each other. New people learn from it because they can see where they are standing. Buyers repeat it because they can redraw it badly and still be right.

A person who had just sold their company put the underlying problem in one line, writing about the first task of the new job: there was no shared way of selling, and the two sales groups were working from different slides. Both sets of slides were correct. That is what makes it hard to catch. A disagreement about how the thing is sold does not look like a disagreement until the logic sits in one picture and the two versions can be held next to each other.

But the shape has to come out of your business rather than off a template shelf, because the relationship you are showing decides the shape. A sequence gets drawn as a sequence, a trade-off as two axes, and a scope decision as boxes inside boxes. A framework borrowed from a slide library is a picture of somebody else's argument. Your team will feel that before they can say why.

Why build one after the sale rather than before?

You should not. Before is better, and it is better for a reason that costs money.

An acquirer is buying next year's revenue, and a commercial process that only runs when the founder is in the room makes next year's revenue a question rather than an asset. So that shows up in diligence, in the structure of the earn-out, and sometimes in the price. There is a fuller version of that argument in the piece on what your sales process is worth when you sell the company.

But after the sale is not nothing, and the job genuinely changes. So the playbook stops being an execution tool. It becomes a reference. The acquirer's team uses it to stop relearning what you already know. You use it in an advisory seat to point at a specific stage instead of offering general impressions. And if there is a next company, you start it with a written account of what worked instead of running the same search again.

If the sale left you writing the playbook for a combined company, with two teams that sell in different ways, the job is different again. There is a separate piece on how a founder builds a commercial playbook after selling the company.

How do you build one when the deals are already behind you?

Backwards, from real deals, not forwards from a blank structure.

1. Pick the deals: five or six you won, three you lost, and the two nobody can explain.
2. Walk through each one out loud with whoever ran it, while somebody else interrupts and writes.
3. Mark the decision points, the moments where the deal could have gone either way.
4. Write what was weighed at each of those points, as a rule with its exception attached.
5. Only then lay out the stages, the owners, the triggers and the metrics around those rules.
6. Test the whole thing against deals it was not built from, and correct what it gets wrong.

The honest limit is worth stating, because anybody who does not state it is selling you something. Roughly eighty to ninety percent of an expert area can be structured this way. But the rest stays judgment, and the right thing to do with it is to name it as judgment rather than pretend a rule exists. A playbook that admits where it stops is more useful than one that quietly guesses.

There is a companion piece on the mechanics of that extraction, on how to codify a sales process before a handover or sale, which goes further into what a decision rule looks like and how to prove the transfer actually happened.

Do you build it yourself, bring somebody in, or buy software?

All three can work, and they fail in different places. Doing it yourself costs the least and asks the most, because the person who understands the offer best is the worst placed to hear how it sounds to somebody who does not. Bringing somebody in buys you that distance, and what you are paying for is the extraction rather than the words or the design laid over it. Software organises a playbook without deciding what belongs in one, which is why it comes after the content rather than before it.

That choice has enough in it to be its own piece. There is a fuller comparison in who should build your commercial playbook, which sets the three routes side by side and ends with the six questions worth asking before you hire anybody.

How do you get it used once you are not there?

Write it for somebody who cannot ask you what you meant, make one person responsible for it, then check whether it is being used.

The first of those is testable, and the test is the part people skip. Hand the playbook to somebody who was not in the room while it was written, give them a live situation, and watch what happens. If they have to interpret a line, the line is not finished. Founder shorthand is the usual culprit, because a phrase carrying ten years of context for you carries nothing for a seller in month two. Qualify properly is not an instruction. Ask who signs, ask what happens to them if nothing changes this year, and walk away if neither question gets a straight answer, is an instruction.

The second is that nobody learns a decision by reading it. They learn it by making it and being corrected, which means running the objections out loud with the people who will face them, walking a live deal through the rules with the document open, and doing it while you are still reachable. A new hire who onboards by shadowing you has learned you, and you are the part that is leaving.

The third is smaller than it sounds. One person owns the document. Deals get marked against the rule that qualified them, so you can see which rules get used and which get quietly routed around. And a rule everybody ignores is either wrong or badly written, which makes it information rather than a discipline problem.

What goes wrong most often?

Four failures, and they are not equally expensive, because the first one quietly invalidates everything built on top of it.

Writing the company you meant to build. You sit down and describe the sales process as it ought to work, and six months later you find that your two best people have been closing on a different path, one nobody wrote down because it was never officially the process. So start from the deals rather than from the org chart. Interview whoever wins most, have them narrate three closed deals end to end, and follow the path they actually took.

Length. A fifty-page document is a decision to be ignored. The parts that change an outcome are the qualification rule, the objection that genuinely kills deals, the position you take against the obvious alternative, and what a real deal looks like at each stage. And everything else is material you will maintain forever and nobody will open once.

Leaving the picture out. A text-only playbook asks a seller to reconstruct your argument from paragraphs while a buyer waits, and under that pressure people fall back on the generic pitch they already knew. The rule that has to survive the meeting needs to be drawable on a whiteboard by somebody who is not you.

Writing it for the acquirer rather than for the team. A document built to look complete in diligence reads like a brochure, gets approved by people who will never run a deal, and sits unopened on the floor where it was supposed to work. So write it for the seller in month two. It will satisfy diligence anyway, because what diligence is testing is whether the revenue runs without you.

What is it worth in an advisory or board seat?

It is the difference between having opinions and having a diagnosis.

With a playbook in front of you, a slipping number has a location. Win rate has fallen in one segment, at one stage, and here is the rule that stage runs on and here is what changed around it. But without one, you are the former founder saying it feels like something is off in the mid-market, which is usually true and almost never actionable.

The same thing applies if you are not staying. So write it for somebody who cannot ask you what you meant. Build relationships and demonstrate value are not instructions. A monthly review on a fixed date, against usage against the goal that was agreed, with one expansion question asked every time, is an instruction. And the test for every line is whether a competent stranger could act on it tomorrow.

What does the work involve, and what does it cost?

You can run this yourself, and after an exit you have the one thing the work needs, which is time to think. The reason it stalls is not effort. It is that the person who understands the offer best is the worst placed to hear how it sounds to somebody who does not, and after twenty years of making the call by instinct, naming what you weigh is genuinely difficult from the inside.

A worked example of the result, rather than of the document. A machine manufacturer, two people, a genuinely good and genuinely technical product. Every deal turned into a fresh argument about their machine against a cheaper one, and the founder made that argument personally every time. The rule underneath it, once it was named, was one sentence: you buy the first machine on price, and from the second machine on, you buy service. In the year that followed the company went from two people to twenty-five. The sentence did not do that on its own and it would be dishonest to say it did. What it did was stop the argument having to come out of one person's mouth to land.

If you want it done with you, this is the shape of it at Strategem. The extraction runs as structured interviews on your own real cases, won, lost and difficult, using grounded qualitative method from an organizational psychology PhD. We draw while we listen, and the bar is the moment somebody says, that is exactly what I do, I just could never name it.

The Clarity and Roadmap package, which includes a workshop, starts at €8.000.

Strategem was founded by Dr. Fritz Hermann, who holds a PhD in organizational psychology and spent a decade as a CMO, with work across banks, insurers and Premier League clubs. The same work runs on expert judgment that has never been written down, on a founder the team keeps pulling into the same sales moment, and on an argument a champion has to carry without you.