Your wins are sitting in a folder. The Proof Engine turns customer results into assets buyers actually see: captured on a trigger, structured buyer-first, cut into five formats, and scheduled into channels you already run.
A great project wraps. Someone writes a case study, legal approves it, it gets a PDF and a page nobody visits. The single most persuasive thing you own, proof that you deliver, gets published once and retired, while sales keeps answering 'who else have you done this for?' from memory.
Your wins are sitting in a folder. The Proof Engine turns customer results into assets buyers see everywhere, on a schedule. Built once, documented in your standard work, and run by your own team week after week.
Proof is the currency of industrial buying, and most companies are rich in it and broke at spending it. This playbook installs the engine: a capture process that makes case studies routine, a format library that turns each one into a dozen assets, and a distribution calendar so proof circulates instead of sitting.
of decision-makers say thought leadership is a more trustworthy basis for judging a company's capabilities than its marketing materials. Customer stories are the most trustworthy material you own, if buyers ever see them.
of a B2B buying group's total buying time is spent meeting with potential suppliers. Proof has to circulate where buyers research without you, because that is where most of the decision happens.
At any given time roughly 95% of category buyers are not in market. A story that re-airs quarterly reaches the buyers the original ran past, right as some of them become the 5%.
Parked proof does not hold its value. Every quarter the wins stay in a folder, the same five things keep happening.
The Proximity Audit counts what you own against what actually circulates, then ranks what to fix first. That is the point of starting there.
An install only sticks when it has owners. Here is who this playbook belongs to inside your company, and what each of them walks away with.
A GM or VP who protects the calendar slots and backs the no-fabrication rule.
OutcomeDeal-killing objections answered with evidence instead of discounts.
Your marketing lead, who owns the proof register, the rotation, and the freshness rule.
OutcomeA schedule and a register instead of a folder and guilt.
The rep or service lead who sends the capture ask and books the twenty minutes.
OutcomeA leave-behind in their own voice for the deals they are working right now.
Service and project managers who flag wins while they are fresh.
OutcomeA two-line nudge to send instead of a writing assignment.
An illustrative composite drawn from real engagement patterns. Company details invented; the shape of the change is the point.
Story structure, the repackaging map, and the calendar.
Customer interviews, production, and posting.
Proof assets in active circulation each month.
Proof engines fail at distribution, not production. Each week makes one decision the next week depends on, so the sequence is fixed and the scope is too.
Every proof asset takes the circulation test: a buyer, a channel, a date, or it is parked. One ranked work plan comes out.
Why firstThe headline count, owned versus circulating, is the baseline day 60 gets judged against; the ranking picks the stories worth six weeks.
Tear down the vendor-hero draft, sentence subjects counted aloud. A five-beat story spine with a test per beat; one spine drafted.
Why before captureInterviewing without the spine wastes the customer's twenty minutes. The beats say exactly what to ask for: situation, problem, turn, numbers, quote.
Trigger moments mapped, the ask sent by the relationship owner, the 20-minute interview rehearsed then run, the approval path tiered.
Why nowFresh wins talk; stale wins stall. The approval path is designed before the interview so the story cannot die in review afterward.
One transcript becomes a case study, a one-pager, a post series, a sales leave-behind, and a partner kit, each with a named reader.
Why before schedulingFormats let one capture serve five readers and five channels. Every claim traces back to the transcript, which keeps the proof honest.
A proof slot in every channel you already run, the next 90 days dated, a quarterly rotation with a re-run rule.
Why before the registerA schedule, not a folder: distribution is the product. Re-runs work because the audience that missed a story last quarter is new now.
A living register: every asset owned, freshness-dated, slotted. Gaps checked against your objection map. The Proof Engine Manual assembled and owned.
Why lastEngines need an operator and a maintenance rule. Freshness dates and the gap check keep day 365 from looking like day one.
Dated slots in the last 30 days against the kickoff baseline, queue items closed, new captures done, the register flagging what is next.
Why it mattersCirculation against the baseline is undeniable: the same proof, finally seen by buyers. The count makes the expansion case.
Every week compiles into the Proof Engine Manual: the named product your team owns, reruns, and keeps feeding long after the install ends.
This playbook lives in System 03: Own, the part of the method that answers one question: What do we own that compounds? Most companies install it alongside one or two related playbooks in a 90-Day Install.
Share this page with your leadership team. If it names your problem, the Proximity Audit will tell you whether this playbook should be your first install or your third.
Installed on one product line first, then yours to rerun across every line you own. Not sure it's the right first move? Start with the Proximity Audit ($7,500, credited toward an install): all fifteen areas scored and a ranked roadmap.
Book a Proximity Audit Ask about this playbook →