Pricing
Pricing
One platform fee for the kernel. Agent work priced per run. People are free.
[How does [company] pricing work? One platform fee covers the GTM kernel and unlimited human seats; each agent family is priced per run. A run is one unit of completed work. Committed annual tiers with soft overage. Plans start at $[floor]/yr.]
What do you pay for?
Two components: a platform fee for the infrastructure, and per-run usage for the work the agents perform. AI pricing fails on unit confusion, so here is the unit, exactly.
Platform fee: the base layer
The kernel →The GTM kernel (records, versioning, governance), unlimited human seats, integrations, audit & controls, scaled by kernel scope (segments / business units), not by people.
AI SDR
[page P1]Priced per run.
Content agents
[page P1]Priced per run.
Creative agents
[page P1]Priced per run.
Research agents
[page P1]Priced per run.
| Agent family | One run is… | What it replaces |
|---|---|---|
| AI SDR | one account worked end-to-end through an approved sequence (research → outreach → reply handling → CRM write) | the research-to-CRM work an SDR does per account |
| Content agents | one content asset taken from brief through approval | a writer's brief-to-approved-draft cycle |
| Creative agents | one variant set (one concept × its formats) through approval | a designer's concept-to-variants production |
| Research agents | one intelligence digest or report cycle | an analyst's digest cycle |
- Committed annual run tiers with a stated rollover posture.
- Usage dashboard with alerts at 80% and 100%.
- Soft overage at a published rate, never a service cutoff.
- No surprise bills.
Which tier fits?
Single motion
teams running one motion
Starts at $[floor]/yr
- Kernel scope
- one segment
- Agent families
- one agent family
- Run volume
- [committed run tier]
- Governance
- standard controls + support
Multi-motion
multi-motion GTM teams
Custom
- Kernel scope
- multiple segments
- Agent families
- multiple agent families
- Run volume
- [higher committed tier]
- Governance
- advanced controls + priority support
Enterprise
multi-BU or regulated
Custom
- Kernel scope
- multiple business units
- Agent families
- all agent families
- Run volume
- [negotiated volume]
- Governance
- enterprise governance + SLA
Bring your security questionnaire. AI & data trust →
[Contract shape: annual, onboarding included, no asterisk farms. All tiers route to a demo; no checkout.]
What drives the cost up?
What moves you up
- Agent families activated.
- Committed run volume.
- Kernel scope: segments / business units.
- [Confirm: premium integrations? residency? (§9)]
What never costs more
- Human seats: reviewers, approvers, stakeholders.
- Kernel records and updates.
- Standard integrations.
- Usage dashboards and audit access.
Which shape is roughly you?
Illustrations, not customers: company shapes, not case studies.
[Small team · one motion · one agent family]
Lands in
Single motion
[State N: annual range]
[Scaling GTM · two motions · two agent families]
Lands in
Multi-motion
[State N: annual range]
[Multi-BU · regulated · all families]
Lands in
Enterprise
[State N: annual range]
[P1: an estimator. Inputs are run volumes + families, output is a tier + range band. Estimate ungated; only “send this estimate” gates on email.]
What are we accountable for?
Uptime
[uptime commitment: defined in your order form (§9.6)]
Support response
[response time by tier (§9.6)]
When an agent errs
[remedy shape: credits, not legal text (§9.6)]
Frequently asked questions
What drives the cost up?
How does overage work?
What are the contract length and payment terms?
What does implementation cost and how long does it take?
What happens to our data and kernel if we cancel?
Why is there no per-seat pricing?
How are price changes handled at renewal?
What's not included?
Leave with a real quote for your volume
30 minutes. We size it to your run volume and give you a number.