FAQ
The questions I get most, answered plainly.
#We already have QA — why bring you in?
Your QA team almost certainly covers the deterministic surface. The gap is the LLM feature: no golden set, no judge, no gate — prompt changes ship on vibes. I add the eval layer to your existing pipeline, and your team owns it when I leave.
#Do you work in our stack or yours?
Yours. Your repo, your CI, your conventions. Every engagement ends with a runbook and a walkthrough — the deliverable is a system your team runs without me.
#What does it cost?
There’s no fixed price list because scope varies too much for one to be honest. Every engagement is quoted in writing after a short scoping call. See Pricing.
#How fast can you start, and how long does it take?
Booking one engagement at a time — check the availability chip on the site. The audit is about a week; sprints run ~2–3 weeks; full builds ~4–8 depending on scope. Something visible ships in the first two weeks.
#What if the evals show our AI is fine?
Then you ship with evidence instead of hope — that’s the win. The suite stays in CI catching the regression that would have landed six weeks later.
#Do you take full-time roles?
Open to the right one. The site has a “Hire me” mode and a résumé — the capabilities here are the ones I’d bring to a team on day one.