✓ Tier 1 · the entry point
QA Readiness Audit
You suspect quality is a liability, but you can’t see the whole picture, and you’re not ready to hire someone to find out.
Two weeks, fixed price. I examine how you ship, where it breaks, and how exposed your AI features are, then hand you a risk map and a 90-day roadmap you can act on with or without me.
Book a call✓ what you get
A clear-eyed read of your quality, and a plan.
- Repo, CI, and release-process review: how code goes from a finished feature to a real user, and where that path leaks defects.
- Bug-history analysis: what’s broken recently, what keeps breaking, and the patterns underneath it.
- Risk map of critical user paths: the journeys that, if they break, cost you a customer or a deal.
- LLM-feature risk assessment: for your AI features: eval coverage, prompt regression exposure, injection surface, and cost blind spots.
- Written report with a prioritized 90-day QA roadmap: sequenced by risk and effort, not a wish list.
- 60-minute readout call: worst findings first, then the roadmap, then your questions.
✓ who it's for
Built for AI startups with no QA hire yet.
- You’re an AI-native team with no dedicated QA hire, anywhere from two founders to ~30 engineers.
- Something broke in production recently and you want to know what else is waiting.
- You’re raising, scaling the team, or chasing an enterprise deal that asks hard questions about quality.
- You want a senior second opinion before you commit to building a whole QA function.
Explicitly out of scope
- Building the automation framework (that’s the Foundation Sprint).
- Fixing the defects we find, the audit names and prioritizes them.
- Ongoing testing or release sign-off (that’s the Fractional retainer).
✓ the outcome
You stop guessing. You get a ranked list of what will actually break, what it would cost, and exactly what to do about it in the next 90 days.
✓ questions
Before you book.
What do I actually walk away with?
A written report (risk map, findings worst-first, and a prioritized 90-day roadmap you can execute yourself), plus a 60-minute readout call. It’s yours whether or not we ever work together again. The completeness is the point.
Is the audit just a sales pitch for the sprint?
No. The roadmap is structured so you could run it yourself in two quarters. If the right move is the Foundation Sprint, the report says so and why; if it isn’t, it says that too. Saying “you don’t need that yet” is the most useful thing I can do for you.
How much of my team’s time does it take?
A short kickoff, read access to your repo, CI, and issue tracker (Jira, Linear, GitHub Issues, or similar), and one async questionnaire (15 fields). I work from there and come back with the report. Roughly 1–2 weeks elapsed, with minimal load on your engineers.
Do you need production access?
No. I prefer staging and read-only access, and I decline production credentials unless they’re genuinely necessary, in writing. Security hygiene is part of the product, you can ask for my vendor-security one-pager.
One bad regression away from a lost week.
Book a 20-minute intro call. I’ll tell you honestly whether I can help and what the right next step is: audit, sprint, or nothing yet.