Startup Due Diligence Checklist for Investors

When my team and I studied failed companies, we found that founders consistently reported moments when they felt something was off but couldn't justify slowing down. Progress elsewhere made it feel irresponsible. The purpose of diligence isn't to catch liars. It's to close the gap between what a founder believes is true and what the data actually shows.

Startup due diligence is the process of verifying claims, assessing risk, and building conviction before committing capital. Every investor has a version of this process. Most are incomplete. The ones who avoid expensive mistakes have a systematic version that covers the same ground, in the same order, every time.

This checklist covers the six dimensions that matter most for early-stage startup diligence: team, market, product, traction, financials, and legal. Each section includes what to verify, what to watch for, and where the difference between self-reported and verified data matters most.

Team Diligence

The team is the single most cited factor in early-stage investment decisions, and the hardest to evaluate objectively. A strong pitch can mask a weak team. A quiet founder can be the most capable operator in the room.

Verify these items:

• Founder backgrounds: employment history, domain expertise, prior exits or failures
• Co-founder dynamics: how long they have worked together, how they divide responsibilities, whether there's a clear decision-maker
• Key hires: who's already on the team vs. who's planned. Are the first hires aligned with the current lifecycle phase?
• Advisor relationships: are advisors actively engaged, or are they names on a slide?
• Reference checks: talk to people who have worked with the founders before, not just people the founders nominate

What to watch for: Founders who can't clearly articulate who does what. Co-founder conflicts that surface as vague answers about decision-making. Advisory boards that exist on paper only.

Market Diligence

Market diligence answers two questions: is the market big enough to matter, and is the timing right?

Verify these items:

• Total addressable market (TAM): is the calculation based on credible third-party data, or is it a top-down guess?
• Serviceable addressable market (SAM): what segment of the TAM can this company realistically reach with its current product and go-to-market?
• Competitive market: who else is solving this problem, how are they funded, and what's the differentiation?
• Market timing: is demand growing, stable, or contracting? What evidence supports the timing hypothesis?
• Regulatory considerations: are there regulatory risks or tailwinds that affect the market trajectory?

What to watch for: TAM calculations that start with a trillion-dollar number and assume a small percentage. If you have seen one "we only need 1% of a $500B market" slide, you have seen a thousand. Markets where the "competition" section says "no direct competitors" (there are always competitors, even if they solve the problem differently). Founders who can't name their top three competitors by name.

Product Diligence

Product diligence assesses whether the company has built something that works and whether it can continue to build what the market needs.

Verify these items:

• Product status: is it live, in beta, or still a prototype? Get access to the actual product if possible.
• User feedback: what are real users saying? Look for unfiltered feedback, not curated testimonials.
• Technical architecture: is the product built to scale, or will it need to be rebuilt at the next stage?
• IP protection: are there patents, trademarks, or trade secrets? Is the IP assigned to the company (not the founder personally)?
• Roadmap: what comes next, and does the planned development align with the lifecycle phase the company is in?

What to watch for: Products that have been "almost ready to launch" for months. Technical debt that will require a rewrite before scaling. Features built for investor demos rather than actual user needs.

Traction Diligence

Traction is where self-reported data creates the most risk. This is the section of diligence that catches the most investors off guard. Founders present metrics in the most favorable light, which is rational, but it means investors need to verify independently.

Verify these items:

• Revenue: ask for bank statements or accounting software access, not just a revenue number in a pitch deck
• User/customer count: how's "customer" defined? Is it paying users, free trial signups, or waitlist entries?
• Growth rate: verify the time period and the baseline. 300% growth from 10 to 40 customers is different from 300% growth from 1,000 to 4,000.
• Retention and churn: monthly and annual. Cohort retention curves matter more than blended averages.
• Unit economics: customer acquisition cost (CAC), lifetime value (LTV), and the ratio between them. Are these numbers calculated from real data or projected from assumptions?

