Skip to main content
Admin Guides

Custom Playbook Development

How custom playbooks work — when to commission one, what the process looks like, and how to make sure the methodology actually matches how your team decides.

Last updated May 13, 2026

A playbook is a structured, multi-step workflow Curated runs end-to-end. The shipping playbooks (Site Selection, Market Analysis, Competition Analysis, Expansion Analysis, plus vertical-specific ones for retail, senior living, and weather/emergency) cover most workflows. When your team needs something specific to your business, a custom playbook fills the gap.

Available from

Professional Max — eligibility for custom playbook commissioning (pro-services line item).

Enterprise — custom playbook development is included in the Platform tier; Departmental tier includes scoped allocations.

When to commission a custom playbook

You should consider a custom playbook when:

  • Your decision workflow doesn't match the shipping playbooks — e.g., you do industrial site selection with a specific environmental + permitting overlay that the Site Selection playbook doesn't ship with
  • Your team uses a methodology a generalist agent can't replicate — proprietary scoring weights, internal benchmarks, custom data sources that need to be threaded through the analysis
  • You run the same multi-step analysis frequently enough that codifying it pays back — typically 20+ runs per quarter is the rule of thumb

You probably don't need a custom playbook for one-off analyses; the existing playbooks plus follow-up prompts handle the long tail.

What the process looks like

1. Scoping session (1 hour)

Our team meets with your analysts to understand the workflow:

  • What's the decision the playbook supports?
  • What data sources feed it?
  • What's the methodology — weights, scoring, comparison logic?
  • What's the output — scorecard, narrative, comparison matrix, custom artifact?

We come out of this with a written scope and a delivery estimate.

2. Development (2–4 weeks)

Our team codifies the methodology as a SKILL.md playbook in the Playbook Agent system. This includes:

  • Data source connections (where new partner data is needed, we scope that separately)
  • Methodology logic — the steps the Playbook Agent will run
  • Output template — what the artifact looks like
  • Per-tenant deployment — your custom playbook lives in your tenant only

3. Test with your team

Before going live, we run the playbook against historical examples your team picks. You validate the output matches what your analysts would have produced.

4. Deploy and document

The playbook becomes available in your workspace, callable by name in prompts ("run our portfolio risk playbook on these assets"). Our team writes the help article that goes in your tenant's documentation.

5. Refine over time

Custom playbooks evolve. As your methodology shifts or new data sources become available, the playbook can be updated. Updates are scoped per change.

What custom playbooks are not

  • They're not custom UI — playbooks are agent workflows, not interface changes. UI work is a different engagement.
  • They're not unlimited per-tenant changes — substantial methodology shifts are new engagements, not a single ongoing change-set.
  • They're not training the AI on your data — playbooks define logic, not learned behavior. Your data still doesn't train any model.

Cost and timing

  • Scoping session: included in your Enterprise engagement or quoted as a single line item
  • Development: 2–4 weeks typical; complex playbooks with new data integrations can take 4–8 weeks
  • Deployment + initial training of your team: included
  • Ongoing maintenance: scoped per change request

Talk to your CSM (Enterprise) or sales (Professional Max) to scope.

Related

  • What is a Playbook? (FAQ)
  • Setting Up Your Organization