Skip to main content
A Playbook is a reusable sales motion captured as an executable workflow. Define it once — pre-call prep, QBR generation, weekly pipeline review, signal-to-touch — and run it as a one-click action, a schedule, or an automatic response to a signal. Playbooks are how institutional sales knowledge compounds into the agent layer.

How they fit the four pillars

Four ways to create

In New Task, click Prompt to build in the right panel. Describe the goal in one sentence:
Komo wires up the steps, tools, and schedule. You review before saving.

2. Playbook Editor

Notion-like editor where you write the workflow in markdown:
Tools and integrations auto-suggest. Visual preview as you write.

3. Import existing SOPs (Enterprise)

Upload Notion / Confluence / Google Docs / Word files from Settings → Playbooks → Import. Komo extracts the steps and proposes a draft.

4. Record your process

Record your playbook Click Record and walk through the motion on your screen, narrating the why. Komo watches and generates the playbook. Useful for nuanced motions that resist being typed out.

Sales-specific examples

Pre-call brief

Account QBR

Weekly pipeline review

Signal-to-touch

Renewal risk scan

Competitive battlecard refresh

Running a playbook

Four invocation paths:

Writing better playbooks

Be specific about inputs and outputs.
  • ✅ “When email subject contains ‘compliance check’ followed by company name”
  • ❌ “When someone needs a compliance check”
Define clear success criteria.
  • ✅ “Pass if no regulatory violations in 24 months AND financial ratios within ranges”
  • ❌ “Check if account is compliant”
Specify exception handling.
  • ✅ “If renewal date is missing, flag for manual review and notify me”
  • ❌ “Handle missing data appropriately”
Map to specific tools.
  • ✅ “Create a Linear issue, assign to @sales-ops, set priority based on deal size”
  • ❌ “Notify the relevant team”

FAQ

Can playbooks call other playbooks? Enterprise feature — contact sales. What if a step fails? Built-in retry + fallback. Failed runs preserved in History for inspection. Can I version playbooks? Yes. Every save creates a new version; roll back from the menu. How do I update one? Edit in the editor, or describe the change in natural language (“add a step: notify CFO if deal > $50k”). Goes live on next run. Can playbooks read sensitive CRM data? Yes, scoped to your account’s permissions.
Turn your team’s repeated motions into one-click playbooks. Start at the Playbook Editor.