For a deeper framework on which traction metrics matter by stage, the key principle is that Phase 3 companies should show acquisition metrics while Phase 5 companies should show efficiency metrics. What counts as meaningful traction depends on where the company is in the lifecycle.

What to watch for: Revenue figures that include signed contracts not yet invoiced. Customer counts that blend paying and free users. Growth rates measured from a cherry-picked start date. LTV projections based on three months of data.

Platforms that track verified activity data (like Startup Science) can pre-qualify traction claims before formal diligence begins. When a company's lifecycle phase is determined by actual platform behavior rather than self-reporting, the baseline for diligence is already more reliable.

Financial Diligence

Financial diligence at the early stage is less about audited statements and more about understanding how the company spends money and how long the current plan is funded.

Verify these items:

• Burn rate: monthly cash expenditure. Is it consistent with the team size and activity level?
• Runway: at current burn, how many months until the company needs additional capital?
• Cap table: who owns what, are there any unusual terms, and is the equity structure clean?
• Prior funding: how much has been raised, from whom, on what terms? Are there any convertible notes or SAFEs with unusual provisions?
• Use of funds: where will this round go? Does the allocation match what the company needs to reach the next lifecycle phase?

What to watch for: Burn rate that doesn't match the stated team size. Cap tables with excessive advisor equity or complex structures that will create problems at the next round. Prior round terms that create unexpected dilution or governance complications.

Legal Diligence

Legal diligence is often deferred at the early stage, which creates risk that compounds as the company grows.

Verify these items:

• Corporate structure: is the entity properly formed, and is it in a jurisdiction favorable for fundraising?
• IP assignment: has all intellectual property been formally assigned from founders and contractors to the company?
• Employment and contractor agreements: are all team members under proper agreements with IP assignment, non-compete (where enforceable), and confidentiality clauses?
• Material contracts: any customer contracts, partnership agreements, or vendor commitments that create obligations?
• Pending or threatened litigation: any legal disputes current or expected?
• Regulatory compliance: is the company operating in a regulated space, and if so, is it compliant?

What to watch for: Founders who haven't assigned IP to the company. Contractors who built core product components without IP assignment agreements. Companies operating in regulated industries without legal counsel. Prior investors with unusual governance rights.

Using This Checklist

Apply this checklist consistently across every deal, not just the ones that feel risky. The purpose isn't to find reasons to say no. It's to build a complete picture so the investment decision is informed rather than instinctive.

For investors working with pre-qualified startups from ESO-backed ecosystems, several of these verification steps (team, product status, traction, lifecycle phase) may already be addressed by the platform data. Verified activity data doesn't replace due diligence, but it gives the process a more reliable starting point.

Diligence starts with better data. See how Startup Science pre-qualifies startups with verified activity tracking.

Startup Science's internal analysis of 89,000+ founder outcomes found that investors who logged 20 or more hours of structured due diligence before committing capital saw roughly 2x the return multiple compared to investors who completed diligence in under 10 hours, primarily because thorough diligence filtered out cap table issues, undisclosed liabilities, and team misalignment before they became portfolio losses.

Due diligence isn't one-size-fits-all. The categories stay the same, but the weight you put on each one shifts depending on where the startup sits in its lifecycle. An investor spending 40% of diligence time on financials for a pre-product company is wasting effort on numbers that don't exist yet. An investor ignoring legal structure at the exit stage is setting up for a deal that collapses in escrow. The table below maps Startup Science's seven lifecycle phases against the six diligence dimensions. "Primary" means this dimension should receive the most diligence hours at that phase. "Secondary" means it's important but shouldn't dominate. "Baseline" means a standard review is sufficient.

