Playbooks

A Playbook is the named bundle that describes a campaign: an audience, the knowledge assets pinned to it (ICP, persona, offer, message) and the process configuration (sequence, channels, sending account). A playbook owns no data itself — it references it.

What a playbook bundles

• Audience — captured as a Table: the rows are the companies and contacts this playbook addresses.
• Pinned assets — which version of ICP, persona and offer this playbook currently uses; see Knowledge for assets and revisions.
• Process configuration — which Columns the table works through (research → scoring → enrichment → copy → enroll), which Sequence the enrolled leads experience, which Integration sends, and which event-driven Workflows hang off it.

Playbooks are shared, companies are not

Several playbooks in one workspace may reach the same company — companies are unique per workspace, not duplicated per playbook. Playbooks differ in audience, approach and channel, not in owning their own copy of the data.

Changing a playbook

Changing a playbook means pinning a new asset version, adjusting the process configuration or widening the audience — never retroactively altering an existing run. Running Runs stay anchored to the configuration they started with.

You create a playbook through Command (“set me up a playbook for X”) or from a template — see Columns for the template building blocks a playbook draws its process configuration from.