Clarity Conserve measures exactly where your AI spend goes — per stage, per request, per day — and removes the repetition. When we instrumented our own reasoning pipeline, 87% of input tokens turned out to be one reference document, re-sent to every stage.
The problem nobody put in the budget
Headcount you approve. Infrastructure you provision. Tokens just accumulate — one request at a time, invisibly, until the invoice arrives.
And most of it isn't work. It's the same context, shipped again and again inside a single logical task, because that was the simplest way to make the system correct.
The waste isn't in the answers. It's in the setup, repeated.
What we found in our own pipeline
Our document-reasoning pipeline runs eight stages. Before this work, per-stage cost was unmeasurable — every stage reported the whole run's running total. Fixing the meter came first.
One run, one article, eight stages: 246,219 tokens.
Then the surprise. Input barely grew from stage 1 to stage 8 — 1.39×, not 8×. The cost wasn't accumulation. It was a fixed floor: every stage paid ~25,000 tokens for the same reference material before doing any work.
of all input: the same envelope, sent eight times.
everything that genuinely accumulated.
~29,500 tokens in 11 tokens out
The clearest single example: one stage spends ~29,500 input tokens to produce 11 output tokens. Its prompt reads three small sections and never once looks at the largest thing it's being sent.
We went in expecting runaway growth. The data said otherwise, and we corrected our own diagnosis in writing. The fix that follows from the corrected measurement is a different fix — and about six times more valuable — than the one we would have built on the assumption.
Retrieval, not stuffing
When someone attaches a document, the naive approach puts the whole file in the prompt — again on the next message, and the next.
Clarity Conserve doesn't:
So a long attachment contributes a few kilobytes rather than its full length — and the answer can still cite the exact passage it relied on. The same retrieval layer powers Clarity Secure — the provenance that makes an answer enforceable is the provenance that makes it citable here.
The layer that makes an answer citable is the layer that makes it cheap. Same investment, twice the return.
You can check our arithmetic
Clarity Conserve ships the meter alongside the engine:
Every number on this page came out of that instrumentation, on a real run. You can point the same instrumentation at your own workload and reconcile it against your provider's bill.
What this is worth
The only number that matters is the one derived from your volume and your provider's rates. What we will do is instrument your workload and show you the calculation, line by line, from your own telemetry.