# Playbooks Why the plugins coach with specific, durable sales-craft instead of generic advice, and how that craft gets sharper from your own wins and losses. **Not a page you fill in.** The playbook brain is memory the plugins carry, not a form you manage. This page explains what it is and how it shapes the coaching you see, so the advice a plugin gives you reads as "here's what worked on deals like this," not "here are five generic tips." ## What the playbook brain is Alongside the go-to-market brain (your company, offer, ICP, voice, funnel), Sales as Code keeps a second, sales-craft brain: a durable record of *how deals actually run*. Objection branches that worked. Plays that moved a stuck deal. Loss postmortems with the prevention rule they wrote. Win patterns worth repeating. Every closer-facing plugin, [GTM Engine](https://salesascode.com/docs/library/plugins/gtm-engine) and [Inbound & Lifecycle](https://salesascode.com/docs/library/plugins/inbound-lifecycle) chiefly, reads from this brain before it drafts. That's the difference between a tool that *runs* your process and one that *coaches* it: the coaching is grounded in specific, dated craft, and it improves every week because each real outcome adds an entry. ## The five loops The playbook brain is organized as five reinforcing loops. You never edit them directly (the plugins write to them as your deals progress) but knowing the shape explains why the coaching lands where it does. Plays Named moves for a situation, "multi-thread proof," "re-engage a dark champion," "trade a discount for a proof point." Surfaced when a deal matches the situation. Objections Objection → branch. The specific rebuttal that landed, and the follow-up that closed the gap, ranked by what actually worked on your deals. Patterns Win patterns worth repeating, the sequence, the proof, the timing that correlated with closed-won. Anti-patterns Moves that looked right and cost you deals. Logged so the next draft steers around them. Errors / losses Loss postmortems, symptom · root cause · the prevention rule. The loop the brain learns most from (see below). ## How the plugins coach with it The craft shows up inside the work, not as a separate report: - **Grounded drafts.** When GTM Engine drafts outreach or a next step, it pulls the play or objection branch that fits this deal's shape, so the draft carries a move that worked, not a template. - **Flags with a fix.** When a deal shows a known risk signal (single-threaded past day 30, a champion gone quiet), the flag comes with the specific play the brain wrote for that situation, not just "at risk." - **Objection help in the moment.** Facing pushback you've seen before, the plugin surfaces the branch that closed it last time and the proof point that backed it. - **Draft-only, always.** The craft informs what's proposed; you decide. Nothing sends on its own. ## Learning from losses The brain learns most from losses. Mark a deal closed-lost and the GTM Engine prompts for a short, structured postmortem (**symptom · root cause · what you'd do differently**) and stores it as a dated entry. The next time an open deal shows the same early signals, that prevention rule fires before the deal slips. A representative entry (anonymized, but exactly the shape that ships): S-001 $87k ACV · lost Symptom Champion went dark for three weeks, she'd quietly taken a new role elsewhere. The rep emailed the listed replacement → silence → closed-lost. Root cause Single-threaded. Champion strength read as "healthy," but with one contact a strong champion is fragile by definition. Prevention rule Champion strength now caps until the account has ≥3 contacts with recent two-way activity; any deal single-threaded past day 30 is flagged regardless of strength; the "multi-thread proof" play surfaces every time the flag fires. ## Why it compounds Generic prompts don't get sharper. A brain that learns from *your* runs does. On day one the playbook brain is close to empty and the coaching is general. By day 30, plays are ranked by what converted for you, loss patterns carry prevention rules, and objection branches reflect what actually landed with your buyers. Because the craft lives in a shared scope, every closer-facing plugin sees it, a lesson one deal taught shows up on the next. ## Your brain, your data The playbook brain is scoped to your account (or your team, on a team plan) and syncs through the same metadata-first contract as everything else: `sync_brain` carries brain state, never raw contact PII by default. You can export your entire brain (playbooks included) as JSON at any time from [Data Export](https://salesascode.com/docs/library/data-export). No lock-in. For the full data contract, see the [privacy policy](https://salesascode.com/privacy). **Next:** see the coaching in context on the [GTM Engine](https://salesascode.com/docs/library/plugins/gtm-engine) page, or read how the brain compounds across every plugin in [Concepts → the brain](https://salesascode.com/docs/concepts#brain). --- More for agents: [llms.txt](https://salesascode.com/llms.txt), [full reference](https://salesascode.com/llms-full.txt), [OpenAPI](https://salesascode.com/openapi.json), [sitemap](https://salesascode.com/sitemap.xml).