Code no one owns
Features a model wrote that nobody on the team fully understands, can safely change, or wants to be on call for.
Your team shipped fast with AI. Now the codebase sprawls, the token bill creeps, and nobody quite trusts the parts a model wrote. I find what's actually costing you and clean it up.
Features a model wrote that nobody on the team fully understands, can safely change, or wants to be on call for.
Prompts and calls bolted on without a budget. Inference spend that grows quietly and outpaces what the feature is worth.
LLM features that demo well and break in production: no evals, no guardrails, flaky output, and no one sure how to fix it.
A read of where AI is helping you and where it is costing you: the generated sprawl, the token and inference spend, the features that will not survive scale. You leave with a prioritised cleanup plan, useful whether or not I do the work.
The work, on one fixed scope: cut the token bill, refactor the sprawl into code the team can own, and put evals and guardrails around the features that matter. Two to three weeks, one deliverable.
If it makes sense to keep it clean, I can stay on as a retainer.
Two decades of making systems that have to hold up in the real world: firmware on vehicles, a regulated medical platform, a commerce platform rebuilt to hold its load. AI sprawl is that same problem with a newer cause, code that grew faster than anyone could reason about it. Cleaning that up is the job I have always done. More on keeping systems healthy →
from €6,000
One to two weeks. Findings and a prioritised cleanup plan.
€18,000-28,000
Two to three weeks, one fixed deliverable. Net of VAT. Full engagement model →
A 30-minute call to see whether a Spring Clean is worth it. If it is not, I'll say so.