Services / Code Review Before Due Diligence

Find out what investor due diligence will find in your code, before they do.

An investor is interested, and at some point their engineer is going to open your repository. I read the code first, the way that reviewer will, and give you a ranked list of what they're likely to flag. You get to fix it, explain it, or price it in while it's still your finding and not theirs.

Focused review up to $600. Full two-day review $1,500.

A hand holds a magnifying glass over a neat stack of code printouts, revealing a red crack running through the lines under the lens

Due diligence is the worst time to learn about your own code

It's also when a lot of founders do. The demo went well, the partner meeting went well, and then someone you've never met spends a few days in your code and sends the investor a list. Now every item on it is a negotiating point, and you're answering questions about code you may not have written line by line.

This is especially true if you built the product with Cursor, Claude Code, Lovable, Bolt, Replit, or another AI coding tool. The tool wrote what you asked for. It usually didn't write the server-side check behind the browser check, the authorization rule on every record, or the error handling for the input nobody tried. A demo never exercises those paths, and a technical reviewer goes looking for them first.

Over the shoulder of an engineer reviewing code on a laptop, with one block highlighted in red, while a founder watches from across the conference table

What does an investor's technical review look at?

Whether the product can carry the business plan without breaking, and whether the team can keep it running. Code style matters much less than you'd think. These are the areas I read, because they're the ones that turn into findings.

Claims versus enforcement

Your deck says data is private, plans have limits, and only admins can do certain things. I check whether the server actually enforces each one on every path, or only the screen hides it.

Security and customer data

Secrets reachable from the browser or the repository, records any logged-in user can read by changing an ID, sign-in that can be brute-forced, and input the server takes on trust.

What breaks at real scale

Queries without indexes, lists without paging, outside calls without timeouts, and silent failures nobody would hear about. A reviewer asks what happens at ten times today's users.

Who understands the code

Whether you can explain how your own system works, and what happens if the one person who knows a critical part leaves. Reviewers now also ask how much of the code an AI tool wrote, and whether anyone reviewed it before it was merged.

What happens when due diligence finds problems?

In a technical due diligence report, a red flag is a finding serious enough to change the deal: customer data any user can reach, a limit the pricing depends on that one path skips, secrets in the repository, or a product claim the code doesn't enforce. A problem found in diligence doesn't always kill the deal. It can just as easily get the round repriced, delayed, or tied to fixes. A reviewer expects some issues in an early-stage codebase. What hurts is a serious problem nobody on your side knew about, because it raises the question of what else you don't know.

The same finding reads very differently depending on who raises it.

Found by their reviewer

  • You hear about it for the first time in their report.
  • It becomes a negotiating point you didn't prepare for.
  • The investor starts asking what else nobody knows.

Raised by you first

  • "We found this, here's what we changed, and here's what's still on the list."
  • You decide what to fix, what to explain, and what to price in.
  • You come across as a founder who knows the product.

Not every round includes a code review. Plenty of pre-seed and seed investors never look at the repository. If yours hasn't asked, this review still tells you whether the product is ready for the customers that money is meant to bring in.

The kind of thing I find

These came from short looks at real apps and from my own product. Each one is a gap between what the product says it does and what it actually does, which is exactly what a diligence reviewer is paid to look for.

An inspector with a clipboard checks a newly finished office before anyone moves in

A plan limit that a restore walked straight past

A CRM in closed beta capped its free tier at 50 records. Creating a record at the limit was blocked, but restoring deleted ones from the recycle bin skipped the check, and I ended up at 58.

Read the CRM case study
A tasting-room counter with a back-room door left slightly open

A Private setting that sometimes saved as public

In a community app, I created two posts with Private selected. One saved as private and the other appeared publicly, with no error. Nobody knew to check.

Read the beverage app case study
A velvet rope that blocks only half of an office hallway, with a person walking past the open side

A safety rule enforced in the menu, not the code

