Transfer a founder's sales playbook by making decisions observable, recording the evidence behind them and testing whether another person can apply the method. A script captures words. A usable playbook also explains which account to pursue, when an exception applies and what to do when the evidence is incomplete.
The original LinkedIn post discussed a dispute about company knowledge. This article develops the operational lesson without relying on the allegations: a business becomes easier to hand over when its sales decisions can be understood outside one person's memory. The method below is a proposed working process, not a guarantee of faster ramp or a particular close rate.
For provider selection, use the GTM agency evaluation guide. This page focuses on transferring the work after its scope is clear.
in
“Apple says OpenAI stole its secrets. Here are the 10 craziest facts from the new filing:”
Select One Repeatable Sales Job
Start with a narrow job such as qualifying an inbound request, preparing a discovery call or deciding the next step after a pilot. Describe its inputs and the result another person should produce. Avoid beginning with an entire sales manual, where important decisions disappear among instructions nobody can test.
Choose examples of the work you are authorized to use. Include successes, failures and ambiguous cases. A collection of wins alone hides the conditions under which the approach should be rejected. Keep customer information limited to what the team needs, and use the appropriate access controls for recordings and account material.
Extract the Reason Behind the Decision
Review a real case with the founder. Ask what they noticed, which alternative they rejected and what would have changed the decision. Capture the evidence separately from the interpretation. A statement that an account felt wrong is difficult to transfer; a specific mismatch between the required implementation and the buyer's capacity is something another seller can examine.
Use a consistent record: situation, evidence, decision, reason and unresolved question. Preserve uncertainty rather than rewriting a messy conversation into a confident story. When the reason depends on experience that has not yet been articulated, flag the case for another review instead of presenting a guess as a rule.
Turn Examples Into a Play
Write the smallest instruction that connects the input to an observable action. Include a trigger, the information to check, the permitted next step and the point at which the seller should ask for help. Attach a worked example and a counterexample. The counterexample prevents a useful pattern from turning into a rule applied to every buyer.
For illustration, a qualification play might require a documented problem, evidence that the offer can address it and agreement about the purpose of the next conversation. Missing evidence produces a follow-up question. A known mismatch produces a clear explanation and a decision to stop. This is a sample structure, not a universal qualification framework.
Put the Play Where Decisions Happen
Connect the instruction to the relevant CRM record or call preparation document. Define the fields that preserve the evidence and the owner who resolves exceptions. A separate document is still useful as a reference, but the current instruction should be discoverable at the moment the seller needs it.
Keep one current version and a short change history. Record why a rule changed and which examples motivated the change. Avoid silent edits that leave one seller following an old sequence and another following a revised one. The purpose of versioning is to explain the work, not to create administrative overhead.
Test the Handover on Unseen Cases
Give a second seller an appropriate case that was not used to write the play. Ask them to make the decision and explain the evidence. Compare their reasoning with the intended criteria. A disagreement can reveal a missing instruction, a bad example or an assumption the founder never stated.
Revise the play and test again on another case. Passing a rehearsal does not prove commercial success. It does show whether the instruction can be understood and applied without the founder supplying missing context throughout the exercise. Keep the rehearsal outcome distinct from live sales results.
Review Exceptions Without Rewriting Everything
Collect cases where the instruction was unclear or led to an unsuitable next step. Review them with the person accountable for the process. Change the rule only when the evidence supports the change; one unusual objection does not necessarily justify replacing a working approach across every account.
Measure adoption and business outcomes separately. Track whether sellers can find and apply the play, how often they need clarification and which exceptions recur. Evaluate meetings, opportunities and revenue using their own definitions and observation periods. Do not attribute a change in close rate to documentation without considering other changes in the sales motion.
Know What Remains With People
A playbook cannot eliminate judgment or remove the need for a viable offer. It helps a team preserve what it has learned while leaving room for a buyer whose situation does not fit the examples. The founder should remain available for decisions the process does not yet cover.
The first useful deliverable is one tested play with evidence, an owner and a review point. Expand only when another person can use it and explain its limits. That is a more meaningful handover than a large folder whose contents have never been applied.
The GTM strategy consulting service describes Growth Cab’s engagement scope and fit.
