Updated · Published · 11 min read

Venture Capital Due Diligence Checklist: 7 Areas, Red Flags

A VC due diligence checklist by area: team, market, product, traction and metrics, financials, legal and cap table, and deal terms, with red flags to check.

Your venture capital due diligence checklist: 2025 edition

A VC due diligence checklist covers seven areas: team, market, product, traction and metrics, financials, legal and cap table, and deal terms. At seed, most of the weight sits on the team and the market. From Series A on, investors test the numbers. Below is what to check in each area, the red flags, and a checklist to copy.

Who wrote this. We make Soreno, an AI interviewer for finance and consulting interviews. This is a general checklist, not legal advice. Rules and model documents are linked where we use them.

How VC due diligence works

Most funds move a deal through the same steps, faster at seed and slower at growth stage.

  1. Screen. Is it in the fund's stage, sector and check size? Is the market big enough to return the fund?
  2. First meetings. The team, the problem and why now. Most deals end here.
  3. Deep diligence. Data room review, customer calls, product demo, a look at the model and the cap table.
  4. Investment committee. The deal lead writes up the case, the main risks and what has to go right.
  5. Term sheet, then confirmatory diligence. Lawyers check corporate records, IP, contracts and the cap table before closing.

What gets the most weight changes with the stage:

StageWeighs mostUsually thin
Pre-seed and seedTeam, market, insightRevenue, metrics
Series AEarly traction, retention, sales motionProfit
Series B and laterGrowth efficiency, unit economics, marginsNothing. All of it is checked

Team

  • Founder and market fit. Why are these people the ones to win this market? Look for earned insight: years in the industry, a problem they lived, or a technical edge. Red flag: a pitch any smart team could give, with no reason this team sees what others miss.
  • Roles and ownership split. Who builds, who sells, who decides. Red flag: a sole technical founder who is not full time, or equal splits with no clear decision maker.
  • References. Call former managers, colleagues and early customers, including people the founders did not suggest. Red flag: references that only praise, or vague answers about why someone left.
  • Hiring. Can they recruit people better than themselves? Look at the first ten hires. Red flag: key roles open for months with no plan.
  • Commitment and vesting. Founder shares should vest so a departing founder does not keep a full stake. Red flag: no vesting, or founders still working other jobs.

Market

  • Size, built bottom up. Number of possible customers times what each would pay a year. Compare it with any top-down figure. Red flag: a market size taken only from an analyst report with no customer count behind it.
  • Why now. A change in technology, regulation, cost or behavior that makes this possible today. Red flag: no answer, or an answer that was just as true ten years ago.
  • Competition and substitutes. Direct rivals, incumbents adding the feature, and the spreadsheet or manual process it replaces. Red flag: "we have no competitors."
  • Path to a large outcome. Venture returns come from a few very large wins, so the market has to support a company worth many times the post-money valuation. Red flag: a good business with a ceiling well below that.

Product and technology

  • The problem and how painful it is. Is this a must-have or a nice-to-have? Customer calls answer this better than the deck. Red flag: customers who like it but would not notice if it disappeared.
  • Demo and roadmap. See the real product, not slides. Ask what ships in the next two quarters. Red flag: the demo is a prototype the deck calls a product.
  • Defensibility. Network effects, proprietary data, switching costs, regulation or deep technology. Red flag: the moat is "we will move faster."
  • Technical risk. Architecture, security, reliance on one vendor or one model provider, and the cost to serve each customer. Red flag: a core feature that depends on another company's platform it cannot control.
  • IP ownership. The company, not the founders or a past employer, should own the code and inventions. Check signed invention assignment agreements for everyone who built it. Red flag: code written before incorporation with no assignment.

Traction and metrics

