Did you change the model?

No. Same model family, same tier. Every number in this case study was achieved against the original model choice. Model swaps are on the table later, once the structural waste is gone — but they are the second move, not the first.

Is a 59% reduction typical?

It’s at the high end of what we see, and it came from a clean follow-up run after the full change-set landed. The realistic band across a representative sample of happy paths is 40–60% on dispatcher-style copilots. On unusually prompt-heavy or tool-heavy setups we’ve seen larger reductions; on already-tight stacks, smaller.

How long did the engagement take?

Core changes landed in roughly four weeks. The longer tail — observability, evaluation harness, handover — ran a further four to six. Short, scoped, outcome-based; the client team operates the system now without us.

Can you do this on our stack without access to our source code?

No. Engagements require access to the orchestration layer — system prompt, tool definitions, and a representative sample of production traces. Read-only is fine for the audit phase; write access comes later if we agree on the change-set.

What’s the smallest version of this engagement?

A two-to-four-week audit with a prioritised punch list and a working proof-of-concept on one of the items. No long-term commitment. If you like the punch list, we do the implementation. If not, you keep the punch list.

We cut a dispatch copilot’s token bill by 59% — same model, same product

body{background:#050510;color:#fff;font-family:system-ui,sans-serif;padding:2rem;max-width:720px;margin:0 auto;line-height:1.6}We cut a dispatch copilot’s token bill by 59% — same model, same productToken consumption per happy path went from 75K to under 26K. The bill collapsed. The model stayed.Continue