How to read this table: At Phase 1 (Vision), the startup has no product and no revenue. The only things you can evaluate are the founders' ability to execute and whether the market they're targeting actually exists. Financial diligence at this phase is limited to checking the cap table and runway. By Phase 4 (Standardization), the company has paying customers and is building repeatable processes. Financial and operational diligence dominate because you're evaluating whether the business can scale without breaking. At Phase 7 (Exit), legal and financial diligence consume most of the timeline because the transaction itself depends on clean documentation, defensible IP, and auditable books. This weighting model comes from patterns across Startup Science's data set of 89,000+ founders. Investors who matched their diligence depth to the company's lifecycle phase spent less total time and caught more material issues than investors who ran the same checklist regardless of stage.

A checklist tells you what to examine. Red flags tell you when to dig harder. These are specific patterns within each diligence dimension that experienced investors treat as signals of hidden risk. A single red flag doesn't kill a deal, but it changes the depth of the conversation you need to have.

Team Red Flags

• Founder vesting hasn't started or was backdated. If the founders gave themselves fully vested shares on day one, there's no mechanism to protect the company if one of them leaves. Backdated vesting is worse because it suggests someone anticipated a problem.
• Key technical roles are filled by contractors with no transition plan. A startup that outsources its core technology to an agency or freelancer doesn't own its own product in a meaningful sense. Ask who has commit access and whether those people are full-time employees.
• Co-founder left in the last 12 months and the equity wasn't clawed back. This creates a dead weight on the cap table. It also raises the question of why they left. If the founder can't give a clear, specific answer, there's a story you're not hearing.
• No one on the team has operated in this market before. First-time founders are fundable. First-time founders in a regulated or technically complex market with zero domain connections are a significantly higher risk.

Market Red Flags

• TAM slides cite a single analyst report with no bottom-up validation. A founder who quotes a Gartner number but can't explain how many potential customers exist in their specific segment hasn't done the market work.
• The competition slide shows "no direct competitors." Every market has competitors. If the founder can't identify them, they either haven't looked or they've defined their market so narrowly that it might not exist.
• Customer interviews happened more than 12 months ago with no recent revalidation. Markets shift. A pain point that was acute in 2024 might be solved by three new entrants in 2025. Ask when the last customer discovery conversation happened and what it revealed.

Product Red Flags

• No usage data available for a product that's been live for 6+ months. If the team can't show DAU/WAU, session length, or feature adoption, they either aren't tracking it or the numbers are bad enough to hide.
• Product roadmap is a feature list with no prioritization framework. This signals a team that builds what customers request rather than what the business needs. Ask how they decide what to build next and who makes the final call.
• Core IP is built on top of a third-party platform that could change terms. Startups built entirely on Salesforce, Shopify, or another platform's API are one terms-of-service update away from an existential crisis. Evaluate the dependency depth.
• Single technical founder with no engineering hires after 18+ months. Building a product that scales with one developer isn't sustainable. It's also a bus factor of one. If that person gets sick for a month, the product stops.

Financial Red Flags

• Revenue is growing but gross margin is declining. This often means the company is buying growth through unsustainable discounting, excessive services revenue, or infrastructure costs that scale faster than revenue.
• Burn rate doubled in the last quarter with no corresponding milestone. Spending more should produce more: more customers, more product, more revenue. If the burn increased and nothing else did, ask where the money went.
• Customer concentration above 40% from a single account. One customer providing 40%+ of revenue means the startup is one contract cancellation away from a crisis. This is especially dangerous if that customer is also a reference or early design partner.
• SAFE or convertible note stack from 3+ prior rounds with no priced round. Excessive note stacking creates cap table complexity that can surprise founders and new investors during conversion. Ask the founder to walk you through every outstanding instrument and the conversion math at various scenarios.

Legal Red Flags

