Playbooks

Each playbook below is a complete execution guide — not theory. Pick the bottleneck that's costing you the most time or money, follow the steps, and ship the fix this week.

Playbook 1: Sub-5-Minute Lead Response

RevenueAutomation30 min setup

The problem: You get a lead form submission at 2pm. You see it at 6pm. By then they've talked to two competitors. Studies show responding within 5 minutes makes you 21× more likely to qualify the lead.

What you need

A form tool that supports webhooks (Tally, Typeform, Google Forms + Zapier)
An AI agent or automation layer (OpenClaw, n8n, Make, or even a simple Zapier flow)
A message template library (3–5 pre-written responses by lead type)

Step-by-step

1. Map your lead sources. List every place a lead can enter: website form, email, DM, referral intro. Most businesses have 3–5.

2. Create response templates. Write one template per lead type. Include: acknowledgment, one qualifying question, and a clear next step (calendar link or reply prompt). Keep it under 60 words.

3. Wire the trigger. Connect form submission → webhook → AI agent (or automation). The agent reads the submission, selects the right template, personalizes the first line, and sends within 60 seconds.

4. Add the human handoff. Agent sends the reply AND pings you (Slack, SMS, email) with a summary: who they are, what they asked, what was sent. You review and follow up with depth — but the speed win is already locked.

5. Measure and tune. Track: time-to-first-reply, reply rate, and booked-call rate. After 2 weeks, review which templates get replies and cut or rewrite the rest.

Common mistakes

Making the auto-reply too long or too salesy — keep it human and short
No human follow-up after the auto-reply — the agent buys you time, it doesn't close deals
Forgetting to test the flow end-to-end before going live

Playbook 2: AI-Assisted Client Onboarding

OperationsClient Experience2–4 hours setup

The problem: Every new client gets a slightly different onboarding. Things get missed. The client feels uncertain. You waste the first two weeks asking for info you should have collected upfront.

The framework: Collect → Confirm → Kickoff

1. Collect (before kickoff call). Send an intake form within 1 hour of signing. Collect: business context, existing tools/logins, success criteria, communication preferences, key dates/constraints. Use a structured form — not "tell us about yourself."

2. Confirm (automated summary). AI agent reads the intake form and generates a one-page project brief: scope, timeline, success metrics, first milestone, and open questions. Send this to the client for approval before the kickoff.

3. Kickoff (30 min max). Don't re-collect info. Use the brief as the agenda. Cover only: open questions from the brief, communication cadence, and the first deliverable with a due date. End with the client knowing exactly what happens next and when.

Onboarding checklist

☐ Intake form sent within 1 hour of contract
☐ Intake form completed by client
☐ AI-generated project brief sent for approval
☐ Brief approved or revised
☐ Kickoff call scheduled (30 min)
☐ First milestone and due date confirmed
☐ Client added to communication channel
☐ Internal team briefed with same document

Playbook 3: Weekly Ops Review (The 15-Minute Cadence)

OperationsFounder Time15 min/week

The problem: You either skip weekly reviews entirely (things drift) or they turn into 90-minute status meetings (everyone's exhausted). Neither works.

The format

Before the review: AI agent pulls data automatically — tasks completed, tasks overdue, revenue collected, pipeline status, open client issues. This takes 0 minutes of your time.

The 5-5-5 review (15 min total):
• 5 min: What shipped this week? (celebrate wins, note velocity)
• 5 min: What's stuck? (identify the single biggest blocker)
• 5 min: What's the one decision to make right now? (decide, assign, set deadline)

After the review: Agent generates a summary with decisions and action items. Distributes to the team. Next week's review starts from this summary.

Rules that make it work

Never longer than 15 minutes — if it needs more, schedule a separate deep-dive
One decision per review minimum — no "let's think about it"
Skip weeks where nothing is stuck (use the agent summary as a passive check instead)
The founder's job is decisions, not status updates — let the agent handle reporting

Playbook 4: Scope Creep Prevention System

Client OpsRevenue Protection1 hour setup

The problem: Client asks for "one more thing." You say yes because it's small. Repeat 12 times. Now you're 40% over scope, eating margin, and the client still isn't happy because the original deliverables slipped.

The system

1. Define the scope boundary clearly. In your project brief, list what's included AND what's explicitly not included. "Website redesign includes up to 5 pages. Additional pages are $X each." Specificity prevents ambiguity.

2. Create a change request template. Any request outside the original scope gets logged: what's being asked, estimated hours, impact on timeline, cost. This isn't bureaucracy — it's clarity. (Grab the template →)

3. Automate the trigger. When a client message contains scope-expansion signals (new feature requests, timeline changes, "can you also…"), the AI agent flags it and drafts a change request for your review before you respond.

4. Respond with the framework, not emotion. "Happy to do that — here's what it looks like in terms of time and cost." The change request template makes this a 2-minute conversation instead of an awkward negotiation.

Why this protects the relationship

Clients respect boundaries when they're clear upfront
You stop resenting clients for asking (they don't know it's out of scope unless you tell them)
Revenue stays protected without being adversarial

Next step

Pick one playbook, run it for 7 days, and measure what changed.

Open matching Templates →