The playbook isn’t missing because your founder is hiding it. It’s missing because they never wrote it down. The founder’s knowledge is tacit — built from personal conviction, deep product knowledge, and years of pattern recognition. Turning it into something explicit is a real piece of work no one has done yet. That work is part of your job. The mechanism: shadow the founder, run calibration debriefs that ask why, hold a weekly cadence that turns anecdotes into documented process, and accept that a working motion takes three to six months — not thirty days.
You’re a month into the seat. You’ve onboarded, met the team, watched a few demos. Now you’re waiting. You’re waiting for the founder to send you the document — the playbook, the deck, the deal flow, the thing that tells you how this company actually sells.
It’s not coming.
What you’ll get instead is a collection of war stories, a few pitches that worked, and a general sense that the founder “just knows” when a deal is real. Across 250+ founder conversations, this is the most consistent pattern I see. The knowledge that closes deals at $500K to $5M ARR never left the founder’s head. Your job isn’t to receive it. Your job is to extract it.
Why the playbook is missing
Most founders selling early-stage deals have never written their process down because they never needed to. They were living it. They closed deals based on personal conviction, technical depth, and relationships built over years. The process worked, but the process wasn’t a process — it was them.
This is especially true for technical founders, who tend to prioritize product over sales documentation. They might have built something extraordinary, but the sales motion lives in their head. That’s not a flaw. It’s a stage. Your role is to translate it into something other people can run.
Founding AEs think they’ll be handed a playbook. What’s actually happening: they’ll be handed a problem to solve. The seat is more like a translation job than a sales job in the first 90 days.
The three-part extraction mechanism
The work splits into three pieces that have to run in sequence and then together. Skip any one of them and the others don’t produce a real playbook.
Shadow the founder on every sales call you can. But shadowing isn’t passive listening. You’re scanning for patterns. The language they use. The objections they anticipate before they’re voiced. How they handle pricing. The moments where the prospect visibly shifts from skeptical to engaged — what triggered that?
Record the calls. With permission, with transcription. Review them later. The patterns are easier to see when you can re-watch with notes. Look especially for the moments where the founder deviates from what would be the “standard” pitch. Those deviations are where the tacit knowledge lives — the unspoken rules that guide which lever to pull when.
The point isn’t to mimic the founder. It’s to understand the why behind their moves. Once you understand the why, you can build your own style on top of the same core principles.
After every shadowed call, hold a debrief. Not casual. Structured. Come prepared with specific questions based on what you saw. The goal is to force the founder to articulate the reasoning behind moves they made on instinct.
“Why did you choose that example when she pushed back on integration complexity? Was there something about her role that made you go to the manufacturing case study specifically?”
“You didn’t mention pricing until forty minutes in. Was that intentional, or did the conversation just not get there? What signals would have made you bring it up earlier?”
Frame these as collaborative problem-solving, not interrogation. You’re not catching the founder doing anything wrong. You’re building the mental model that lives in their head into something you can hold in yours.
Founders think you’re trying to copy their moves. What’s actually happening: you’re trying to understand the logic behind the moves, which is the only way the motion ever scales.
One-off calibration sessions help. A weekly cadence is what turns scattered insights into a repeatable motion. Block an hour each week with the founder. Review recent calls. Surface the patterns. Refine the pitch, the demo, the pricing posture.
This cadence is a forcing function for both of you to reflect on what’s working and what isn’t. Are certain objections coming up repeatedly? Are deals stalling at the same stage? Are buyers asking the same question in the first call?
Document what changes. Build a shared document that captures the foundational pieces: the ICP, the pain points in the buyer’s words, the value proposition, the demo flow with its turning points, the pricing structure, the three to five objections that show up in every deal. This isn’t a script. It’s a flexible framework that evolves as you learn.
Across 250+ founder conversations, the same thing shows up: the founders who can’t make this hour are the ones still selling instead of building a sales engine. If the founder consistently can’t hold the time, that’s data — not about you, about whether the motion is actually transferable yet. See the pre-sign checklist on what that means for your role.
What goes in the playbook (and what doesn’t)
Don’t try to codify everything. The playbook isn’t a script that covers every scenario. It’s a skeleton that captures the foundational elements every seller needs to understand:
In the document: the ICP, the pain points that drive purchase, the value proposition in the buyer’s language, the demo flow with its turning points, the pricing structure and how to defend it, and the three to five objections that come up in every deal.
Not in the document: every possible edge case, every founder anecdote, every one-off situation. Those live in a shared channel or a weekly Q&A. The goal is continuous learning, not exhaustive documentation.
Founding AEs think the playbook is the deliverable. What’s actually happening: the ongoing conversation about the playbook is the deliverable. The document is a snapshot of where the thinking is right now. The conversation is what keeps it alive.
The standard-deal test — are you actually ready to scale?
At some point in months three to six, you’ll have enough closed deals to ask the harder question: is the motion you’ve documented actually transferable? The test is whether your recent wins share a standard shape — standard origin (not founder’s network), standard pricing (not custom-quoted), standard solution (not one-off engineered).
If the answer is yes, you’ve done the translation work. The playbook is real and the next AE can be trained on it. If the answer is no, the motion isn’t transferable yet — and what you’ve been doing is helping the founder close better, not building a sales engine. Both are useful. They’re also different jobs with different comp expectations. Worth surfacing directly with the founder before another quarter passes.