1The problem
Most playbooks don't survive contact with a live deal.
Most teams already have some form of playbook. It just doesn't show up when the seller is in the deal. Stages mean different things to different reps. Discovery changes depending on who's running it. A deal gets marked Proposal Sent because someone sent a deck, not because the buyer asked for one. Follow-up runs on memory. Managers each inspect their own way.
A playbook that sits beside the work, in a folder, never changes any of that. It has to live inside the work.
2The shift
Written properly, a playbook is data, not a document.
Something has changed. A playbook used to be a document people were meant to read and remember. Written properly now, it's structured data a machine can read. Once the process, qualification, method and the behaviours that define good are codified, that same data drives the next best action, surfaced for the seller inside the live deal, in the CRM, in the flow of work, not in a separate tool no one opens. The catch: AI is only as good as the architecture underneath it. Vague guidance in, vague prompts out. The playbook is that architecture.
Get the architecture right, and the next best action follows.
3The architecture
The sales system, not a document.
We don't ship a static PDF. Underneath every good playbook sit four things: three are the moving parts of how a deal is won, and the fourth is the standard they are all measured against.
1
Sales Process
Clear stages, stage purpose and exit evidence.
So everyone knows what progress should look like before a deal moves forward.
2
Sales Method
What sellers need to know, show, do and say at each stage.
So discovery, demos, proposals and follow-up stay connected to how buyers decide.
3
Sales Qualification
Deal scorecards, risk flags and manager prompts.
So managers can inspect buyer evidence and coach the next best action.
4
Behavioural best-practice rubric
The defined standard of good that the other three are scored against.
Set against the rubric, these four become the architecture that decides the next best action: for this deal, at this stage, right now. Same source of truth whether a manager gives the steer in a deal review or AI surfaces it in the CRM. No deck that gets admired and then ignored.
What good looks like
4
Behavioural best-practice rubricthe standard each one is scored againstNot a document
{ }Structured data
The playbook as a model a machine can read.
CRM + AI
In the flow of work
Where your reps already are, no separate tool.
The output
Next best action
This deal · this stage · now.
The architecture decides the next best action: given by a manager in a deal review, or surfaced by AI in the CRM. Same source of truth.
A real system, not a slide
.avif)
Codify the sales motion
Stages, goals, approach and exit criteria, so everyone knows what progress should look like.
.avif)
Standardise deal judgement
Qualification definitions, questions and scoring rubrics, so teams inspect buyer evidence, not seller opinion.
.avif)
Anchor messaging in buyer problems
Problem, pain, root cause, promise and payoff, so messaging and proposals stay connected to what buyers care about.
4In the week
Built into the week, not beside it.
In practice this becomes a live CRM workflow, deal scorecards, call guidance and an inspection rhythm the team can actually run, where your reps already work.
The next best action is surfaced in the deal, by a manager or by AI reading the same architecture. No extra tabs.
1
Codify
Stages, goals, approach and exit criteria, what progress should look like.
2
Embed
Fields, checklists and call guides live inside Salesforce or HubSpot.
3
Coach
A monthly deal-review huddle and a manager cheat-sheet of risk cues.
.svg){kind=logo}
Your system lives where your reps live. No extra tabs.
5Who it's for
Two starting points, one system underneath.
Use it when
Turn founder selling into something the team can repeat
Make the method show up across the whole team
6Proof
What changed for the teams we built these with.
We landed our first enterprise deal in eleven weeks. Now every deal runs on a repeatable process, not crossed fingers.
James FellFounder & CEO, Credit Canary
With a turn by turn system in HubSpot, we're executing at a new level. Win rates are up, forecasts are reliable and we've got a clear path to the next revenue ceiling.
Callum MurrayFounder & CEO, Amiqus
Closing Foundry helped us bring structure to complex enterprise deals. We moved from judgement led selling to a clearer way of qualifying, progressing and inspecting opportunities.
David BoonFounder & CEO, Dijuno
7Where it fits
Build playbooks your team will actually use.
Where Playbooks fit
Playbooks are the Enable layer of Closing OS, the point where the plan becomes behaviour in live deals. Built on their own, a Playbook helps. Built inside the full system of Design, Enable and Run, it holds.
How to start
You can build Playbooks as a focused Enable sprint, or as part of a Closing OS Install. If you already know the process, qualification and messaging need building into the workflow, we can scope a Playbooks sprint. If what isn't working isn't clear yet, start with 5 Days to Scale.
8Questions
Frequently asked questions
Closing Foundry Playbooks are practical sales execution tools built around how your team actually sells. They turn qualification, discovery, buyer evidence, objection handling, next-step discipline and manager inspection into usable guidance for live deals, not documentation that sits in a shared folder.
Playbooks are for founder-led and scaling teams where selling is too dependent on individual judgement. They're most valuable when new hires need a clearer standard to ramp against, managers need a consistent coaching tool, or the team needs one agreed way to work opportunities through the pipeline.
A generic playbook describes a sales approach. Closing Foundry Playbooks are built around your ICP, deal stages, buyer evidence, CRM workflow and management rhythm. The measure of quality isn't how thorough the document is. It's whether the behaviour shows up in live opportunities the week after it's built.