The playbook

How to make pre-sales, migration, activation delivery and go-live growth agentic.

Every agent gets built the same way.

  1. Connect

    One adapter gives agents tools for your metadata, data and sandbox.

  2. Capture

    Your best people’s method becomes skills and runbooks.

  3. Test

    Real customer flows become tests before an agent ships.

  4. Gate

    A person approves anything a customer sees or production receives.

  5. Refresh

    Every release of yours re-runs the tests and shows what broke.

Follow one deal, from first call to expansion.

An illustrative story, not a customer. Under each chapter you’ll see how that part gets built.

  1. Pre-sales

  2. The first call

    After the first call, the prospect shares an export of their current system. A draft fit-gap is ready before the next meeting, and your solutions engineer corrects two lines and sends it.

    Agent
    Fit-gap agent
    Reads
    Exports, docs and call notes
    Person in the loop
    Solutions engineer, before sharing
    Proof it works
    Matches a hand-checked fit-gap
    Ship it as
    MCP tool

  3. The demo

    The prospect expects the usual sample data and sees their own accounts on screen. Your engineer runs the demo from a tested script.

    Agent
    Demo builder
    Reads
    Their sample data and your demo environment
    Person in the loop
    Solutions engineer runs it
    Proof it works
    The script runs start to finish
    Ship it as
    MCP tool

  4. The proof of concept

    The rep moves the deal forward in the CRM, which starts the agent. It builds a sandbox, runs their flows and reports that 14 of 15 pass. Your engineer fixes the last one.

    Agent
    Proof of concept agent
    Reads
    The fit-gap and their configuration
    Person in the loop
    Solutions engineer signs off
    Proof it works
    Their key flows pass
    Ship it as
    Triggered agent
  5. Migration

  6. The migration question

    Their finance lead asks what happens to their data. You show them a trial migration with matching totals, and they approve the mapping.

    Agent
    Migration agent
    Reads
    The old system’s data and configuration
    Person in the loop
    Customer approves mapping and cutover
    Proof it works
    Totals reconcile on repeat runs
    Ship it as
    Triggered agent
  7. Signature
  8. Activation delivery

  9. Delivery picks up the sandbox

    Delivery opens the sandbox the customer approved and skips the discovery questions already answered. The agent builds the rest, and your consultant reviews each change until their flows pass.

    Agent
    Implementation agent
    Reads
    The approved sandbox
    Person in the loop
    Consultant reviews each change
    Proof it works
    Their flows pass end to end
    Ship it as
    MCP tool
  10. Go-live
  11. Go-live growth

  12. The first request

    The customer’s admin asks for a new price list inside your product. They see a preview and approve it. Anything riskier waits in a queue for your team.

    Agent
    Run and admin agent
    Reads
    Requests and current configuration
    Person in the loop
    Admin approves queued changes
    Proof it works
    The regression suite passes

  13. The expansion

    Your account lead asks in Slack who is close to their plan limit. The agent names this customer and drafts a proposal from their usage, and your account lead decides whether to send it.

    Agent
    Upsell agent
    Reads
    Usage and configuration
    Person in the loop
    Account team decides what to send
    Proof it works
    Each claim traces to real usage
    Ship it as
    Chat teammate

Four ways to ship an agent

MCP tool, with skills

Who uses it
Your team and customers, from Claude or Codex
Best for
On-demand work, from quick questions to expert tasks a person steers
You need
An MCP server over the adapter with per-user permissions, plus skills that teach your method
draft_fit_gap(prospect_export)
check_flows(sandbox)
/build-demo prospect-data.csv

Chat teammate

Who uses it
Your team, in Slack or Teams
Best for
Quick questions and actions inside a deal or customer channel
You need
A Slack or Teams app over the adapter, with channel-level permissions
@Sokn who is near their plan limit?
Sokn: 3 accounts. Draft proposals?
@Sokn yes, start with the first

In-product agent

Who uses it
Customers, inside your product
Best for
Guided setup and routine admin at scale
You need
A customer-scoped agent behind your login, with preview before apply
Customer: "Import my price lists"
Agent:    shows a preview of 148 lists
Customer: approves, agent applies

Triggered agent

Who uses it
An event starts it, and your team reviews the result
Best for
Long jobs that finish with something to review
You need
Event hooks from your CRM and releases, plus an approval queue
on deal.stage = "Proof of concept"
  build_sandbox(prospect)
  ask solutions_engineer to approve

Examples are illustrative. Most vendors would mix patterns, and all four sit on the same adapter and tests.

House rules

Want this for your product?

Start with a paid diagnostic: $5–10k, credited against your first build.

Email us about your backlog