Campaigns as experiments

Outbound playbooks

A playbook is not a script to repeat. It is the current best experiment, with its readings attached.

Most playbooks are templates. Ours are segments. Each segment of the base gets its own sequence, written for the thing that makes that segment a fit, and measured on its own so a change can be made where it is not working rather than everywhere.

Every sequence follows the same rules. A plain-text first message with no links. A nudge on day 3 and day 8 for the never-opened. A shorter message for the opened. An immediate stop on any reply. A cap on volume that comes from the reading, never from the playbook.

What makes it a playbook rather than a guess is the log. Each sequence carries its readings per message: deliveries, opens with and without known proxies, replies and their classification. A sequence that beats the one before it becomes the playbook. One that does not is rolled back.

Every number in it carries a status, target or measured, and a target is never shown as a result. That rule is what lets the playbook be trusted by the sales team that has to act on it.

Questions

Do you share the playbooks?

With the client, in full, on the board. Publicly, as research posts once the readings behind them are published with a dataset, a window and a read date.

Terms and pages this builds on

Behavioral follow-up Target versus measured Plain-text first message Cold email automation How the seven stages run What outbound engineering is

This page is part of outbound engineering, the practice of running B2B outbound as a measured system.

Bring your ideal customer profile. Leave with a plan for the first eight weeks.

Three screens, then thirty minutes with the person who builds the system. If outbound is not worth running for you, you hear that too.

Get your plan

Already running outbound? Say so and we start from your deliverability numbers.