A sales playbook that lives in the founder's head is a single point of failure. Here is how to get it out, write it down, and wire it into HubSpot or Salesforce so your next reps ramp in months, not quarters.
The short version: process makes average reps repeatable. Everything below is how to build that process.
A sales playbook that lives in the founder's head isn't a playbook. It's a single point of failure.
I've seen founders spend six months onboarding BDRs through osmosis. Shadow the rep. Watch some calls. Read a Notion doc that's 70% out of date. Then they're live with no defined sequences, no objection handling framework, no clear ICP at the attribute level.
The ramp takes five months. Half the cohort churns. The cycle repeats with the next hire.
The best BDR programs are built before the first rep is in seat. ICP defined at the attribute level, not just firmographic. Messaging indexed to persona and pain point. Sequences with actual timing logic, not "reach out until they respond." Stage criteria that any rep can execute against, not just the ones who've been around long enough to absorb it.
Process makes average reps repeatable. Write it down.
Founder-led sales works because one person holds the whole model. Hiring breaks it because nobody wrote the model down.
The founder qualifies on instinct: which pains are real, which buyers stall, when to walk. None of it is written, so new reps learn it by shadowing, slowly and with gaps.
"Series B SaaS, 50 to 500 employees" isn't an ICP a rep can act on. Without trigger events, tech stack and pain signals at the attribute level, reps spend their weeks on bad-fit accounts.
Each rep improvises a pitch. Results then vary by rep instead of by process, and you can't coach what isn't standardized.
No step count, channel mix, spacing or exit rule. Reps over-touch good accounts, under-touch great ones, and burn the domain.
If "Qualified" has no exit criteria in the CRM, only people who've been around long enough know the rule. New reps push deals forward early, the forecast inflates, and the founder ends up re-qualifying everything in pipeline review. Your sales stages need checkable criteria, not vibes.
The median SDR now ramps in about three months. If yours take five, the gap is your playbook, not the market.
| Metric | Weak | Acceptable | Strong | Source |
|---|---|---|---|---|
| SDR ramp time | 5+ months | ~3 months | Under 3 months | Bridge Group 2025Avg 3.0 months; 3.8 at the 2014 peak |
| AE ramp time | 8+ months | ~6 months | 4 months or less | Bridge Group 2026Avg 6.2 months, highest in study history |
| SDR annual attrition | Above 57% | 21% to 40% | Under 21% | Bridge Group 2025Median 40%; middle 50% is 21% to 57% |
| SDRs at quota | Under 50% | ~60% | 70%+ | Bridge Group 202560%, lowest in study history |
| AEs at quota | Under 40% | ~48% | 57%+ | Bridge Group 202657% in the most AI-engaged teams vs 39% in the least |
| Annual pipeline per SDR | Under $1.9M | ~$3.8M | Above $6.4M | Bridge Group 2025Median $3.78M raw pipeline |
| Founder-closed customers before first hire | Under 5 | ~10 | 10+ with a written pattern | Mercury, 2025"At least 10," depending on deal size |
| Win rate on qualified pipeline before hiring | Under 15% | 15% to 25% | 25%+ | The GTM NewsletterFounder-led sales readiness signal |
Sources: The Bridge Group, SDR Models, Motions and Metrics 2025 (351 B2B companies); The Bridge Group, AE Models, Motions and Metrics 2026 (158 B2B companies); Mercury, handing off founder-led sales; The GTM Newsletter. Weak and strong cutoffs are JayOh thresholds anchored to the published medians and ranges.
Write it from evidence, then enforce it in the CRM. A playbook that only lives in a doc loses to the CRM every time.
ICP Tier, Trigger Event and Primary Tech Stack, then set the tier with a workflow or lead scoring. Salesforce: add Account fields plus a formula field for ICP_Tier__c. Report on win rate by tier monthly.Most playbooks fail at adoption, not authorship. Short, enforced and current beats long and complete.
Score your playbook, then put a dollar figure on a slow ramp. Change any input and the numbers update.
Math: ramp is treated as linear, so a rep produces about half their full output while ramping. Months lost per rep = (current ramp minus target ramp) / 2. Salary cost = hires x months lost x monthly cost. Pipeline delayed = hires x months lost x monthly pipeline. Extra churn = hires x (current attrition minus target attrition) x (half of current ramp x monthly cost + recruiting cost). The $315K default is the Bridge Group 2025 median of $3.78M annual pipeline per SDR, divided by 12.
Copy the one-page skeleton. Or let Claude draft v1 from your founder's call transcripts with the skill below.
SALES PLAYBOOK v1 | Owner: ____ | Version: 1.0 | Last reviewed: ____ 1. ICP (attribute level) - Industry / segment: - Employee band / revenue band: - Trigger events (new exec, funding, acquisition, tool change): - Tech stack signals: - Pain signal visible from outside: - Disqualifiers (from lost deals): - CRM fields: ICP Tier, Trigger Event, Primary Tech Stack 2. PERSONAS x PAINS (3-4 personas) Persona | Pain in their words | Hook | Proof point | Discovery question 3. DISCOVERY GUIDE Situation -- Pain -- Impact -- Decision process -- Timing (paste the founder's best-performing questions, word for word) 4. OBJECTIONS Objection | Buyer's words | Reframe | Proof | Tested? Y/N 5. STAGES + EXIT CRITERIA Stage | Exit criteria (checkable facts) | Required CRM field Discovery | pain confirmed in buyer's words; economic buyer named | Pain__c, EB__c Evaluation | success criteria agreed; next meeting booked | Success_Criteria__c Proposal | budget confirmed; decision date set | Budget__c, Decision_Date__c 6. SEQUENCES (per persona) Step | Day | Channel | Template | Exit rule (reply / meeting / DQ) 7. RAMP PLAN Days 1-30: ICP, product, pitch -- Gate: pitch certification Days 31-60: live sequences, discovery -- Gate: discovery role-play Days 61-90: full motion -- Gate: objection drill Leading indicators: activities, conversations, meetings held / week 8. PROOF LIBRARY Case | Metric | Persona it lands with | Approved to share? Y/N 9. GOVERNANCE Review cadence: monthly (first quarter), then quarterly Inputs: win/loss reviews, stage conversion by rep vs founder baseline Change log: date | what changed | why
sales-playbook-builderSettings, then Capabilities. Make sure code execution and file creation is on. Under Skills, click Upload skill, choose the .zip, and toggle it on.
Save the file as ~/.claude/skills/sales-playbook-builder/SKILL.md, or in .claude/skills/ inside your repo.
Skills are available on Claude Pro, Max, Team and Enterprise plans. New to skills? Read how to use skills in Claude.
--- name: sales-playbook-builder description: Turns a founder's call transcripts, deal notes and CRM exports into a v1 sales playbook a new BDR or AE can execute, then grades readiness and lists the gaps. Use when someone says "build our sales playbook", "get the playbook out of the founder's head", "onboard our first reps", "turn these call transcripts into a playbook", or is moving from founder-led sales to a sales team. --- # Sales Playbook Builder You turn what the founder already knows (calls, notes, won and lost deals) into a written playbook with the 8 components below, mapped to CRM fields so it can be enforced. You never invent what the evidence does not show. ## Inputs to ask for (use whatever the user provides) 1. Call transcripts or recordings summaries from the founder's last 10 to 20 deals (won and lost). 2. Closed-won and closed-lost list with company, industry, size, deal value, cycle length, and loss reason. 3. Current pipeline stages and what the founder thinks each one means. 4. Any existing pitch deck, one-pager, Notion doc or email templates. 5. CRM in use (HubSpot or Salesforce) and plan tier, if known. If fewer than 10 closed deals are provided, say so at the top: the pattern may not be stable yet. ## Step-by-step 1. **Inventory the evidence.** List each source you received and how many deals it covers. Count won vs lost. 2. **ICP at the attribute level.** From won deals, extract the shared attributes: industry, employee band, tech stack, trigger event, buyer title, pain indicator. From lost deals, extract disqualifiers. Every attribute must cite at least two deals. Propose CRM fields (HubSpot company properties or Salesforce Account fields) and an ICP Tier rule (Tier 1, 2, 3, Disqualified). 3. **Personas and pains matrix.** For each buyer persona seen in the evidence, list the top pains in the buyer's own words (quote them), the proof point the founder used, and one discovery question that surfaces the pain. 4. **Discovery guide.** Pull the questions the founder actually asked in calls that moved forward. Order them: situation, pain, impact, decision process, timing. Quote the best phrasing. 5. **Objection handling.** List every objection heard more than once. For each: the buyer's words (quoted), what the founder said, whether the deal advanced, and a recommended reframe. Mark reframes with no evidence of working as UNTESTED. 6. **Stages with exit criteria.** For each stage, write the exit criteria as checkable facts (for example: pain confirmed in buyer's words, economic buyer named, next meeting booked). Map each criterion to a required CRM field: HubSpot conditional stage properties, or Salesforce Path key fields plus a validation rule for hard gates. 7. **Outbound sequence.** Draft one sequence per primary persona: number of steps, channel per step, day spacing, exit rules (reply, meeting booked, disqualified). Note: in HubSpot a contact can be in only one sequence at a time. 8. **Ramp plan.** A 30/60/90 day plan with certification gates (pitch, discovery role-play, objection drill) and leading indicators. Benchmarks for reference: SDR ramp averages 3.0 months (Bridge Group 2025); AE ramp averages 6.2 months (Bridge Group 2026). Five or more months for an SDR is a red flag. 9. **Readiness grade.** Score each of the 8 components 0, 1 or 2 (0 missing, 1 partial, 2 complete with evidence). Total out of 16. 13 to 16 = Ready to hand off. 8 to 12 = Hire, but founder stays on late-stage calls. 0 to 7 = Not ready: founder keeps selling and documents first. ## Output format (always this order) - **Evidence summary** (sources, deal counts, confidence: High, Medium or Low) - **1. ICP and disqualifiers** (table: attribute, value, deals cited, CRM field) - **2. Personas and pains** (table: persona, pain in their words, proof point, discovery question) - **3. Discovery guide** (numbered questions) - **4. Objection handling** (table: objection, buyer quote, reframe, status Tested or UNTESTED) - **5. Stages and exit criteria** (table: stage, exit criteria, required CRM field) - **6. Sequences** (per persona: steps, channel, day, exit rule) - **7. 30/60/90 ramp plan** - **8. Proof library** (only proof points that appear in the inputs) - **Readiness score** (component scores, total of 16, verdict) - **Missing evidence** (what to collect next, and from whom) ## Guardrails - Quote the input as evidence for every claim. If there is no quote or deal behind it, put it under Missing evidence instead. - Never invent numbers, customer names, case studies or proof points. - Never fill a gap with generic best practice without labeling it SUGGESTED, NOT FROM EVIDENCE. - Keep each play short: one situation, one action, one example. - Flag conflicts between what the founder says a stage means and what the deals show. Built by JayOh (jayoh.io). Framework from https://jayoh.io/sales-playbook/
Straight answers to the questions founders ask before their first sales hires.
Eight components: an ICP defined at the attribute level with disqualifiers, a persona x pain messaging matrix, a discovery guide, objection handling, stage definitions with exit criteria, sequences with timing and exit rules, a 30/60/90 ramp plan, and a proof library. Add an owner and a review cadence so it stays current.
When the motion is repeatable and written down: roughly 10 founder-closed customers with a shared pattern (Mercury), a 15% to 25% win rate on qualified pipeline (The GTM Newsletter), and a v1 playbook. Hire two reps at once so you can separate the person from the process.
The Bridge Group's 2025 report puts the average SDR ramp at 3.0 months, the lowest since 2010. AEs average 6.2 months per its 2026 report. If your SDRs take five months or more, the usual cause is a missing playbook and a CRM that doesn't enforce the process.
Both, but the CRM is the enforcement layer. Keep the narrative in one doc, and put stage exit criteria as required fields, messaging as templates and snippets, and discovery as in-record playbooks in HubSpot or Path guidance in Salesforce. Reps follow whatever the CRM asks for.
Monthly for the first quarter after launch, then quarterly. Feed every win/loss review and stage-conversion report back into it, and keep a change log so reps know what changed and why.
AI can draft one from transcripts, pulling discovery questions, objections and buyer language, but the founder has to validate it. The free sales-playbook-builder Claude skill on this page quotes evidence for every claim and lists missing evidence instead of inventing it.
Founders don't fail at handing off sales because they hire badly. They fail because the playbook was never written, so every new rep has to rediscover it, and the founder ends up re-selling deals in pipeline review.
The fix isn't a bigger doc. It's a short playbook built from real deal evidence and enforced by the system reps already live in. If you're planning those hires now, pair this with sales capacity planning and our guide to RevOps for founders. Reps who need help day to day can start with Claude Cowork for BDRs, and our sales enablement team can build the whole system with you.
JayOh builds the playbook, the CRM enforcement and the ramp dashboards as one system, so your next cohort ramps on process instead of osmosis.
Further reading: HubSpot Knowledge Base: Use playbooks; Salesforce Trailhead: Optimize Sales Processes with Path; The Bridge Group SDR (2025) and AE (2026) research reports; Mercury; The GTM Newsletter; SaaStr; Spekit.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
