Investors don’t fund mess. Or rather: they fund it, but they price it in. Every piece of unfinished, abandoned, or quietly broken infrastructure in your engineering org becomes a discount on your valuation, and a credibility tax in technical due diligence. Most founders don’t realize how much of this they’ve accumulated until a serious diligence call rips through their stack.

Six to twelve weeks before you go out, run a deprecation pass. The goal isn’t to ship new things. The goal is to delete, archive, and finish — to make your engineering org look like the one you’ve been telling investors it is.

Why This Matters More Than You Think

Series A diligence calls almost always include a “show me your repos and your infrastructure” round. The investors aren’t usually trying to catch you out — they’re trying to understand the operational maturity of the team. What they see in those calls shapes their model of how fast you can scale post-funding, which directly affects valuation, board structure, and how much rope they’re willing to give the founders.

A clean engineering footprint signals that your team has discipline, judgment, and the ability to focus. A messy one signals the opposite, even if the actual product is great. The good news: most of this can be fixed in a few weeks of focused work.

The Deprecation List

This is the list I run with founders before fundraising. Not all of it will apply, but most will. Work through it ruthlessly:

  • The half-built feature you’ve been promising — finish it, hide it, or kill it. No third option
  • The vendor you’ve outgrown but never migrated off — Heroku at 100K users, Auth0 at scale, you know who you are
  • The “temporary” service that became permanent — name it, document it, or delete it
  • The intern’s code path that nobody owns — either someone owns it or it goes
  • The repos with no README, no CI, and no recent commits — archive them
  • The third-party integrations you turned off but didn’t actually remove — delete the keys, kill the webhooks, drop the unused tables
  • The feature flags that have been “on for everyone” for over six months — collapse them into the code
  • The dashboards nobody looks at — turn them off and see if anyone notices
  • The microservice you regret — either invest in it or merge it back
  • The cron job that’s been failing silently for weeks — you have one, you just haven’t found it yet

The Question to Ask About Each One

For every item on the list, the question is the same: “Would I be embarrassed if a sharp investor asked me to walk through this on a screen-share?” If yes, fix it now. If no, leave it alone — diligence isn’t an excuse to over-engineer.

The bar isn’t perfection. The bar is “this looks like the work of a team that is in control of its codebase.” A few rough edges are fine. A pattern of abandoned half-things is not.

What Not to Do During This Pass

Don’t refactor for elegance. Don’t add documentation to working code that nobody is going to read again. Don’t migrate to the new framework you’ve been wanting to try. The deprecation pass is about subtraction, not addition. Every hour you spend adding things during this period is an hour you’re not spending finishing or removing things, and finishing and removing is what investors actually notice.

Resist the urge to make your codebase pretty. Make it honest instead. An honest codebase is one where every running piece has a reason to exist and an owner who can explain it. Most of your team’s energy in the run-up to fundraising should go into proving that your engineering org is small, focused, and disciplined — not into showcasing how clever your architecture is.

The Other Half: People

The same logic applies to your team and process. The contractor whose contract you keep extending without a clear end date, the meeting that everyone hates but nobody cancels, the OKR that hasn’t moved in six months — these get noticed too, and they say something about how the team operates. A short pre-fundraising pass on people and process is just as valuable as the engineering one. Sometimes more.

The Compounding Benefit

Here’s the underrated part: most of this work pays off whether you raise or not. A team that does an annual deprecation pass is faster, calmer, and harder to surprise with a stale system that no one remembered owning. The fundraising deadline is just a forcing function for the cleanup you should be doing anyway. After your first one, schedule it on the calendar.

Let’s Talk

If you’re going out in the next three months and want a second pair of eyes on what to kill before diligence, that’s the kind of work I do with founders right before they raise. A short pre-fundraising review usually surfaces three or four things that would have come up in diligence and would have cost you something. Reach out and let’s clean it up before the calls start.