The Scale Playbook

Scaling: Teams, Founders & the Road to $100M — the AI-Native Execution Playbook · Companion to Sales Booklet Chapters 23–26

How to Use This Book

The Booklet's scaling arc makes one demand: stop being the machine and start building it. Chapter 23: sales scaling is about systems, not stars — hiring order matters, incentives shape culture, and calm revenue is the sign of success. Chapter 24: founder-led sales is powerful but temporary; the transition is from doing sales to owning the system; founders become sales architects. Chapter 25: repeatability is the true growth constraint. Chapter 26: at the top, compounding beats effort, trust becomes infrastructure, and architecture replaces optimization. Playbook D supplies the arithmetic ("selling is a craft, but scaling is arithmetic"); Playbook E supplies the hiring scorecard.

This volume assumes Volumes 1–7 run as your systems. Its job is to make them run without you. Prompts P64–P71.

Chapter 1 — The Repeatability Audit: Are You Ready to Scale?

The Principle

Chapter 25: repeatability is the true growth constraint — $10M is a success milestone and a hidden risk when it was built on heroics. Chapter 24: predictability signals readiness to step back; micromanagement signals missing systems. Scaling an unrepeatable motion just manufactures expensive chaos.

Step-by-Step Execution

P64 — Scale-Readiness Audit

Specification

ROLE: You are a scaling diagnostician. You distinguish repeatable systems
from founder heroics, and you say plainly when a company should NOT hire
salespeople yet.

CONTEXT:
- Last 4 quarters: deals won, by segment, with who sold them and how
  much founder magic each needed (honest notes): [paste]
- The system inventory: which of my series artifacts exist and are
  actually used [ICP tiers, one-page strategy, funnel map, sequences,
  discovery arc, demo scripts, proposal system, CRM hygiene %,
  dashboard]: [status per item]
- Win rate, cycle, deal size, and their variance: [from Vol 6 dashboard]

TASK:
1. The repeatability scorecard: for each stage of my funnel — is the
   playbook DOCUMENTED, is it FOLLOWED, and would it survive a
   competent stranger running it? (three checks per stage)


2. Founder-dependency map: which deal moments currently require me
   specifically, and which of those are system gaps vs genuine
   founder-value (Ch 24: strategic involvement remains essential —
   separate the two)


3. Variance analysis: is win rate/cycle stable enough to forecast a
   hire's ramp against? (high variance = process not ready)


4. Verdict: SCALE NOW / DOCUMENT FIRST (with the 5 artifacts to finish)
   / FIX THE MOTION FIRST (with the broken stage)


5. If DOCUMENT FIRST: the founder playbook outline — what a new hire
   would need to sell deal #1 without me in the room

VERIFY: Grade honestly. Hiring into an undocumented motion buys you a
salary and keeps you the bottleneck.

Checklist & Metrics

Audit run; verdict accepted; playbook gaps scheduled if any.
Metric: % of last-quarter revenue that required zero founder heroics — the readiness number.

Chapter 2 — Sales Math: Capacity, Coverage & Velocity (Playbook D)

The Principle

Playbook D: scaling is arithmetic. Coverage = open pipeline ÷ quota (many B2B teams aim 3–4×; your history beats any rule of thumb). Velocity = (qualified opps × win rate × avg deal size) ÷ cycle days — four levers: volume, win rate, deal size, cycle time, with cycle time the most overlooked. Forecast categories (Commit 90%+, Best Case 50–70%, Pipeline 20–40%) keep numbers meaning the same thing to everyone.

Step-by-Step Execution

P65 — Capacity & Growth Model Builder

Specification

ROLE: You are a sales-math modeler. You build models a founder can hold
in their head, with every assumption visible and changeable. Historical
data beats benchmarks; where I have data, use mine.

CONTEXT:
- My actuals: win rate, avg deal size, cycle days, opps created/month,
  current pipeline by forecast category: [from Vol 6]
- Revenue target next 12 months: [number]
- Current selling capacity: [founder hours + anyone else]

TASK:
1. Velocity today: the formula with my numbers, revenue per day, and
   which of the four levers is mathematically cheapest to pull first
   (show the sensitivity: +10% on each lever = what?)


2. Coverage requirement: pipeline needed per quarter for the target at
   MY win rate (not folklore's), and what that demands upstream in
   Vol 1–2 output (conversations/month, sequences running)


3. The capacity wall: at what revenue level does founder-only capacity
   break, given hours per deal — the math behind the hiring trigger


4. The hire model: quota for hire #1 (typically 3–5× their cost at
   maturity), ramp assumptions by month, pipeline they'll need fed vs
   self-generated, and the cash-flow dip before contribution


5. The model as a table I can rebuild in a sheet, assumptions listed

VERIFY: Stress-test with win rate at 0.8× and cycle at 1.2× — if the
plan only works at best case, it isn't a plan.

Checklist & Metrics

Model built in a sheet from P65; hiring trigger defined by math, not mood; forecast categories adopted in the CRM.
Metrics: velocity (tracked monthly); coverage vs required; forecast-category accuracy (Commit should land 90%+ — if not, definitions are decorative).

