I recently met a founder who burned two priceless weeks chasing "just one more piece of information" for an investor who was taking only a 15 percent minority stake. The review spiraled from an architecture walk-through to line-by-line code sampling and vendor audits - none of which would have changed the price. That detour stalled roadmap work and almost derailed the deal. The lesson for me was: depth must follow deal structure.

Minority growth investments - a light touch

When an investor buys a non-controlling slice, the goal is to protect against downside while letting the team keep its speed. For a minority position, when the investor doesn't steer the roadmap, one focused day on-site - after 2-3 days of prep reviewing things like architecture docs, pen-test summaries, cloud-spend trends and some proof the IP really belongs to the company - is usually enough to protect downside without draining sprint capacity.

Majority control buy-outs - a deeper dive

Swap the minority check for a controlling position and the conversation sharpens. Once the buyer owns the steering wheel, their return hinges on how quickly they can scale the platform and widen its margins. Beyond the light-touch checks above, you'll now layer on deeper work. For example, sample the code-base, dig into cloud cost-allocation rules, benchmark security maturity against peers, and verify that the business-continuity plan has been tested in practice.

Carve-outs - the heaviest lift

The heaviest lift is a carve-out. The central question becomes: Can the carved-out platform/product/service stand alone on Day 1 and still integrate on Day 100? This demands data-ownership maps, migration run-books, identity separation, and interim service-level agreements between seller and the new entity. Here, nothing can be left to chance. Separation readiness as well as integration readiness should be tested.

Stake sets the depth, stage sets the granularity

Founders often ask if the funding round itself (Series A, B or C) dictates how deep a Tech Due Diligence digs. Not really.

Stake size dictates how far the lens zooms in. A minority Series C can be lighter than a majority Series A recap because the investor's control - and therefore risk - differs.

Stage, meanwhile, dictates the resolution of evidence. At Series A, it's enough to provide high-level cloud-cost trends; by Series B, investors expect a full FinOps dashboard, because the detailed, tag-level usage data should be in place by then.

Short rule: structure determines depth, stage determines detail.

A safeguard against scope creep

Before any review starts, I insist on a one-page scoping note: deal type, a materiality threshold ("Would this risk change price or kill the deal?"), a checklist of evidence we will and will not request, and the calendar time the team can spare. Once both sides sign off, that page is the shield when curiosity balloons into a fishing expedition.

Common traps I still see

  • Over-engineering a minority deal - deep dives that hijack sprint capacity but don't shift valuation.
  • Letting stage override structure - a minority Series C should still be lighter than a majority Series A if the stake is smaller.
  • Finding shared-service entanglements too late in carve-outs - In many companies, different business units rely on central, shared services that live in the parent organization. Dependency mapping must begin in week one, not week four.

A practice worth adopting

Add a simple scope matrix to the data room with three columns: Must-have evidence, Nice-to-have, Out-of-scope. Complete it before the first investor call and change it only by joint agreement. One sheet often preserves both momentum and goodwill.

What scope mistakes have you lived through? Was a review too shallow, too deep, or did it miss the real risk entirely? Share the story - collective scars make the best guidebook.

Need help drafting a scope matrix or pressure-testing the one you have?

Let's talk.

Mini-Glossary

  • Minority stake: Investor owns <50% and lacks board control.
  • Carve-out: A carve-out transaction happens when a company sells (or spins off) only a portion of its business (a product line, a subsidiary, a regional unit, etc.) rather than the whole firm. That piece is literally "carved out" of the parent's tech stack, data, people, contracts, and processes.
  • FinOps dashboard: Cloud-cost metrics tied to revenue or teams.
  • Materiality threshold: Cut-off where a risk could change price or kill the deal.

Next in the Playbook

Edition 3 will examine the metrics that matter - the handful of deployment, incident and cost signals that predict whether a platform will scale without nasty surprises. Subscribe and it will land in your inbox.

Originally published on the Tech Due Diligence Playbook newsletter on LinkedIn.