# Playbooks

> Situation-anchored outreach recipes — each page maps one specific sales situation to targeting, sequence structure, message templates, expected results, and the steps that build it in Reply.

**Each playbook page anchors to a specific sales situation — reviving closed-lost deals, founder-led outbound, a cold database, a lean team adopting an AI SDR, or inbound signals going cold — and walks from targeting through sequence structure, templates, and expected results to the exact steps that build it in Reply.**

_Status: Reviewed — written against Reply's product documentation on 2026-08-03, not yet confirmed against the running product._

A playbook is anchored to a specific situation, never a keyword. Each page starts from a
moment teams actually recognize — "our closed-lost pipeline is sitting untouched", "trial
signups keep going cold" — and works forward: who the play fits, how to target, the
sequence structure step by step, illustrative message templates, the results to expect,
and the numbered steps that build the whole thing in Reply.

> **Playbooks (this section) vs Playbook (Jason AI object).** These pages are human-readable
> outreach recipes. The [Playbook object](/specifications/playbooks) is Jason AI
> configuration — the machine version of a strategy. A page here may tell you which Playbook
> object to create.

## The plays

- [Reactivate closed-lost pipeline](/playbooks/reactivate-closed-lost-pipeline) — deals lost to timing, budget, or a competitor, reopened with what-changed messaging
- [Outbound for seed-stage founders](/playbooks/outbound-for-seed-stage-founders) — founder-led meetings from a small account list without burning the main domain
- [Re-engage a cold contact database](/playbooks/re-engage-cold-database) — hygiene first, a permission-style reopener, prune whatever stays silent
- [AI SDR for lean teams](/playbooks/ai-sdr-for-lean-teams) — Jason AI with approval gates for a one-to-three person GTM team
- [Book meetings from inbound signals](/playbooks/book-meetings-from-inbound-signals) — fast follow-up on visitors, downloads, and trials before intent decays

## Related

- [Workflows](/workflows) — complete outcomes with every product rule on the path
- [Learn](/learn) — the mechanisms these plays depend on, from deliverability to reply classification
- [Capabilities](/capabilities) — what Reply can and cannot do at the task level