Sales playbook foundations

Purpose

Writes down what good looks like for the sales team, so the playbook works when the leader is absent or gone, a new rep can succeed from the document alone, and the team agrees on the same standard.

Produce a playbook that is written, agreed, built from real calls and deals, and owned. Put people first, because people are the ones who run the plays. Show the math behind every target. Make ramp and qualification evidence explicit, so promotion, termination, and onboarding decisions do not depend on memory.

When to use

• The sales team needs a written playbook that works without the leader present, built from real calls and deals.
• A new rep needs to succeed from the document alone, and the team needs one agreed standard.

Route elsewhere when:

• The question is hiring, offer or close decisions for a sales role. Use sales-hire-offer-close.
• The question is succession of leaders. Use bench-strength-and-succession.
• The question is coaching individual deals or the qualification gate itself. Use deal-qualification-gates.
• The question is CRM field or stage configuration. Use revops-salesforce, or revops-data-governance for data standards.
• The question is territories, capacity plans, or org structure. Use gtm-planning-org-design.
• The question is messaging, battlecards, or outreach copy. Use positioning-messaging-designer or sdr-outbound-rules.
• The question is discount policy. Use deal-desk-operations.

Inputs

1. Recent calls, deals (won and lost), and any existing sales material. Use real examples, not aspirations.
2. The company's values, and the leader's own view of what success looks like.
3. Quota or targets, average deal size, close rate, and pipeline coverage, if known.
4. Interview access to reps and managers for the Prospect, Problem, Process, and Product sections.
5. Recent hiring and ramp data: months to first meeting, first qualified opportunity, and first win, by hire cohort. If none exists, say so.
6. The current methodology in use, if any, and the CRM fields that record it.

If targets, close rates, or ramp data are missing, leave those figures as explicit blanks to be filled, not invented.

Procedure

Principles

• Write it down. A playbook in someone's head is not a playbook.
• Build from reality. Document how the team actually sells, from real calls, deals, and rep language. Do not write the ideal process that nobody runs.
• People first. Most playbooks start at product and never reach people. Draft people first, so every later section has someone to execute it.
• Show the math. Every target should be re-derivable by the rep who has to hit it.
• Evidence over time. Ramp and qualification are gated by evidence, not by how long someone has been in the role.
• Keep the leader involved. Outside help can draft and structure. The leader must shape the standards, or the playbook will not be adopted.
• Own it. A playbook needs an owner, a review cadence, and one place everyone can reach it. An unmaintained playbook is one of the most common failures.

Step 1: Frame the five P's

Structure the playbook in this order: People, Prospect, Problem, Process, Product. Draft the skeleton first, so each section has a place before anything is written.

• People: who does the job, what they must do, how they are measured, how they grow, and how they are held to standards.
• Prospect: who the team sells to, the ICP, and where prospects come from. Link to the icp-builder output.
• Problem: the pains prospects have, in their words, and the cost of leaving them unsolved.
• Process: the steps of a deal, the methodology, and the qualification gates. Link to the methodology and qualification skills.
• Product: what is sold, the value it creates, its proof, and the pricing and objections the team handles.

Step 2: Draft the People section with the leader

Work through four blocks.

Expectations. Set the daily, weekly, and monthly rhythm: activity, call reviews, trainings, team meetings, and key targets. Break every target into its math. Example: a $100K quarterly target at an average deal size of $10K needs 10 deals. At a 25 percent close rate, that is 40 qualified opportunities. If inbound and SDR support cover 35, the rep must self-source 5. A rep should be able to re-derive their number from these inputs. Then set the promotion and termination criteria, both known from day one.

Standards of excellence. Define the behaviors the team holds itself to. These are separate from the company values on the wall. Values are what you believe. Standards are how you behave. For each standard, define it, give a real example from the team, and end with a signature page where each person commits to uphold it. The signature is what a hard conversation later refers back to.

Goals. New hires set personal goals with their manager, so the manager can align what the person is trying to achieve with the support the company gives.

Stories and records. Collect them from the team: the people who set the standard, the comeback stories, the last-minute deals, the honest failures, one tip from every rep, and the records (fastest ramp, largest deal, most meetings in a week). New people need to see people like them succeeding.

Step 3: Build the ramp into the People section

Ramp is the most expensive unmanaged period in the sales budget. Treat it as a system.

Ramp math first. Ramp cost per hire is months to full productivity multiplied by loaded cost plus the quota coverage gap. Calculate it for the last four hires. Capacity plans should count ramped-equivalent reps, not heads. A rep in the second month of a five-month ramp counts as a fraction of a rep. Plans that count heads produce a pipeline gap that is blamed on the market.

Milestone-gated 30-60-90. The default arc for a mid-market AE. Compress or stretch it by motion, but keep the gate logic:

• By day 30: certified on the story. Can run the first-call pitch and discovery to standard, scored against a call-scoring rubric on real or roleplay calls. Self-assessment does not count.
• By day 60: certified on the motion. Running discovery on live calls with a manager or peer listening. Qualified opportunities created that pass the gates in Step 4.
• By day 90: producing with a fading scaffold. Owns deals through mid-funnel, with a first outcome appropriate to the cycle length.

Each gate has three outcomes: pass, remediation with a named gap and a re-test date, or an early honest verdict. The purpose of gates is to surface a poor fit by month two, not month nine.