Ask for the monthly data, not the summary slide. The core checks for a software or subscription business:

  • Revenue quality. Recurring versus one-off, contracted versus pilots, and how concentrated it is. Red flag: one customer above about a quarter of revenue, or "ARR" that includes unsigned pilots.
  • Growth. Month-over-month and year-over-year, and whether it is speeding up or slowing down. Red flag: growth that came from one launch or one big deal.
  • Retention. Logo retention (customers who stay) and net revenue retention (revenue from last year's customers this year, including upsells, minus churn and downgrades, divided by their revenue last year). Red flag: cohorts that shrink every month.
  • Unit economics. Customer acquisition cost (sales and marketing spend divided by new customers) and the payback period (months of gross profit to earn back that cost). Red flag: payback that keeps getting longer as spend rises.
  • Burn efficiency. The burn multiple is net burn divided by net new ARR in the same period, a ratio set out by David Sacks of Craft Ventures (The Burn Multiple, April 2020). Lower is better. Red flag: burning several dollars for each new dollar of ARR.
  • Engagement. For consumer and usage products: daily and monthly active users, and how often people come back. Red flag: sign-ups that grow while active use stays flat.

Financials

  • Bank balance and runway. Cash on hand divided by monthly net burn. Check it against the bank statement. Red flag: runway that only works if the round closes this month.
  • Gross margin. Revenue minus the direct cost to deliver it. Software usually runs much higher than services or hardware. Red flag: margins that fall as the company grows.
  • The model. A monthly plan for the next 18 to 24 months with hiring, spend and revenue assumptions you can trace. Red flag: a hockey stick with no driver behind it.
  • Use of funds. What this round buys: which hires and milestones, and where it leaves the company for the next round. Red flag: a raise sized to the valuation the founders want, not to a milestone.
  • Debt and obligations. Loans, venture debt, convertible notes, unpaid taxes and large commitments. Red flag: liabilities that appear only in the lawyer's review.
  • Cap table. Every holder of shares, options, warrants, SAFEs and notes, fully diluted. Red flag: a messy table with many small holders, or a founder team already below a controlling stake at seed.
  • SAFEs and notes. Y Combinator's SAFE, a common early instrument, converts into shares when the company raises a priced round (Y Combinator, SAFE documents). Model the conversion at this round's price. Red flag: many SAFEs with different caps nobody has modeled.
  • Founder tax elections. Founders with restricted stock that vests often file an 83(b) election, which must be filed no later than 30 days after the shares are transferred (26 CFR 1.83-2). Red flag: elections nobody can find.
  • Securities filings. For an offering relying on Regulation D, a company must file Form D within 15 days after the first sale (SEC, Filing a Form D notice). Check past rounds were filed.
  • Corporate records. Charter, board minutes, stock issuances approved by the board, and the option plan. Red flag: shares or options promised by email but never approved.
  • Contracts, disputes and compliance. Key customer and supplier contracts, any lawsuits, data privacy, and licenses the business needs. Red flag: a change-of-control clause that lets a big customer walk after an acquisition.

Deal terms

Venture financings in the US are often papered on the NVCA model documents: the certificate of incorporation, stock purchase agreement, investors' rights agreement, voting agreement and right of first refusal and co-sale agreement (NVCA, Model Legal Documents). The terms to check:

  • Valuation and the option pool. Pre-money plus the new money gives post-money. If the option pool is enlarged before the round, its dilution falls on existing holders, so the effective pre-money is lower than the headline.
  • Liquidation preference. Who gets paid first in a sale and how much. A 1x non-participating preference returns the money invested or converts to common, whichever is more. Participating preferences take both.
  • Anti-dilution. Protects investors if a later round is priced lower. Broad-based weighted average adjusts for the size of the down round. Full ratchet resets to the new price and is much harsher on founders.
  • Board and control. Who sits on the board and which decisions need investor approval (protective provisions).
  • Pro rata and information rights. The right to invest in later rounds and to get regular financials.
  • Red flags on either side. Stacked or participating preferences, full ratchet anti-dilution, investor control of the board at an early stage, or a valuation so high the next round is hard to clear.

What founders should have in the data room

If you are raising, put these in one folder before the first partner meeting:

  1. Deck and a one-page memo of the business
  2. Monthly financials, bank statements and the operating model
  3. A metrics sheet with the definitions you use (ARR, retention, CAC)
  4. Fully diluted cap table, plus every SAFE and note
  5. Charter, board consents, option plan and 83(b) elections
  6. Signed IP assignment agreements for every founder, employee and contractor
  7. Top customer contracts and a list of customers investors can call
  8. Product demo access and a short architecture overview
  9. Any litigation, debt or regulatory matters

A clean data room shortens diligence and makes the business look run well.

How VC interviews test due diligence

Venture interviews often hand you a startup and ask whether the fund should invest. Interviewers are checking that you can pick the two or three risks that decide the deal, not recite every item above. A strong answer:

  1. States the investment case in one sentence
  2. Names the biggest risk in each of team, market and traction
  3. Says what you would ask for to test each risk
  4. Ends with a decision and what would change your mind

Practice it out loud. Writing a memo is easier than defending one live when the partner pushes back.

Copyable checklist

Copy this into a doc and tick it off as you go.

Team

  • Founder and market fit, in one sentence
  • Roles, ownership split and who decides
  • Reference calls, including ones the founders did not suggest
  • Hiring plan for the next 12 months
  • Founder vesting in place

Market

  • Bottom-up market size (customers x price per year)
  • Why now
  • Competitors, incumbents and the manual substitute
  • A path to an outcome far above the post-money valuation

Product

  • Customer calls on how painful the problem is
  • Live demo and next two quarters of roadmap
  • Defensibility beyond speed
  • Technical and platform risks, cost to serve
  • IP owned by the company, assignments signed

Traction and metrics

  • Monthly revenue, recurring versus one-off
  • Customer concentration
  • Growth rate and trend
  • Logo retention and net revenue retention by cohort
  • CAC and payback period
  • Burn multiple

Financials

  • Cash, monthly net burn and runway, checked against the bank
  • Gross margin and its trend
  • 18 to 24 month model with traceable drivers
  • Use of funds tied to milestones
  • Debt, notes and other obligations

Legal and cap table

  • Fully diluted cap table
  • SAFE and note conversion modeled at this round's price
  • 83(b) elections on file
  • Form D filed for past rounds
  • Board approvals for all stock and options
  • Key contracts, litigation, privacy and licenses

Terms

  • Pre-money, post-money and option pool effect
  • Liquidation preference and participation
  • Anti-dilution type
  • Board seats and protective provisions
  • Pro rata and information rights

Frequently asked questions

What is due diligence in venture capital?

It is the review a fund does before investing: the team, market, product, traction, financials, legal records and deal terms. The goal is to find the few risks that decide whether the company can become large enough to matter to the fund.

How long does VC due diligence take?

It depends on the stage and the fund. Seed deals can move in days or a few weeks. Later rounds with more data, customer calls and legal review usually take longer.

How is seed due diligence different from Series A or B?

At seed there is little data, so investors judge the team, the insight and the market. From Series A on, they check revenue quality, retention, unit economics and burn, and later rounds add margins and efficiency at scale.

What do VCs check on the cap table?

Who owns what on a fully diluted basis, how SAFEs and notes convert, how much the option pool dilutes, whether every issuance was approved by the board, and whether the founders still own enough to stay motivated.

What should founders prepare for due diligence?

A data room with financials and bank statements, a metrics sheet with definitions, the cap table and every SAFE or note, corporate records, IP assignments, top contracts and customer references.

Is this the same as private equity due diligence?

The areas overlap, but private equity buys mature companies, often with debt, so it goes much deeper on cash flow, quality of earnings and the debt the company can carry. See our private equity case study guide.

Related guides

Interview questions to practice

VC Due Diligence Checklist: 7 Areas and Red Flags (Copyable) | Soreno