• IP assignment agreements don't exist for early employees or contractors. If the first version of the product was built by a contractor who never signed an IP assignment, the company may not legally own its own product. This is the single most common legal issue in early-stage diligence.
• Corporate structure was set up in a non-standard jurisdiction without a clear tax or regulatory reason. Delaware C-Corp is the standard for U.S. venture-backed startups for a reason. Unusual structures create friction during future rounds and exits.
• Pending or threatened litigation that the founder didn't disclose upfront. The lawsuit itself might be manageable. The failure to disclose it isn't. It raises immediate questions about what else hasn't been shared.
• Employee classification is ambiguous (1099 vs W-2). Misclassification of full-time workers as contractors creates tax liability, potential back-pay claims, and regulatory risk. This is a fixable issue, but it has to be fixed before close.

Operational Red Flags

• No documented processes for customer onboarding, support escalation, or incident response. This is fine at 5 customers. At 50, it means every new customer creates chaos. Investors at Phase 4+ should expect written SOPs for core workflows.
• Customer churn above 5% monthly with no retention analysis. High churn isn't automatically a deal-killer if the company knows why it's happening and has a plan. High churn with no analysis means the team either doesn't track it or doesn't understand it.
• Key vendor relationships are handshake agreements with no contracts. A startup that relies on a critical infrastructure provider, channel partner, or data source without a written contract is exposed to sudden terms changes.

Use this checklist as a working document during your diligence process. Each item maps to one of the six diligence dimensions. Check off items as you verify them. Items marked with a flag (!) are areas where red flags most commonly appear.

Team Diligence

• [ ] Founder backgrounds verified (LinkedIn, references, prior company records)
• [ ] Vesting schedules in place for all founders, with cliff and acceleration terms documented
• [ ] (!) IP assignment agreements signed by every person who contributed to the product
• [ ] Key person risk assessed (what happens if the CEO or CTO is unavailable for 90 days?)
• [ ] Organizational chart reviewed, including open roles and hiring plan
• [ ] (!) Co-founder departures and equity disposition documented
• [ ] Advisory board agreements and compensation reviewed
• [ ] Reference checks completed (former employees, co-investors, customers)

Market Diligence

• [ ] Bottom-up TAM calculation verified (not just analyst report citation)
• [ ] (!) Competitive positioning mapped with specific alternatives, including "do nothing"
• [ ] Customer interviews or discovery data reviewed (dates, sample size, methodology)
• [ ] Market timing thesis evaluated (why now, and what changed in the last 2 years?)
• [ ] Regulatory environment assessed (current and pending legislation)
• [ ] Distribution channels identified and validated with evidence

Product Diligence

• [ ] Product demo completed (live, not recorded)
• [ ] (!) Usage metrics reviewed: DAU/WAU, retention cohorts, feature adoption
• [ ] Technical architecture reviewed (scalability, security, third-party dependencies)
• [ ] Product roadmap reviewed with prioritization rationale
• [ ] Customer feedback data reviewed (NPS, support tickets, feature requests)
• [ ] (!) Platform dependency risk evaluated (API terms, vendor lock-in)
• [ ] Code quality assessment (for Series A+): technical debt, test coverage, deployment frequency

Financial Diligence

• [ ] (!) Revenue verified against bank statements or payment processor records
• [ ] Unit economics calculated: CAC, LTV, gross margin, payback period
• [ ] (!) Customer concentration analyzed (no single customer above 30% of revenue)
• [ ] Burn rate and runway calculated from actual bank balance and monthly spend
• [ ] Cap table reviewed in full, including all outstanding SAFEs, notes, and options
• [ ] Financial projections stress-tested (what happens at 50% of projected growth?)
• [ ] Historical financials reconciled (P&L, balance sheet, cash flow for all available periods)
• [ ] Outstanding debt, liens, or obligations documented

Legal Diligence

• [ ] Corporate formation documents reviewed (articles of incorporation, bylaws)
• [ ] (!) All IP assignments collected and verified (founders, employees, contractors)
• [ ] (!) Pending or threatened litigation disclosed and assessed
• [ ] Material contracts reviewed (customer agreements, vendor agreements, leases)
• [ ] Employee/contractor classification verified (1099 vs W-2)
• [ ] Option pool size and remaining authorized shares confirmed
• [ ] Data privacy compliance assessed (GDPR, CCPA, SOC 2 if applicable)
• [ ] Insurance coverage reviewed (D&O, E&O, cyber liability)

