Skip to main content
Legacy Playbooks are deprecated. New workspaces and agents should use Motions instead.The legacy Playbook entity has been replaced by a structured hierarchy: Motion → Motion Playbook → Motion ICP. The new model separates the strategy (Motion), the narrative angle (Motion Playbook), and the persona×segment targeting (Motion ICP) into independently editable, learnable units. It is what every agent reads at runtime.

​
What were legacy Playbooks?

A Playbook was a flat object that combined an Offering, Personas, a Segment, Use Cases, References, Proof Points, Competitors, Alternatives, Buying Triggers, and per-persona Value Props into a single executable sales strategy. Agents read from one or more Playbooks at runtime to generate personalized output.

​
Why we replaced them

Legacy Playbooks worked for a single audience but didn’t model the reality that the same offering needs multiple narrative angles (default, thematic, milestone, account-specific, competitive) — and that each angle reaches multiple persona×segment cells, each with its own narrative, learnings, and recommended evidence. Motions make those layers explicit:
Legacy conceptNew equivalent
Playbook (1 flat object)Motion + Motion Playbook(s) + Motion ICP(s)
Per-persona value propsMotion ICP narrative + learnings
Playbook → segment + personasMotion Playbook scope (AUTO or MANUAL)
Playbook → competitors / triggersMotion Playbook narrative type: COMPETITIVE / MILESTONE / ACCOUNT
Playbook collateralMotion Playbook anchor overrides

​
Migration

Existing Playbooks remain accessible via the legacy /api/v2/playbook/* endpoints, but new development should target the Motion APIs. See Motions for the full data model and endpoints.

​
Legacy API (for reference)

  • GET /api/v2/playbook/list
  • GET /api/v2/playbook/get
  • POST /api/v2/playbook/create
  • POST /api/v2/playbook/update
  • DELETE /api/v2/playbook/delete