Loading Actuals…
Actuals — start your subscription
actuals Start your subscription
Founding subscriber · support

Find out what your AI vendor actually delivered.

A subscription to the meter, not a one-off invoice. It opens with an audit of your last twelve months of support work, measured against your own people on the same queues, and then keeps measuring while the vendor keeps billing. You get a number you can put in front of your vendor, and the evidence underneath it. Support is the first instance of the meter; the intake is the same for any system that records claimed work and what happened next.

What you get
01
Audit report
Claimed rate against durable rate, per queue, with your human baseline beside it. Every headline number anchored to the matched pairs that produced it, and five named limitations stated plainly.
02
Routing recommendation
Queue by queue: keep on AI, first-pass only, or pull back to human. Delivered as a printable pull-back plan your support lead can work through with the vendor's console open.
03
Working session
Ninety minutes with your CX and procurement leads. We walk the evidence, you challenge the matches, and we leave you with the rebuttal packet in the shape you need for the renewal conversation.
What we need from you
  • Read-only access to whatever holds the work — a Zendesk light agent with an API token, or a CSV/JSON export. Ten minutes of an admin's time either way.
  • Your cost per contact, or a range you are comfortable with. We will not guess it for you.
  • Your vendor contract terms, if you want the renewal maths in the report.
What we never do
  • No write actions. We never post, close, tag, or touch a ticket.
  • No training on your data. Your tickets are never used to improve a model, ours or anyone's.
  • No vendor cooperation. We do not contact your vendor, and we take no money from any vendor we measure.
  • No fee that depends on the finding. We charge the same whether the number is good or bad. That is the point.
Founding subscriber {{ slotsLeft }} of {{ slotsTotal }} left
{{ foundingPrice }} {{ standardPrice }}
{{ priceNote }}
{{ priceFinePrint }}
First report10 business days
Ticket volumeup to 500k / 12 mo
SourcesZendesk API · CSV/JSON
Working session90 min, included
{{ taken }} taken. We onboard four subscribers at a time so the working sessions stay real.
{{ offerFootnote }}
Code pilot · waitlist Not yet measuring
The same meter for coding agents: merged PRs against reverts, linked bugs, and reopened issues. Eight repositories in the first cohort, no fee while it is a pilot.
{{ email }} is on the list. We will write once, when the pilot opens.
Not recorded
{{ joinErrorText }}
Send it to us by email →
{{ checkoutKicker }}

{{ checkoutTitle }}

{{ checkoutBlurb }}

{{ lineItemLabel }}{{ lineItemPrice }}
Opening audit, 12 monthsincluded
Working session, 90 minutesincluded
{{ dueLabel }}{{ dueValue }}
{{ dueNote }}
Not recorded
{{ slotErrorText }}
Send it to us by email →
{{ slotsLeft }} of {{ slotsTotal }} founding slots remain {{ prototypeMarkText }}
Slot held · founding subscriber {{ partnerNumber }}

Your founding slot is held.

{{ confirmedBlurb }}

What happens next
TODAY
Connect your data
A read-only Zendesk light agent and an API token, or an export from your own system. Your admin can do either while you watch.
DAYS 1–3
We read
Twelve months of work read through. You will see honest progress, not a spinner that lies.
BUSINESS DAY 10
First report and session
The report lands in your account first. We walk it together the same week.
Book the working session
Ninety minutes, after the report lands. Tell us when suits you and we will come back with a time.
{{ tzNote }}
Session requested
{{ bookSentText }}
Not recorded
{{ bookErrorText }}
Send it to us by email →
Data processing
You accept our DPA in-product before any data moves — versioned, recorded with a timestamp, and enforced: uploads and engine runs stay blocked until it is accepted. It names the sub-processors, fixes retention at 90 days past report delivery, and deletion is a working control in your Settings. Your tickets are never used to train a model.
The DPA is accepted in-product and recorded before any data moves.
{{ onboardLead }}
{{ onboardCta }}