TRAKEN — traken.ai · reconciled to the cent
01 — the reconciliation

When investors ask about your AI margins, “roughly” isn’t a number.

Every AI cost tool estimates from a price sheet. Provider invoices don’t work that way — cache multipliers, reasoning tokens, mid-month price changes, 30-day restatements. Traken reconciles every request to your provider invoice, to the cent. Then it proves what your AI actually costs, wastes, and earns.

Verified against real provider invoices — where reconciliation succeeds, the residual is $0.00; where it can’t, Traken tells you exactly why instead of hiding it.

Read-only. Token counts and hashes only — never your prompts.

Telemetry Invoice
req_7c19e2af18,204 / 2,411 claude-sonnet-4-6$1,204.18
req_7c19e2b044,806 / 1,022 cache writes 1.25×$866.42
req_7c19e2b19,331 / 3,208 reasoning output$733.90
req_7c19e2b261,240 / 884 batch discount$641.27
req_7c19e2b312,077 / 1,530 claude-haiku-4-5 batch$498.11
restatement · day 30$238.19
req_7c19e2af18,204 / 2,411
claude-sonnet-4-6$1,204.18
req_7c19e2b044,806 / 1,022
cache writes 1.25×$866.42
req_7c19e2b19,331 / 3,208
reasoning output$733.90
req_7c19e2b261,240 / 884
batch discount$641.27
req_7c19e2b312,077 / 1,530
claude-haiku-4-5 batch$498.11
restatement · day 30$238.19
Residual Δ $0.00
reconciled · 2026-07-01 04:12 UTC
02 — proof

Numbers a CFO can take to the board. Because they tie to the invoice.

Traken’s core is deterministic SQL — zero LLM anywhere in the numbers path. Every figure traces to an invoice line or is explicitly labeled MODELED with its named assumption. Never one blended ROI number.

Reconciled, not estimated.

Per-request true cost matched to provider invoices — and every gap explained, never averaged away.

AI and cloud on one reconciliation engine.

Upload your AWS, GCP, or any FOCUS billing export — Traken reconciles it to the closed invoice the same way it reconciles your LLM spend, allocates shared costs with sub-0.1% error, and shows anything unallocated explicitly instead of smearing it. The ~3% silent misallocation that makes finance distrust cost tools is exactly what we refuse to do.

Unit economics per feature, tenant, and customer.

The gross-margin-per-feature answer investors ask for.

P&L bridge — and the return side in the language your board expects.

Invoice → general ledger → margin bridge; measured savings separated from modeled forecasts, exceptions shown, never dropped. NPV, IRR, payback — with optimism explicitly haircut, never baked in.

AI COGS bridge · May → June 2026 MAY COGS $41,882.10 PRICE +$3,214.55 VOLUME +$6,027.42 MIX +$1,499.63 SAVINGS LANDED −$4,412.33 JUNE COGS $48,211.37 axis truncated at $35k
source: repriced line items · rate cards v2026.06.28
AI COGS bridge · May → June 2026 $35k $40k $45k $50k $41,882.10 +$3,214.55 +$6,027.42 +$1,499.63 −$4,412.33 $48,211.37 MAY COGS PRICE VOLUME MIX SAVINGS LANDED JUNE COGS
source: repriced line items · rate cards v2026.06.28 · y-axis truncated at $35k
03 — three answers

One deterministic engine. Three answers.

1 · Where the money goes

Cost attribution and showback per tenant, feature, and customer. Your system of record for AI spend.

Feature Cost Gross margin
rag search$12,406.8861.2%
summarize$8,114.2043.7%
agent runs$6,943.1522.4%
embeddings$1,208.4488.1%
Tag coverage 96.4%
reconciled · 2026-07-01 04:12 UTC
2 · What you’re wasting — and the exact fix

