Fixed prices, published.
No open-ended meters, no "book a call to find out." The free teardown sets the exact quote for everything after it.
Free Teardown
Where everyone starts
A 20-minute recorded video of a senior architect walking your repo and architecture: 3 concrete findings, ranked by what to fix first, and a straight fix-or-rebuild verdict. Async, no sales call, no slide deck.
- Delivered within 72 hours of your slot
- Read-only repo access, or just a URL
- NDA signed first if you want one
- You keep the video either way
Hardening Sprint
If the teardown finds real gaps
One to two weeks, fixed scope, fixed price, set by your teardown and agreed before any money moves. I fix what blocks the deal on your calendar, in this order:
- Auth and tenant isolation that actually isolates
- Payments integrity: charges reconcile
- Data safety: backups tested, migrations sane
- Secrets out of the client and the repo
- Monitoring and alerts before users find bugs
- Deploy hygiene: a bad deploy can't sink you
Plus the trail, what makes it stick: docs a new hire can follow, tests that guard the fixes, a runbook for the 2 a.m. moment.
The guarantee, in writing The sprint names its critical issues up front. Resolved, or the balance is refunded. No partial-credit language.
Senior Oversight Retainer
Most sprint clients keep me on
Your team keeps shipping fast with AI. Someone senior makes sure it keeps holding.
- Weekly review of AI-generated PRs
- Architecture decisions, before they calcify
- Incident support when it matters
- Hiring help: JD reviews, tech interviews
No rebuild pitch, ever. If the honest answer is "you're in decent shape," that is the answer you get.
Investor or acquirer? There is a separate fixed-price Due-Diligence Read ($1,500, 5 business days).
Common questions
- Why is the teardown free?
- Because it's the honest way to show you what senior eyes catch, and it's how I decide whether a Hardening Sprint would actually help you. Some teardowns end with "you're in decent shape." Either way you keep the video and the findings, no strings.
- What happens after the teardown?
- You get the recording with 3 concrete findings and a fix-or-rebuild verdict. If a sprint makes sense, I'll name exactly what it covers and a fixed price. If it doesn't, I'll say that. No follow-up sequence, no pressure.
- What do you need access to?
- A read-only repo invite (I reply with the username) or just your live URL. I sign your NDA before touching anything sensitive. You can revoke access the moment the teardown lands.
- Will you tell me to rebuild from scratch?
- Almost never, and I don't sell rebuilds, so there's no incentive to say it. Most AI-built products need targeted hardening, not a rewrite: the smallest set of changes that make it hold.
- Why only 2/week teardowns?
- Each one is real senior hours on your actual code, and the 72 hours promise only works with a cap. If the week is full you get the next slot, with a date, not a waitlist limbo.
- What stacks do you cover?
- Most modern stacks: JavaScript/TypeScript, Python, Go, the usual clouds and databases, and products built with Cursor, Lovable, Replit, Bolt, or Claude. This is architecture-first, stack-second.
- Who is this NOT for?
- Pre-product founders who need someone to build the app; that's a dev shop. And agencies looking for white-label capacity should email me directly instead of requesting a teardown.
Find out where you actually stand.
A senior architect walks your system and records what he finds: 3 concrete findings and a fix-or-rebuild verdict, in your inbox within 72 hours. Free.
no sales call · NDA available · 2/week cap · no rebuild pitch