Pre-Investment Due Diligence: A Builder's-Eye View

I spent over a decade on the inside of tech companies.

I was the operator inside the org chart, and I know the problems a deck rarely shows: tech debt that isn't pitched as debt, founder dependencies that aren't called out, AI claims that turn out to be thin wrappers around someone else's model.

Now I'm building a DD practice from the operator's side.

This piece outlines the framework I'd apply, the things documents alone do not show, and what operator-led DD should look like. It's written for VCs evaluating how to add this lens to their existing process - and for founders who want to understand what an operator-led assessor would actually look at.

What Documents Alone Do Not Show

Most pre-investment DD follows a familiar pattern: management interviews, document review, customer calls, expert calls, and a polished deck of findings. It's thorough on what's documentable - financials, contracts, market data, customer concentration.

Some questions do not show up in documents:

• How the team actually makes decisions
• Whether the architecture will scale or buckle
• Whether the founders will execute or freeze under pressure
• Where critical knowledge is concentrated in one person
• Whether the AI strategy is real or marketing

The 5-Phase Operator DD Framework

Phase 1: Operational Diagnostic

Typical duration: ~2-3 days. Actual time depends on target company size, data room quality, and management availability.

An operational review can stop at the org chart. Mine starts there.

What I actually look for:

• Decision flow: Who really makes which decisions, regardless of titles? Founder bottlenecks limit how far a company can scale.
• Process maturity: Do "processes" exist as documented artifacts nobody follows? Or as actual operating rhythm? The gap between the two predicts post-close pain.
• Tribal knowledge mapping: What lives only in one person's head? Quantify the bus factor on critical functions.
• Communication patterns: Do teams talk to each other or only through leadership? Cross-functional friction is invisible in interviews but visible in workflow analysis.
• Cultural cracks: Companies look great when revenue's growing. Cultural problems surface during the first hiring crunch, the first big customer loss, or the first AI competitor.

Output: Operational maturity assessment with prioritized risks.

Phase 2: Technical Architecture Review

Typical duration: ~3-5 days. Larger codebases, complex infra, or AI-heavy stacks extend this phase.

Technology moves fast, so a technical review needs an evaluator who works with current tools and practices.

What I actually look for:

• Architecture vs. business plan alignment: Does the architecture support the next 18 months? Or only the last 18?
• Tech debt that's been rebranded: "Fast iteration" sometimes means "we never refactored." Decode the language.
• Real engineering practices: Code review culture, deployment frequency, incident response - these signal engineering maturity better than headcount.
• Build vs. buy decisions: Companies that built what they should have bought reveal poor judgment. Companies that bought what they should have built reveal weak technical leadership.
• Hidden infrastructure costs: Cloud bills, third-party APIs, data licensing - costs that grow with usage and surprise teams at scale.

Phase 3: AI Readiness Assessment

Typical duration: ~3-5 days. Depth varies by how central AI is to the company's value proposition.

Companies can pitch AI capabilities they are not positioned to deliver.

Reading the AI section of the deck and taking management's word is not enough. Operator-led AI DD evaluates against the 5 dimensions of AI readiness:

1. Data foundation: Is the data clean enough for AI to produce useful output?
2. Team capability: Does the team understand AI well enough to use it correctly?
3. Infrastructure: Can existing systems support AI integration?
4. Strategy & governance: Is there an AI strategy beyond "we use ChatGPT"?
5. Use case identification: Are AI use cases tied to measurable business outcomes?

Phase 4: Team & Founder Evaluation

Typical duration: ~2-4 days. Includes founder interviews and decision-archeology sessions.

This is the highest-stakes module.

Management interviews capture stated philosophy. Operator DD also looks at decision patterns under pressure.

• Founder decision archeology: What are the 3 hardest decisions you made in the last 12 months? How did you make them? What would you do differently? The answers reveal more than any psychometric.
• Conflict resolution: When co-founders disagree, how does it actually resolve? Unresolved founder conflict is a risk worth understanding early.
• Hiring philosophy: Show me the last 5 senior hires. Who interviewed them? Who decided? The answer reveals whether founders can let go.
• What scares them: Ask founders what would kill the company. Vague answers ("execution") reveal weak strategic clarity. Specific answers ("we have 90 days to fix our churn before LTV inverts") reveal operators.
• Bus factor: If the founder disappeared for 60 days, what breaks? The answer measures the company's actual independence.

Phase 5: Risk Inventory & Post-Close Roadmap

Typical duration: ~2-3 days. Synthesis across the prior phases into a written, actionable inventory.

This is where operator DD ends with more than findings: it ends with an actionable post-close roadmap.

What goes in the inventory:

• Key-person dependencies that need redundancy planning
• Process gaps that will fracture at the next growth stage
• Technical debt requiring immediate attention vs. eventual refactor
• AI claims requiring deal terms (e.g., milestone-based payments)
• Cultural risks needing hiring or coaching intervention
• Governance gaps requiring board attention

