Introduction
Your stack runs the data. Dispatch runs the work.
Author a workflow once. Dispatch an agent to run it — for yourself, or any of your clients.
What this is.
Dispatch is a system of action. It sits on top of QuickBooks, Salesforce, Drive, Linear, Stripe — the systems that hold your data — and runs the work you'd otherwise do by hand.
You author a Workflow once. You dispatch an Agent to run it for any Client you serve.
The data stays where it lives. Every Run is a permalink, every step is visible, every approval is in your hands.
The vocabulary.
Seven words. That's the whole product.
- Source
- A connected system of record. QuickBooks, Salesforce, Drive.
- Client
- A tenant you serve. Every Run can be scoped to one.
- Workflow
- A recipe an Agent runs. Steps, inputs, outputs.
- Agent
- The collaborator. Runs Workflows. Drafts new ones.
- Conversation
- An ongoing exchange with an Agent. Where most work begins.
- Run
- One execution. Replayable. Auditable. Permalinkable.
- Approval
- A gated decision a human authorizes mid-Run.
An example.
Partnership return · Acme Corp.
▸ dispatch run partnership-return --client acme
┌ Pulled trial balance · QuickBooks
├ 3 accounts with variances over $500
├ approval: write adjustments to QuickBooks approved
├ Wrote 3 journal entries · QuickBooks
├ Generated workpaper from template · Drive
└ Run completed · 4 steps · 4m 12s
Every Run page shows the same thing — the plan, the steps, the inputs, the outputs, the why.
Request access.
Dispatch is in private development. Tell us about the work.