← All solutionsSolution · AI cost control

Make the AI bill grow slower than revenue

Know what every feature, user and plan costs you, then bring it down without making answers worse: smaller models where they are good enough, prompts laid out for caching, free-user spend capped before the request, and a ledger finance can read.

Who it is for

AI features users love and finance does not, and new products that need a cost per user before launch.

What we can build for you

Six things we can put in your product, each backed by work we have already shipped.

01
Metering per call
Tokens and cost logged per user, feature and plan, priced from a table you can edit.
02
Model tiering by task
The smallest model that does each job well, the largest only where it earns its place.
03
Prompt-cache layout
The static part of the prompt first and byte-identical, so most input tokens come from cache.
04
Free-tier caps
Free-user spend limited before the request, not discovered on the invoice.
05
Token wallets and plans
Allowances, prepaid packs, and alerts at 80, 90 and 100%.
06
Cost per user, projected
For a new feature, the cost at launch worked out from your real data before you build it.

The four tests, for this

Where this kind of feature usually breaks, and what passing each test looks like.

01 · Design
Does it feel right?

Users never notice the cheaper model, because it only runs where the quality holds.

02 · Mobile and backend
Does it hold up?

Caps and budgets enforced in code, and nothing breaks when a limit is hit.

03 · AI, retrieval and evals
Is it right?

Every cut measured against an eval set, so savings never come from worse answers.

04 · Metering and pricing
Most at risk
Does it pay?

A cost per user you can read every month, next to what that user earns you.

Closest track: Fix the margin

How the two weeks go

€6,000, fixed. Written findings on day five; stop there and pay half. You keep everything either way.

  1. Days 1 to 4Meter it: tokens and cost per operation, per user and per plan. Find where free spend happens.
  2. Day 5Findings: what a free user costs today, and the three cheapest cuts, with their risk.
  3. Days 6 to 9Tier the models by task, fix the prompt-cache layout, and cap free spend before the request.
  4. Day 10Handover with a usage ledger and the new cost per user, measured.

Where we have done it

Previous work · 2025 to now
Multi-agent AI platform
77.5% of input tokens served from cache, six models tiered by task, and a token wallet.
Built by our team · 2025 to now
Voice AI writing app
A free tier that makes no model calls at all.
Built by our team · 2026, early access
AI product analytics platform
A cache key chosen so the hourly sync can never trigger a model call.

Tell us what you are building.

Thirty minutes, no deck. You get a straight answer about whether we are the right people, and we say no when we are not.