Max Kushner · Co-founder · revenue systems & agentic interfaces
Building the unglamorous systems that keep the numbers honest.
Billing, reconciliation, revenue recognition — the plumbing nobody puts on a conference slide, but without which everything leaks. And lately, the other kind of plumbing: making a product usable by agents, and knowing whether they got the job done rather than whether the tool returned 200. I write about the unshowy work of making sure the number on the dashboard is actually true.
- Agents wrote our backlog. Then the telemetry audited me, and the loop got one wrong.
Part 2 of 2. What agents asked for when nothing in our MCP toolset fit, three of my own claims that didn't survive the telemetry, and the loop that now drafts pull requests from it - including the first one it got wrong. Plus what I'd instrument on day one.
- The tool responded. The agent didn't get anywhere.
Part 1 of 2. 98.9% of calls to our MCP server succeeded, and agents were still working around it. What PostHog's MCP analytics showed us in the first four weeks, and the three fixes that came out of it.
- Keeping the numbers honest
Numbers don't need a liar to drift. They go wrong on their own — and the job is to build the systems that catch them before anyone reports them.
- The realization-rate haircut
Bookings are a promise; revenue is a fact. The discipline of a single, honestly-applied realization rate is what keeps the two from being confused.