Playbooks
Standing rules that stage your own work. When a listing goes live, when a lead arrives, when a deal goes under contract — the checklist files itself on the right days.
A nurture plan sends things to your clients. A playbook stages work for you. That distinction is the whole idea.
What a playbook is
A trigger, then an ordered list of steps.
- The trigger is a thing that happens: a listing created, a listing arriving
from your MLS feed, a lead captured, a deal reaching a particular stage, a
recruit added. Or
manual— you start it yourself. - The steps are tasks, each with a day offset, and optionally a dependency on an earlier step. Some steps can write marketing copy rather than just remind you to.
The starters
Three arrive already set up and active. Look at them before writing your own — they are the shape most people want.
| Starter | Fires when | Does |
|---|---|---|
| Listing launch | A listing is created | Stages photography, copy, the announcement, and the social pieces across the first fortnight |
| New lead follow-through | A lead is captured | First call, a follow-up, a check-in, on a sensible rhythm |
| Under contract | A deal reaches under contract | Asks for the transaction dates first, then anchors every step to them |
Editing one
Tasks → Playbooks, then pick one. You can rename it, change the trigger, and add, remove, or reorder steps. Each step has:
- A title — what the task will say. It can carry the subject’s details:
{{first_name}},{{address}},{{closing}}. - A day offset — how long after the trigger it should appear.
- Depends on — checkboxes over the earlier steps. A step with a dependency waits until those are done.
A playbook that is already running keeps the steps it started with. This is on purpose: shifting the steps under a run in flight would break the dependencies it has already resolved. Your edit takes effect the next time it fires.
Steps anchored to a date
In a deal playbook, a step can be anchored to a transaction milestone rather than to the trigger — two days before inspection, on closing.
Anchored steps wait for the date to exist. That is why the Under contract starter leads with “Set the transaction timeline”: capturing the dates is what launches the rest of the checklist. Tell Elle the dates and the whole thing unrolls.
Steps that write
A generate step in a listing playbook does the drafting rather than reminding you to draft. When it comes due, it writes the piece — an announcement email, a listing narrative — saves it against the listing, and files a short task telling you a draft is ready to review.
If drafting is unavailable for any reason, the step degrades honestly into an ordinary task with a Generate it chip. It never silently skips.
Writing one from scratch
Tasks → Playbooks → New, then either start from a template or choose a blank.
Or describe it to Elle: “Build me a playbook for open house follow-up — thank you note the next day, call after three days, and a check-in a week later.” She writes the whole thing; you review it before it runs.
Watching them run
The Playbooks page shows recent runs. A run knows which step it is on and what it is waiting for. You can stop a run at any point without switching the playbook off for everyone else.
Pausing a playbook freezes all of its runs; reactivating resumes them.