One dollar-ranked list across your AI and cloud bill: model right-sizing, caching, context bloat, retries, batch — alongside unattached volumes, idle gateways, orphaned snapshots, off-hours waste. Anti-double-counted, each shipped as a ready-to-apply config diff plus an eval plan — hand it to your engineer or your coding agent, run the evals, merge. Traken never touches your production path; you approve every change. And after you ship a fix, Traken reprices your actual workload against the next invoice — so every claimed saving is measured, not asserted.

model right-sizing$2,841/mo
caching$1,904/mo
context bloat$1,377/mo
retry storms$912/mo
PLAYBOOK S2 · CONFIG DIFF
- model: claude-opus-4-8
+ model: claude-sonnet-4-6
+ cache_control: ephemeral
- max_context: 200000
+ max_context: 32000
verified against invoice #INV‑2026‑06‑114
the realized change is confirmed by the next reconciliation run — not projected.
Eval plan
1  replay 10,000 sampled requests offline
2  quality evals vs baseline · win rate ≥ 0.98
3  reprice against next invoice — measured, not asserted
3 · Whether it’s worth it

Most AI initiatives can’t demonstrate ROI — not because there is none, but because nobody defined benefits, baselines, and owners before shipping. Traken’s guided interview does exactly that: benefit classes and conversion paths, costs beyond inference, hurdle rates, ramp phasing, a skeptic pass that challenges optimistic assumptions against reference-class priors. Then actuals flow in monthly from reconciled cost, and MEASURED vs MODELED variance is tracked — so six months in, you know whether the case held, not just whether it was pretty.

−12% vs target JAN JUN MEASURED MODELED
source: value_case actuals · reconciled inference cost
04 — the evidence pack

When the term sheet comes — the evidence pack, ready.

Two artifacts, one engine, exportable in a day:

TRAKEN Verified Cost Report
period2026-06 · 24 pp coverage100.0% · tiered stress-replay+25% · cache off · 5–10× shaa3f9c21e · run twice, identical
TRAKEN Value Case
contentsNPV · IRR · payback · 18 pp bias adjustmentexplicit targets vs actualsmonthly savings ledgerreconciled

Verified Cost Report. What you actually spend on AI — every dollar tiered by how it’s verified: reconciled to the invoice, invoice-verified, management-declared, or uncovered. Coverage sums to 100% — we tell you what we couldn’t verify, too. Includes deterministic stress-replay: your real workload repriced under +25% provider prices, caching off, 5–10× load — same SQL, same hash, run twice.

Value Case. What it returns — NPV, IRR, payback with explicit bias adjustment, benefit targets vs measured actuals month by month, and a closed loop on every optimization: each shipped fix counterfactually repriced against the next invoice, so “we saved $X” is a reconciled number, not a slide.

Coverage · sums to 100%
T1 RECONCILED 62% T2 23%
T3 9% UNCOVERED 6%
T1 reconciled 62%T2 invoice-verified 23%T3 management-declared 9%uncovered 6%

A boutique cost review runs €5,000–15,000 and takes 2–4 weeks — opinions in a PDF you can’t re-run. AI-specific or enterprise FinOps work runs well past €30,000, often 4–8 weeks, with the same limitation. Traken’s report is generated from your reconciled data, reproducible bit-for-bit, from €490, in a day.

Boutique consultancy
price€5,000–15,000
duration2–4 weeks
verdictopinions, not re-runnable
AI / enterprise FinOps
pricewell past €30,000
duration4–8 weeks
verdictopinions, not re-runnable
Traken report
pricefrom €490
durationone day
verdictdeterministic, re-runnable
BOUTIQUE CONSULTANCY€5,000–15,0002–4 WEEKSOPINIONS, NOT RE-RUNNABLE
AI / ENTERPRISE FINOPSWELL PAST €30K4–8 WEEKSOPINIONS, NOT RE-RUNNABLE
TRAKEN REPORTFROM €490ONE DAYDETERMINISTIC, RE-RUNNABLE
Get your Verified Report → View a sample report Self-serve, priced by spend band. No calls required.
05 — why estimates break

estimated_cost != invoice_total

