Most founders write a GTM playbook for their first sales hire. This is the wrong sequence. The playbook written before the hire is three times more useful than the one written after. The one written after is assembled under pressure, during onboarding, by someone who is also learning the product.
The pre-hire playbook benefits from something the post-hire playbook doesn’t have: the founder’s full attention and the ability to document without compromise. After the hire, the documentation gets done in gaps. Key sections get abbreviated. The urgent displaces the complete.
The Pre-Hire GTM Playbook assembles five components the founder has been building across the GTM chapter. This article is for the founder planning to hire their first sales rep within 12 months.
Why GTM Playbooks Get Written Too Late
The obvious failure mode: the first sales hire joins and spends their first week asking the founder questions that should have been written down. The founder answers the same five questions three times per week for the first month. By the time the hire has the context they need, they’ve spent 20 hours of the founder’s time reconstructing it.
The less visible failure is that the playbook written reactively is incomplete by definition. It contains answers to the questions the first hire asked. It doesn’t contain the context the second hire would need, the third objection pattern that didn’t come up in the first month. The ICP nuance that takes a founder three months to explain is absent as well.
The deepest failure is that reactive documentation is rarely revisited. It reflects the GTM knowledge at the time of the first hire. As the product and market evolve, the playbook doesn’t. Two years later, the sales team is onboarding from a document that describes a product that no longer exists.
The Pre-Hire GTM Playbook
The playbook has five sections. Each one assembles knowledge from work the founder has already done across the GTM chapter.
Section 1: Who we sell to and why they buy
Section 1 is the ICP definition from the product strategy work, translated into sales-process language.
The engineer who built the product needs a technical ICP. The sales rep who sells it needs a behavioral ICP. It specifies which buyer type converts, what triggers a buying event, which qualification criteria reliably predict close, and what success looks like for customers.
Section 1 contains:
- The two or three buyer types most likely to convert
- The trigger events that create buying intent
- The qualification criteria from the sales process documentation
- The customer success pattern that makes the product stick
Section 2: How we run the sales process
Section 2 is the sales process documentation from Article 22, reformatted for a new rep’s first week.
The purpose is not to reproduce Article 22 verbatim. It’s to give a new rep enough structure to run their first call without asking the founder first. The structure they need:
- What to do in the first five minutes of a discovery call
- Which questions to ask that qualify the deal in or out
- What the demo shows and in what order
- How to handle the three most common objections
- How to close toward a next step
Section 3: What we charge and how we discuss it
Section 3 is the pricing framework from Article 23, reduced to what a sales rep needs to know in a commercial conversation.
The rep doesn’t need the pricing decision methodology. They need:
- The price point and any approved discount floor
- When to introduce pricing in the conversation
- How to handle the “that’s too expensive” objection
- What commercial terms are flexible and what are not
Section 4: How we compete
Section 4 is the competitive context from the CI system work in Chapter 03, filtered for sales relevance.
Not all competitive intelligence belongs in a sales playbook. The section contains what a rep needs to win a deal that includes a competitor in the evaluation:
- The two or three competitors that appear most often in evaluations
- The positioning contrast that works for each
- The questions to ask that surface what the customer values
- The objections that appear when a competitor is in the conversation
Section 5: What success looks like in the first 90 days
Section 5 sets expectations for the ramp period. A new sales rep without a defined ramp expectation doesn’t know if they’re performing.
The expectations include:
- Activity targets for the first 30 days (calls, meetings, pipeline generation)
- Deal milestones for the first 60 days (specific deal stages expected to be reached)
- First close expectation for day 90 (and what the expectation is if it slips)
How the Living Library Assembles the GTM Playbook
The week before the first sales hire starts, the founder needs the whole go-to-market approach in one place. Not scattered across six documents and a year of memory. The GTM Playbook is already that place. The Library has pulled the five components together into one current artifact the rep can actually work from.
Those components live across Collections: the ICP definition and positioning statement, the sales process and pricing notes, and the competitive context. When any one changes, say a pricing update or an ICP refinement, the playbook reflects it. It does not go stale the day after it was written.
So the new rep does not have to interrupt the founder for every answer. On day one they can ask the Conductor, Kiluma’s context-aware AI: “What are our top three objections, and how do we handle them?” It pulls the answer from the sales process documentation, and the founder’s calendar stays off the critical path.
The Sales Process Documentation from Article 22 is the primary source for Sections 2 and 3. The playbook assembles that documentation into a format optimized for a new rep’s first week.
Write Section 5 First
Section 5 (ramp expectations) is the most commonly skipped section and the most important for a new hire’s first week.
Write it before the hire is made. Decide now: what does a successful 90-day ramp look like for your first sales rep? Write it down. Show it to the candidate during the interview process.
The conversation that happens when you share ramp expectations in the interview is one of the most useful interviews you’ll have.
If Your First Sales Hire Joined Tomorrow, What Would They Have?
If your first sales hire started tomorrow, what document would you hand them that would let them run their first call without calling you? Try Kiluma free for 14 days at kiluma.ai.