All case studies
Metabase saving Issue #86814 open, triaged

Every follow-up paid for the whole conversation again.

21–64%saved per follow-up turn
≈ $17–51per 1,000 turns, by turn number

At 100,000 follow-up turns a month, that is about $1,700 to $5,100 a month, depending on how long conversations run.

Metabot caches well inside a turn. Across turns it didn't, because the conversation it sent back was not exactly the one it had sent before. A context block with a date to the microsecond wasn't saved, thinking blocks were dropped, parallel tool calls were split, and a failed tool result lost its error flag.

So the first call of every follow-up turn read only the tools and system prompt (12,600 tokens) from the cache and wrote the rest of the conversation again, at the 1.25× cache-write price.

The fix is to replay each turn exactly as it was sent, so every turn starts with everything the last one cached. That changes how conversations are stored, which is their team's call, so we reported it as an issue with the evidence and offered our patch.

Measured saving per follow-up turn (whole turn, all calls)
turnsavedper 1,000 turns
221–31%≈ $17
346%≈ $28–44
456–64%≈ $33–51

The same thing in your product

Caching only works when a request starts with exactly what the last one sent. Here the history changed between turns; in PostHog and Chatwoot it was a timestamp near the top of the prompt. If your product has long conversations, this is the first thing we check.

Find out how much you could save.

Tell us what you run and roughly what you spend on AI each month. If an audit isn't worth your time, we'll say so.

Get a free audit [email protected]