Skip to main content

You built fast with AI.
Now it has to hold.

An enterprise pilot, a due-diligence request, real load, a first hire. Someone senior walks the system first.

Get your free teardown Fixed prices, published
Teardown · representative findings 3 / 3
  1. 01

    Live payment key hardcoded in config.ts

    Anyone who reads the repo can charge your customers. Rotate today, move it to environment variables.

    fix today
  2. 02

    Payment errors are caught and dropped

    A failed charge still shows the customer a success screen. Nobody is alerted.

    this sprint
  3. 03

    One file runs auth, billing, and email

    Changing login touches billing. Split along the seams, no rewrite needed.

    plan it

Verdict Fix, don't rebuild. Two weeks of targeted hardening.

Patterns seen across 50+ AI-built codebases. Read the full list

Dan Podina, systems architect

Dan Podina, systems architect. A person, not a scanner.

Twenty years designing and fixing backend systems in fintech, healthcare, and SaaS, the industries where "it mostly works" does not survive an enterprise security review. Review bots flag patterns. What they can't give you is a verdict: what to fix first, what to leave alone, and whether the codebase is ready for the deal on your calendar.

Experience
20 years, backend
Industries
fintech · healthcare · SaaS
Also
Founder, GQLTeam
Capacity
2/week teardowns · 2–3 retainer seats
How I work

Senior eyes on your actual code. Free.

3 concrete findings and a fix-or-rebuild verdict, recorded on video, within 72 hours. How it works

Private repo is fine — I'll reply with a username for a read-only invite. NDA first if you want one.

2/week cap • recorded video within 72 hours of your slot • no sales call • no rebuild pitch

Fixed prices, published

Start free. Scale only if it earns it.

Every step is priced before it starts. Nothing is bought on this site: the teardown decides what, if anything, comes next.

  1. Free Teardown

    $0

    20-minute recorded review of your repo and architecture: 3 concrete findings and a fix-or-rebuild verdict within 72 hours. Async, no sales call.

    cap 2/week

    Get your free teardown

  2. Hardening Sprint

    from $2,500 fixed

    1–2 weeks, scope set by your teardown: auth and tenant isolation, payments integrity, data safety, secrets, monitoring, deploy hygiene. Ships fixes plus the trail: docs, tests, runbook.

    exact quote comes from the teardown

    Full scope

  3. Senior Oversight

    $2,000/mo

    Your architect on call: weekly review of AI-generated PRs, architecture decisions, incident support, hiring help. Most sprint clients keep me on.

    2–3 client seats, total

    How it works

No rebuild pitch, ever. If the honest answer is "you're in decent shape," that is the answer you get.

From the trail

Findings, dated and kept.

All findings
  1. Is my AI-built codebase well designed? Count the files each change touches (2026) The one design signal a non-engineer can measure: how many files change per small change. Three or four means separable parts; fifteen means tangled. In git.
  2. Is my Lovable app secure? Six checks to run before launch (2026) Six checks before a Lovable app launches: RLS on every table, no secret key in the bundle, auth settings, bucket policies, keys server-side, a tested backup.
  3. What does it cost to make an AI-built app production-ready in 2026? In 2026 an AI-built app costs $0 to $1,500 to diagnose, $2,500 to $8,000 for a two to three week fix pass, and $2,000 to $15,000 a month for senior oversight.
  4. Before you raise: what technical due diligence asks of an AI-built codebase (2026) Technical due diligence on an AI-built codebase in 2026 asks five things: who understands the code, is it secure, can it be restored, can it be maintained, and can it survive a hire. Here is the evidence to prepare.

Not ready to share a repo? Take the 60-second check.

Six questions, no repo access, an instant read on where your product is most likely to crack: scaling, reliability, security, or hiring.

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.

Get your free teardown Prefer to talk first? Book 15 minutes

no sales call · NDA available · 2/week cap · no rebuild pitch