Scope note. This describes an operational and technical assessment of a target company. It is not investment advice, securities advice, a valuation, or an audit, and it is not a recommendation to make or refrain from making any investment. The investment decision remains entirely with the investor.

The output: An execution-readiness verdict, plus a prioritized 90-day post-investment value creation plan. If you invest, here's what to fix first.

Red Flags an Operator Tests For

Some patterns worth testing for, often invisible in a deck:

1. The "Architectural debt" Hidden in Velocity

Companies bragging about deploy frequency sometimes have it because nothing is actually tested. Investigate: do they have automated tests? Code review culture? Or is "ship fast" a euphemism for "ship without rigor"?

2. The Founder-As-Hero Dependency

If the founder personally closes every enterprise deal, personally interviews every senior hire, personally makes every product trade-off - the company has no business after the founder. Look for what the founder has successfully delegated.

3. AI as Marketing, Not Capability

Test: ask the head of engineering to explain how AI is integrated into the core product. If the answer is "we use ChatGPT for X" without describing data flows, model selection, fine-tuning approach, or governance - the AI claim is marketing.

4. Process Theater

Companies show you their Notion workspace with 47 documented processes. Ask people on the ground: do you actually follow this? Where the answer is no, the documented processes are theater - performed for investors, ignored in practice.

5. Customer Concentration Risk Hidden in Logos

"We have 50 customers" sometimes means "1 customer is 60% of revenue, 49 are 40%." Look at revenue concentration, not logo count.

6. The Fast-Growth Cultural Crack

Companies that grow very fast often carry unresolved cultural debt - hires made too fast, processes broken to ship, leadership stretched thin. The crack isn't visible until growth slows. Plan for it.

What Modern Deal Pace Requires

Deals often move faster than a multi-week engagement allows.

So the assessment is scoped to the deal: one read of how the company runs, timed to the deal and agreed in writing before the work starts.

Operator-led DD is one experienced person plus a network of specialists when needed, which keeps coordination overhead low and lets the work run to the deal timeline.

Why DD-to-Portfolio Continuity Matters

The pattern I want to build my practice around: VCs engage me for pre-investment DD. I surface what's real about operational maturity, technical posture, and team scalability. If they invest, I continue with the portfolio company to help fix the issues I diagnosed.

Why this design works:

• No re-onboarding cost. The same person already understands the company in depth.
• Credibility with founders. The DD report becomes a roadmap, not a hit job - because the assessor stays to help execute it.
• Continuity for the VC. One point of contact for both pre- and post-investment work on a highest-risk asset.
• Aligned incentives. An assessor who has to live with the findings has a reason to be calibrated. Because the same person may also do the post-close work, ask for the evidence behind each finding.

This pattern doesn't fit every VC's model. But for funds investing in companies that need operational support to reach the next stage - it's substantially more efficient than serial consulting engagements with different vendors at each stage.

Frequently Asked Questions

What's operator-led DD vs traditional DD?

Traditional DD applies frameworks from analyst perspective. Operator-led DD applies pattern recognition from someone who's built and scaled the systems being assessed. Both have value - operator-led DD adds a view on how the company executes and produces a post-close roadmap.

Should I always do operator DD or sometimes pure analyst?

Pure analyst DD wins when: financial rigor matters most, deal is in a sector you're not familiar with, or regulatory complexity dominates. Operator DD wins when: scaling/execution risk is the main question, AI capabilities need verification, or post-investment value creation is part of the thesis.

How honest can DD really be when fees come from the VC?

As with other paid professional reviews, reputation is the currency. A DD assessor who hides issues to please a fund loses every future engagement once those issues surface post-close. The economic incentive aligns with honesty over flattery, regardless of who pays.

Can DD findings change a deal?

Findings can change what an investor decides, and sometimes they should. The value of operator-led DD is an accurate read on execution readiness: what the team can and cannot execute, which risks are fixable, and what to fix first. It does not say whether to invest. That decision, and the deal terms, stay with the investor and their advisers.

Related Reading

• Enterprise AI Transformation: The Operator's Playbook - The companion flagship for post-investment AI transformation in portfolio companies.
• AI Readiness Assessment Guide - The diagnostic framework underneath the AI readiness section of any DD.
• The Operator-Consultant Method - The four-phase methodology behind post-investment portfolio support.

Sources

This guide describes a practitioner framework and the author's own approach. It does not rely on external statistics or studies. The phase durations and engagement formats are indicative and depend on the deal.

Working With May on a Live Deal

If you have a deal in motion that needs operator-led DD, the full DD service overview covers the six modules and how the assessment is scoped to the deal. Post-close, the same person can be brought into the portfolio company as an interim or fractional product and program manager.

About the author: May Mor is a developer, product manager, and organizational consultant with 10+ years scaling tech companies across fintech, digital banking, and adtech - building the onboarding for an R&D team growing from 30 to 150 developers and serving a digital bank with 100K+ customers. She holds an M.Sc in Intelligent Systems & AI from Afeka and is certified in Organizational Consulting from Bar-Ilan University. She runs Scale with May: interim and fractional product and program management for tech companies, and operational due diligence for investors.