Cache writes billed at 1.25×–2×. Reasoning tokens billed as output. Prices changed mid-month. Batch and cache discounts stacking. Usage restated 30 days later. Price-sheet math silently drifts from the bill — and Traken’s effective-dated rate engine catches the drift before you see it on the invoice.

PRICE-SHEET ESTIMATE INVOICE mid-month price change restatement (day 30) caught before the invoice. DAY 1 DAY 30
source: repriced line items · rate cards v2026.06.28
PRICE-SHEET ESTIMATE INVOICE caught before the invoice. cache write 1.25× mid-month price change restatement (day 30) DAY 1 DAY 30
source: repriced line items · rate cards v2026.06.28
06 — how it works

Bring the telemetry you already have — Langfuse, OpenTelemetry GenAI, or our thin SDK wrapper. Traken ingests token counters and metadata (never message content), reconciles against your usage API and invoice, and puts every number behind a SQL query you can inspect. Narrative reports are generated by an EU-resident model by default, with every number cited from SQL and hard-blocked if grounding fails.

telemetry · OTel GenAI
usage APIs
invoices · PDF/CSV
cloud exports · FOCUS/CUR
DETERMINISTIC ENGINE
rate engine
reconciliation
attribution
THREE ANSWERS
EVIDENCE PACK
telemetry · OTel GenAI
usage APIs
invoices · PDF/CSV
cloud exports · FOCUS/CUR
DETERMINISTIC ENGINE
rate engine
reconciliation
attribution
THREE ANSWERS
EVIDENCE PACK
07 — finops as software

FinOps as software, not headcount

The FinOps playbook — attribution, tag coverage, anomaly detection, rate-drift monitoring, savings ledgers, business-case governance — built into the product instead of a hire you can’t make yet. FOCUS-aligned data model, FinOps-standard KPIs, and the discipline enforced by the engine, not by a slide deck.

One engine, one methodology — from your Anthropic invoice to your AWS bill.

The FinOps playbook
attribution
tag coverage
anomaly detection
rate-drift monitoring
savings ledger
business-case governance
08 — faq
Isn’t this just another cost dashboard?+

Dashboards estimate. Traken reconciles. If a number doesn’t tie to an invoice line, it’s labeled modeled — or it doesn’t ship.

We could build this with LiteLLM.+

You’d get estimates. Reconciliation requires an effective-dated rate engine, a residual-allocation waterfall, and restatement handling — and a build-it-yourself spreadsheet won’t survive diligence.

How is the report different from a consultant’s cost review?+

Price, speed, and reproducibility. A boutique review runs €5–15k and takes 2–4 weeks; AI-specific or enterprise work runs well past €30k and 4–8 weeks — and both deliver opinions you can’t re-run. Traken’s report is generated from your reconciled data by a deterministic engine — every number traceable to SQL and invoice lines, reproducible bit-for-bit, from €490, in a day. When a number is challenged, you re-run it instead of scheduling a call.

Do you cover cloud costs (AWS/Azure/GCP)?+

Yes — upload your billing export (FOCUS, CUR 2.0, BigQuery export); no cloud credentials needed. We reconcile finalized bills to the invoice, allocate to teams and features, and detect billing-visible waste. We deliberately don’t do real-time dashboards, commitment trading, or workload rightsizing — we reconcile truth, not guesses.

Do you see our prompts?+

No. Token counts, hashes, and business metadata only. Our collector config is open for inspection.

Do you change our production traffic?+

Never. Read-only, off-path. Remediations ship as config diffs with eval plans; you apply them.

Do you guarantee savings?+

No one honestly can. We show dollar-ranked opportunities grounded in reconciled cost — and after you ship a fix, we counterfactually reprice your workload against the next invoice, so the savings ledger tracks what actually landed in your P&L.

Where does our data live?+

EU infrastructure, EU-resident narration model by default. A premium model lane is available opt-in.

09 — close $0.00

Upload one invoice. Watch it reconcile.