Chapter 3 — Hiring: Scorecard, Interviews & Ramp (Playbook E)

The Principle

Chapter 23: hiring order matters, sales maturity beats raw energy, and incentives shape behavior and culture. Playbook E's scorecard makes hiring an evidence exercise. Chapter 24: guardrails enable safe autonomy.

Step-by-Step Execution

P66 — Hiring Scorecard & Interview Kit

Specification

ROLE: You are a sales hiring specialist for founder-led companies making
their first sales hires. You screen for maturity, coachability, and
system-following — not charisma. You know a bad first hire costs a year.

CONTEXT:
- The role: [first AE / SDR to feed founder / full-cycle?] per the P65
  capacity math and Ch 23's hiring-order logic
- Our motion + playbook state: [from P64]
- Our deal profile: [size, cycle, buyer type, cross-border demands]
- Playbook E scorecard themes: [paste from the Booklet]
- Comp philosophy notes: [base/variable appetite]

TASK:
1. The scorecard: 6–8 competencies weighted for MY motion (e.g.,
   discovery diagnosis, written communication for cross-border, process
   discipline, resilience), each with 1–5 behavioral anchors


2. Interview plan: 3 rounds with per-round scorecard mapping — including
   a work sample (run a mock discovery on OUR buyer using OUR Playbook A
   arc; a role-played objection round from Vol 5's P53 bank) — plus the
   questions per competency and the follow-up probes


3. Reference-check script: 5 questions that surface how they actually
   sold, not how they interview


4. Red flags list specific to my context (lone-wolf signals, discount
   reflexes, process allergy)


5. Comp structure options (per Ch 23: incentives shape culture): base/
   variable split for the role, what behavior each option rewards and
   what it risks

VERIFY: The work sample is graded on OUR playbook adherence — we're
hiring someone to run a system, and the interview should test exactly
that.

P67 — 30-60-90 Ramp Plan Generator

Specification

ROLE: You design ramp plans that produce a self-sufficient seller in 90
days, with guardrails that make autonomy safe (per my source book) and
checkpoints that catch drift early.

CONTEXT: The hire + role: [from P66]. Our system inventory: [Vols 1–7
artifacts]. Quota + ramp assumptions: [from P65].

TASK: The 30-60-90: DAYS 1–30 — absorb (foundation docs, call
recordings library, shadow every room, pass a playbook quiz; deliver:
mock discovery graded on the arc). DAYS 31–60 — assist (run discovery
with founder observing, own P47 analyses, first supervised demos;
deliver: X real calls at three-outcomes standard). DAYS 61–90 — own
(full-cycle on Tier B, founder joins only at proposal; deliver: first
closed-won or a pipeline at coverage standard). Per phase: guardrails
(discount authority, Negative-ICP enforcement, what needs approval),
the weekly coaching ritual (film review of one real call against the
playbook), and the abort criteria — the honest signals by day 60 that
this hire is not working, and the professional exit path.

Checklist & Metrics

Scorecard + kit built before sourcing; work sample mandatory; ramp plan signed with the hire on day 1; weekly film-review ritual booked.
Metrics: ramp vs plan checkpoints; scorecard-prediction accuracy (revisit scores at day 90 — calibrate the instrument); guardrail violations (early culture data).

Chapter 4 — The Founder's Evolution: From Closer to Architect

The Principle

Chapter 24: the transition is from doing sales to owning the system. Founders become sales architects, not closers. Strategic involvement remains essential; founder visibility sustains trust (your Vol 1 authority engine does not retire); letting go requires identity evolution; emotional decision-making damages scale; founders influence revenue most through standards and vision. Chapter 23: leadership behavior defines culture, and burnout signals system failure.

Step-by-Step Execution

P68 — Founder Role Redesign

Specification

ROLE: You are an executive coach for founders exiting day-to-day sales.
You are direct about identity, honest about what only the founder can
do, and allergic to fake delegation (handing off the task, keeping the
decision).

CONTEXT:
- My current week in sales (hours by activity): [honest log]
- The team now: [who does what]
- What I secretly don't want to give up, and why: [honest note]
- Repeatability audit verdict: [P64]

TASK:
1. The keep/architect/delegate split of my current activities:
   KEEP (founder-only: key-account moments, vision, standards, the
   Vol 1 authority engine — visibility sustains trust), ARCHITECT
   (design + inspect the system: strategy page, dashboard reviews,
   playbook evolution, coaching), DELEGATE (with the guardrail per item)


2. My new operating rhythm: the weekly architect calendar (pipeline
   review as inspector not driver, one film-review coaching session,
   one system-improvement block) — hours, not intentions


3. The interference audit: my 3 most likely micromanagement patterns
   (from my honest note) and the replacement behavior per pattern —
   micromanagement signals a missing system; name the system to build
   instead


4. The standards document seed: the 10 non-negotiables that define how
   we sell (drawn from the one-page strategy + Vol 9's ethics) — the
   founder's real control surface at scale


5. The emotional tripwires: decisions I should never make same-day
   (pricing exceptions under quarter pressure, firing after one bad
   month) and the cooling protocol per

VERIFY: The calendar must show hours REMOVED from deals, not just added
to architecture. Both-jobs founders burn out — and burnout signals
system failure.

Checklist & Metrics

Role redesign done; architect calendar live; standards doc v1 written; interference patterns shared with the team (accountability works better in daylight).
Metrics: founder hours in deals (trending down) vs founder hours in system/coaching (stable); revenue predictability (forecast accuracy is the step-back license — Ch 24); team decisions made without founder escalation.

Chapter 5 — The Road to $100M: Repeatability, Expansion & Moats

The Principle

Chapter 25: standardization enables scale; expansion drives compounding growth; customer success becomes revenue-critical; sales creates moats through trust and integration; category definition improves pricing power; operational discipline protects margins; endurance defines long-term winners. Chapter 26: trust becomes infrastructure; sales evolves into ecosystem design; architecture replaces optimization; AI rewards responsibility and punishes hype; leaders operate at leverage, not urgency.

The System

Three growth engines added to the machine, in order: expansion revenue (existing customers — the cheapest pipeline you own), the reference ecosystem (customers, partners, and reputation selling without you — Ch 26: ecosystems sell without constant effort), and category narrative (the Vol 1 authority engine, matured into defining how buyers think about the problem itself).

P69 — Expansion & Ecosystem Playbook

Specification

ROLE: You are a growth strategist for the post-$1M phase. You believe
the second dollar from a happy customer is worth five first dollars
from a stranger — and that ecosystems compound while campaigns expire.

CONTEXT:
- Customer base: [accounts, what each bought, health/results, expansion
  surface per account]
- Reference assets: [who would advocate, case studies live]
- Partner candidates: [who else serves my ICP without competing]

TASK:
1. The expansion map: per account — the natural next scope (new
   workflow, new team, new geography), the trigger to raise it, the
   internal champion, framed per Vol 7's rule where AI: "same
   governance, new scope"; plus the QBR rhythm that surfaces expansion
   without pressure


2. Customer-success-as-revenue: the 3 health signals to instrument
   (usage/results/sentiment), the intervention play per signal — at
   scale, retention IS sales


3. The reference ecosystem: the advocate cultivation plan (Playbook C's
   referral ask, systematized), the partner motion starter (2–3
   co-marketing or referral structures with the economics), and what
   we give back — ecosystems run on reciprocity


4. Moat inventory: where trust + integration already lock in (data,
   workflow depth, governance track record) and the roadmap choice that
   deepens each


5. The category question: the one idea from my POV (Vol 1, P2) that
   could name the category — and the 12-month authority plan to own it

VERIFY: Expansion asks must trail demonstrated results, never lead
them (Ch 22/26: expansion follows trust, not pressure).

Checklist & Metrics

Expansion map live per account; QBR rhythm running; first partner conversation held; moat roadmap chosen.
Metrics: net revenue retention (the scale metric — >100% means the base grows itself); expansion % of new revenue; referral-sourced pipeline %; margin discipline (Ch 25: operational discipline protects margins as you grow).

Chapter 6 — The 90-Day Plan

Days 1–20: P64 audit; accept the verdict. If DOCUMENT FIRST — the founder playbook becomes the only priority (it usually takes 3–4 weeks of the two weekly sessions). P65 model built; hiring trigger and forecast categories adopted. Days 21–50: If scaling: P66 scorecard + kit; sourcing starts; work samples run. P68 founder redesign; architect calendar live; standards doc v1. Expansion map (P69) drafted; first QBRs booked. Days 51–90: Hire made against the scorecard (or deliberately deferred — the math decides, not the ego); P67 ramp begins with weekly film reviews. First expansion conversations following results. Day 90: review — repeatability score moved? founder deal-hours down? ramp on checkpoint? NRR baseline set? Pick the next constraint from the velocity math.

Protect if behind: the playbook documentation and the weekly coaching film review. Systems and judgment transfer — those two are how.

Appendix — Prompt Index

#	Prompt	Purpose
P64	Scale-Readiness Audit	Repeatability verdict
P65	Capacity & Growth Model	The arithmetic (Playbook D)
P66	Hiring Scorecard & Interview Kit	Evidence-based hiring (Playbook E)
P67	30-60-90 Ramp Plan	Safe autonomy via guardrails
P68	Founder Role Redesign	Closer → architect
P69	Expansion & Ecosystem Playbook	NRR, references, partners, moats

Cadence: quarterly — P64 re-score, model refresh, NRR reading · weekly — coaching film review, architect calendar · per-hire — P66/P67 full cycle.

Closing Note

Chapter 23 gives this volume its finish line in three words: calm revenue — the quarter that closes without heroics, the forecast that lands, the team that sells the way the playbook says because the playbook is genuinely how deals are won. Effort built the first million. Architecture builds the next hundred. The founder's last great sales skill is building the machine that makes their own heroics unnecessary.

— Companion Volume 8 · FISTA Solutions · Sales Booklet 2026