About
Who reads your prompts
Every audit is read and written by one person. This page exists so you know who that is before you paste anything.
Justin Davis
I have spent the last few years building with Claude daily — across long-running code sessions, research work and production workloads on the API — and watching bills and usage limits behave in ways the documentation never quite explains. The pattern that kept repeating was that the expensive part was almost never the work; it was everything being dragged along beside it.
I started writing those findings down, first for teams I was working with and then here. The audit is the same exercise done on your transcript instead of mine: read twenty exchanges closely, work out where the context went, and say plainly what to change.
This site is maintained by hand, not generated. Pricing and limit figures carry a last-verified date because they move, and a page you can trust to be current is worth more than a page that guesses.
How to reach me
Email is the only channel — there is no booking link anywhere on this site, by design. Questions about an audit get answered in the same thread as your report.
Independence
This is not an Anthropic property and carries no affiliation with them. Nothing here is sponsored, and the advice is not tuned toward pushing you onto a bigger plan — most audits recommend spending less.