In my own product, sensitive actions were hidden from an AI agent's tool menu and a comment called that a safety rule. Tracing a call through dispatch showed a known tool name could still run.

Read the write-up

A technical due diligence report example: one finding

Every finding in my report is written up the same way, so you can fix it or hand it to an investor as it stands. This one is the privacy issue from the beverage app, written up the way the report would present it.

Fix now

Posts marked Private are sometimes saved as public

What I found
Two posts created with Private selected didn't save the same way. One was stored as private. The other appeared on the public map and feed, with no error and no warning to the user.
How to reproduce
  1. Sign in as a new user and create a post with Private selected.
  2. Create a second post the same way.
  3. Sign out, or sign in as a different user, and check the public map and feed. One of the two posts is visible.
Why it matters in diligence
It contradicts a promise the product makes to its users about their data, and it fails quietly, so nobody on the team knew to look. A reviewer can find it in minutes by trying the setting a few times.
What to change
Trace the visibility value from the form to the stored record and find where it gets lost. Make the server treat a missing value as private rather than public, then add a test that creates private posts and confirms none of them show up in public queries.

Two ways to do it

If you have a specific worry, start with the focused review. If you want the whole codebase read before you share repository access with anyone, book the full review.

Up to $600

Focused review

For one question you already suspect a reviewer will ask, like whether customer data is really separated between accounts, or whether your payment flow trusts the browser.

  • $150 an hour, billed in 15-minute increments
  • Four-hour hard cap, so $600 at most
  • Plain-language written findings within three business days
  • Optional 30-minute call about the findings, included
$1,500

Full AI App Review

Two full days reading and running the whole codebase across security, performance, stability, and data integrity: the same ground an investor's reviewer covers.

  • A ranked report: fix now, fix soon, fine to leave
  • Steps to reproduce every finding
  • A 90-minute walkthrough, which is also good practice for the technical call
  • One fixed price, invoiced when the report is delivered

When should I get the review?

Before anyone outside the company has repository access, and early enough to fix what turns up. A few weeks before you expect a term sheet is better than a few days.

A founder works through a printed report marked up in red pen, with sticky notes, a laptop, and a desk calendar with days circled
1

Tell me where the raise stands

Use the request form to describe the product, the stage of the conversation, and any date you're working toward. I'll tell you which review fits and whether the timing works.

2

Share read-only access

After we agree on scope, give me read-only repository access or a source export. I'll sign an NDA if you want one. Don't put passwords or tokens in the form.

3

Fix, explain, or disclose

You get the ranked report and we go through it together. The report is yours: fix first and say nothing, or share it along with what you've already changed. That's your call.

What to have ready before their review

Reviewers ask for evidence, not reassurance. If you can hand over these six things the day they ask, the technical part of diligence goes faster and reads better.

An architecture overview

One page: the main parts of the system, where customer data lives, and every outside service the product depends on.

A known-issues list with a plan

What you know is weak, why it was built that way, and when you'll fix it. Known problems with a plan get priced in; surprises cause trouble.

A dependency and license list

The libraries and services you rely on, their versions and licenses, and anything unmaintained.

Who owns what

Who understands each critical part, how much of the code an AI tool wrote, and how changes were reviewed before they shipped.

Access and secrets

Who can reach production and admin tools, where secrets live, and what happens when someone leaves.

Test, deploy, and restore evidence

How a change reaches production, which tests run on the paths that handle money and permissions, and the date of the last backup restore you actually tested.

What this review isn't

It doesn't replace the investor's own diligence, and I can't promise what their reviewer will conclude. It isn't a penetration test, a compliance certification, or a legal review, so IP assignments and contractor agreements are a question for your lawyer. I don't change your code under the review; if you want help fixing what it finds, that's quoted separately.

If you're on the other side of the table, buying or investing in a software company, you want Technical Due Diligence instead.

Read your code before their reviewer does.

Tell me about the product and where the raise stands. The request and the first conversation are free.

Request a pre-diligence review