We build it for you, not a toolkit you assemble yourself

An AI agent on your site and your phone line — built for your business, live in days.

Starter is ready in 7 working days. Pro — phone, texts, and an agent that can act rather than only answer — is ready in 14. Underneath both sits the same reliability layer the platform has always run on: every customer reaches only their own data, a person signs off before anything destructive, and every answer is on the record.

A person reviews every build before it goes live. What's included at every tier is below.

Same question · three places Live

Site chat

"Are you open Saturday?"

"Yes — 9 to 5, last booking's at 4."

Phone

"Are you open Saturday?"

"Yes — 9 to 5, last booking's at 4."

Text

"Are you open Saturday?"

"Yes — 9 to 5, last booking's at 4."

One agent the same answer, wherever your customer asks — illustrative, not a screenshot
Scroll

How it works

You describe it. We build it. It goes live.

Every build — Starter or Pro — goes through the same four steps. Nothing is built until you've seen and approved the spec, and nothing is charged until you've seen and approved the agent.

  1. 1 · Describe it

    Tell us what the agent should answer, what it should be able to do, and where your customers should meet it — your site, your phone line, your texts.

  2. 2 · Confirm the spec

    We turn that into a written spec — the exact scope, the integrations, the tier and the price. You read it and approve it before anything is built.

  3. 3 · Watch it build

    We build the agent against the confirmed spec and test it in a sandbox. You can follow along and try it yourself before a single customer does.

  4. 4 · Go live

    It goes live on the day we quoted — 7 working days on Starter, 14 working days on Pro — and the balance is due when it does, not before.

Pricing

Three ways to get an agent built.

Every tier ships with the same reliability layer described below — scoped data, a human sign-off on anything destructive, a tamper-evident record. What changes is where your agent answers and what it's allowed to do.

Self-serve

Starter

An agent on your site that answers questions about your business.

$1,500 build

+ $199/mo once it's live

Live in
7 working days
Where
Your site, as a sidebar
Integrations
Up to 2 of your systems
Can it act
No — reads and answers only
Start with Starter

By appointment

Bespoke

Inside your codebase, your deploy, or data that needs an agreement first.

from $12,000 build

from $999/mo once it's live

Live in
Quoted after a call
Where
Embed, phone line and texts
Integrations
Scoped on the call
Can it act
Yes
Talk to us — no price without a call

Every build splits into two payments: half when you confirm the spec, half when it goes live. Nothing is charged before you've approved what we're building.

What you actually get

The reliability layer is still what it runs on.

This used to be the whole pitch. It still runs underneath every build — it's just not the reason to hire us any more. It's the reason it's safe to.

  • Your customers only ever reach their own data
  • A person signs off before anything destructive
  • A retry never becomes a second charge
  • Every call is on the record — read it, flag it

Every customer only ever reaches their own data.

We bind your agent to whoever's signed in the same way for every customer — the model is never even shown the field that would let it reach someone else's order, account or record. There's nothing for a stray question, or a deliberately odd one, to talk its way into, because the door isn't in the room.

The AXONIC console showing the End users tab for a tool named slop_list_orders. A green panel reads: Scoped. An end user can only ever reach their own data. Below it, a Bound parameters row maps the parameter customer_id to end_user.external_id, and a list headed What the model is handed shows limit, since and status as supplied by the model while customer_id is struck through and marked removed from the model's schema.
The platform underneath cropped, not retouched

A person signs off before anything that can't be undone.

Anything that changes a record, charges a card or cancels something waits for a human before it happens. What that person is shown is not a summary of what the agent wants to do — it's the actual request, in plain terms. It only goes ahead once someone says yes.

Every call is on the record, and you can flag the ones that go wrong.

Every conversation your agent has — what it was asked, what it answered, what it tried to do — is logged with its outcome. When an answer looks wrong, you flag it from the same view, not a support ticket that goes nowhere.

The AXONIC call log. Filter chips across the top read Success, Retried success, Validation error, Silent failure, API error and Guardrail block. A volume panel reports 856 calls and a latency panel breaks p95 down by band, with failure counts beside each band.
AXONIC console Activity → Call log every call, with its outcome

A retry never becomes a second charge.

If we're not sure whether something already went through, we check before trying again — read the record back, never guess. What's below is a real one: five writes our side thought had landed once, that the provider's own records disagreed with.

The AXONIC reconciliation view, subtitled: writes AXONIC recorded that the provider does not agree with. A panel headed What the provider disputed shows five findings, all critical, all of kind duplicate at provider. Stat tiles below read Disagreements found 5, Critical 5, Open right now 5, Closed in window 0.
Govern → Reconciliation each one is a 200 OK that did not mean what it said

The record can prove nobody's quietly edited it.

Every privileged action your agent takes is written down in order and chained together, so the log can catch its own tampering. That's what "you get the transcripts" actually means here — not a promise, a receipt.

The AXONIC audit log. A green banner reads CHAIN INTACT above a row of interlocking chain links, with readings beside it: rows checked 348, first break none, checked just now, and a Verify again button.
AXONIC console Govern → Audit log export as CSV or JSONL

See one

Ask us anything, right here.

This is AXONIC's own assistant, and it will answer questions about what we build, what it costs and how long it takes. Be clear about what it is: a taster. It holds no tools and can't do anything on anyone's behalf.

Your agent is the opposite. It reaches your real systems, under the rules you set, and you test it yourself in a sandbox — with its tools live and every guard armed — before you pay the second half of anything.

This bit needs JavaScript to answer. If you would rather just get on with it, start a build — you will be talking to your own agent in a sandbox before you pay anything beyond the deposit.

Start building

Before you start

What people actually ask.

What happens if it gives a wrong answer?

Every build ships with the guardrails on this page: it only ever sees your own data, and anything that changes something waits for a person. When it doesn't know something, it says so and hands off instead of guessing. You get the transcript for every conversation, so you can see exactly what happened and flag it.

Who owns it?

It's built for your business specifically — not a shared template — and it runs under your account from the day it goes live. The exact legal terms of that are in our terms of service .

Can I change it after it's built?

Small changes — a new answer, an updated hour, a different tone — are covered by the monthly fee. Anything bigger, like a new integration or a new surface, goes through the same spec-and-confirm step as the original build.

What if it doesn't work out?

You only pay the balance once you've tested the agent in a sandbox and approved it going live, so you're never on the hook for a build you haven't seen work. Once it's live, the monthly fee runs like any other subscription — cancel it and it stops.

What if it makes a mistake that costs us something?

The guardrails on this page — scoped data, a human sign-off on anything destructive — exist for exactly that reason. Beyond them, our terms of service set out what we're each responsible for. We'd rather you read that before you start than find out after something goes wrong.