Operational Diligence

• [ ] Core workflows documented (onboarding, support, billing, incident response)
• [ ] (!) Customer churn rate and retention analysis reviewed
• [ ] Key vendor and partner contracts in place (not handshake agreements)
• [ ] Security practices assessed (access controls, data encryption, backup procedures)
• [ ] Compliance requirements identified and current status verified
• [ ] Infrastructure scalability evaluated against growth projections

Frequently Asked Questions

How long does startup due diligence typically take?

Seed-stage diligence typically takes two to four weeks. Series A diligence runs four to eight weeks. The timeline depends on how organized the founder is and how many items require follow-up. The biggest time sink isn't the review itself; it's waiting for documents the founder doesn't have ready. Founders who build a data room before their first investor meeting can compress the timeline by 40% or more. The VC due diligence checklist covers exactly what documents to prepare in advance.

What documents should a startup prepare for due diligence?

At minimum: articles of incorporation, cap table, all outstanding SAFEs or convertible notes, IP assignment agreements for every contributor, financial statements (or management accounts if pre-audit), material customer contracts, employment agreements, and a current organizational chart. For product companies, add usage metrics, a technical architecture overview, and security documentation. For Series A and beyond, investors also expect audited financials, board meeting minutes, and a detailed financial model. Build a shared data room (Notion, Google Drive, or a purpose-built tool like Carta) organized by category before your first meeting.

What's the most important part of startup due diligence?

It depends on the lifecycle phase. For pre-product companies (Phase 1 and 2), team diligence matters most because there's limited data on everything else. For post-revenue companies (Phase 3+), financial and product diligence carry the most weight because investors can verify claims against actual data. Across all stages, the single highest-impact diligence item is the cap table review. A clean cap table with proper vesting, clear IP ownership, and no undisclosed instruments is the foundation that every other dimension rests on. Our startup evaluation framework maps the full scoring methodology investors use across all six dimensions.

How do investors verify startup revenue claims?

Three ways. First, bank statements. Investors ask for 12 months of bank or payment processor records and reconcile them against the reported revenue figures. Second, customer calls. Investors will contact 3 to 5 customers directly (with the founder's permission) to confirm contract terms, satisfaction, and renewal intent. Third, third-party data. For SaaS companies, investors sometimes request access to Stripe, Baremetrics, or ChartMogul dashboards to see real-time revenue data independently. Founders should expect all three. The ones who volunteer access to financial dashboards upfront create significantly more trust than the ones who share a self-built spreadsheet. For more on which traction metrics investors prioritize, see our dedicated guide.

How does due diligence differ between seed and Series A rounds?

Seed diligence is lighter in scope but heavier on team evaluation. Investors spend most of their time on founder backgrounds, problem validation, and early product traction. Financial diligence at seed is primarily a cap table review and burn rate analysis because there's limited revenue history to audit. Series A diligence is broader and more formal. Investors expect 12+ months of financial history, retention cohorts, detailed unit economics, a full legal review, and often a third-party technical assessment. The legal dimension scales dramatically: Series A investors review every material contract, examine IP chain of title, and assess regulatory compliance in ways that seed investors typically skip. For context on how the investor evaluation process works end-to-end, see our guide on due diligence for startups.

Sources

1. Angel School, Due Diligence Checklist for Angel Investors, 2024. angelschool.vc
2. Kruze Consulting, Startup Due Diligence: Your Guide to VC Funding Success, 2024. kruzeconsulting.com
3. Holloway / Ewing Marion Kauffman Foundation research (Wiltbank & Boeker), Business Due Diligence for Angel Investments, 2023. holloway.com