Ramp-adjusted targets. Stepped quota over the ramp period, with any draw or guarantee matched to those steps. A full quota on day one teaches new reps to chase bad deals.

Leading indicators from week one. Track time to first meeting, time to first qualified opportunity, and activity quality, by cohort. These are the early warning. Waiting for month-five revenue is too late.

Manager cadence. Weekly 1:1 against the milestone plan, reviewing evidence rather than feelings. Two call reviews per week at least, through day 60. A written monthly verdict (on track, remediation, or concern) that someone above the manager reads.

Step 4: Build the Process section around the methodology and gates

Choose the methodology. Pick one default and name it in the playbook. Selection depends on the sale:

These ranges are guidance, not benchmarks. Check them against the client's own deal data.

Common pairings: SPICED with Challenger for mid-market SaaS that must qualify rigorously and teach something new; MEDDIC with SPIN for multi-meeting enterprise discovery; Gap Selling with SPICED where the buyer must feel the cost of inaction; BANT as a five-minute screen before a full discovery for high-volume inbound.

Write the evidence gates. Score each qualification dimension from 1 to 5 on the strength of evidence, not on rep confidence:

1. Unknown: never asked.
2. Weak: surface mention, uncorroborated.
3. Confirmed: the buyer said it, and it is logged with a quote, transcript, or email.
4. Quantified: numbers behind it.
5. Validated: corroborated by a third party or by system data.

The jump from 2 to 3 matters most. Set minimum totals per stage, and a floor on every dimension. A deal does not advance if any dimension sits below its floor. Commit-stage deals must have a written answer to: "What breaks for this customer if they do nothing until next quarter?"

Verdicts on a date for every below-gate deal: re-qualify (named person, named day), downgrade, or kill with the loss pattern recorded. "Leave it and hope" is not a verdict. Expect to remove a meaningful share of active pipeline in the first month. The forecast gets smaller and more accurate.

Link the full gate design to the deal-qualification-gates skill when it is added to the library.

Coach with the methodology. The weekly deal review uses three to five deals per rep, prioritizing stuck deals, near-term closes, and large deals. Ask methodology questions, not status questions. Score each deal with the rep present. Agree one next action per deal, not three.

Keep the fields few. Start with five to seven critical fields in the CRM. Add more only after the first set is habit. Twenty fields per deal will end adoption.

Onboard in four weeks. Week one: framework and language, scoring historical deals. Week two: guided practice with roleplays and recorded-call analysis. Week three: shadowing live calls. Week four: live calls with coaching. Then weekly reviews, monthly calibration, and a quarterly refresh.

Step 5: Draft the Prospect, Problem, and Product sections from reality

For each section, interview reps and managers, and take the language they use. Pull real examples from calls and deals. Their input is what makes a playbook adopted rather than shelved.

• Prospect: the ICP as scored in won deals, the sources that produced them, and the disqualifiers the team has learned.
• Problem: the pains in the buyer's own words, the business cost of each, and the triggers that make buyers act.
• Product: what is sold, the proof and references, the objections the team hears and the answers that have worked, and the discount rules, if they exist.

If the team has no real examples for a section, mark it as a gap with an owner and a date. Do not fill it with generic copy.

Step 6: Set the operating rhythm

Assign:

• an owner who is accountable for accuracy
• an update cadence (quarterly is a reasonable default, plus after any material change in the market or the product)
• one shared home that everyone can reach
• a version number and a change log

Name the review trigger: what would force an update before the next scheduled review, such as a lost deal pattern, a new competitor, or a change in pricing.

Step 7: Test the playbook

The test: could a rep who joins after the leader has left succeed from this document alone? Check by walking a new hire through the document and noting every point where they would have to ask someone. Each question is a gap to close.

Output

1. Skeleton: the five sections in order, with the status of each (drafted, partial, or gap).
2. People section, drafted: expectations with the target math, promotion and termination criteria, standards with the signature page template, goals template, stories and records collected, the ramp plan with its gates and manager cadence, and the ramp math for the last four hires (or a note that it is unavailable).
3. Process section: the chosen methodology with its reasoning, the evidence gates, the qualify-or-kill rule, the coaching structure, and the onboarding arc.
4. Prospect, Problem, Product sections: drafted from interview input, with any gaps named and owned.
5. Operating rhythm: owner, cadence, home, version, and review triggers.
6. Open questions: each gap, who should answer it, and by when.

Quality bar

• Every target shows its math.
• Every ramp gate names its evidence, and its remediation path.
• Every methodology choice is justified against the sale, not chosen by default.
• Every section draws on real calls, deals, or rep language, or the gap is named.
• Figures from vendor or survey sources are labeled as such, with the year.
• No invented numbers. Missing data is a blank with an owner.
• The operating rhythm names an owner, a cadence, and a home.
• The new-hire test has been run, and each gap it found is logged.

Rules

• MUST be written down, and agreed with the sales leader and at least some reps.
• MUST build each section from real calls, deals, and rep language. NEVER fabricate a process the team does not run.
• MUST draft the People section first, and show the math behind every target.
• MUST gate ramp and qualification on evidence, not elapsed time.
• MUST name the methodology and the minimum evidence per stage in the Process section.
• MUST NOT present survey or vendor figures as industry standards. Label the source and its year.
• MUST NOT invent targets, close rates, or ramp data. Leave a blank with an owner.
• MUST assign an owner and an update cadence before the playbook ships.
• NEVER let the playbook be fully outsourced. The leader stays heavily involved.