Due diligence at the early stage is a different animal than what growth-stage or buyout funds do. You are not auditing years of financial statements or stress-testing mature business models. You are making a judgment call about a team, a market, and a product that may barely exist yet, with limited data and significant uncertainty.
That does not mean due diligence should be casual or unstructured. The best early-stage investors are rigorous in their process. They just know where to focus their rigor. A seed-stage company will not have three years of audited financials, but it should have a clear thesis about why the market opportunity exists and credible evidence that the team can execute against it.
This checklist covers every major area of early-stage due diligence. Not every item will apply to every deal. Pre-seed investments require a lighter touch than Series A. Deep tech companies need more product diligence than SaaS businesses. Use this as a comprehensive framework and calibrate the depth based on the specific opportunity.
Team Evaluation
At the early stage, the team is the investment. Markets shift, products pivot, and business models evolve. What persists is the founding team's ability to navigate uncertainty, attract talent, and execute under pressure. This is where you should spend the most time.
Founder Background and Fit
- What is each founder's relevant domain expertise? Have they worked in or deeply studied the problem space?
- Do the founders have complementary skills? Is there a clear technical lead and a clear business lead, or is there significant overlap that could create gaps?
- What is their track record of execution? Have they built and shipped products before, even if in different contexts?
- Why are they working on this specific problem? Is there a personal connection, deep frustration, or unique insight that drove them to start this company?
- Have the founders worked together before? If not, how did they meet and how long have they been collaborating?
Founder Resilience and Character
- How do the founders handle disagreement with each other? Ask for specific examples.
- What is the hardest professional challenge each founder has faced, and how did they navigate it?
- Are the founders coachable? Do they take feedback well, or do they become defensive when challenged?
- What do former colleagues, managers, and direct reports say about them? (Back-channel references are essential here.)
- How do the founders talk about competitors? Respectful awareness signals maturity. Dismissiveness is a red flag.
Team Composition
- Beyond the founders, who are the first five to ten hires? Are they strong individual contributors or early managers?
- Is the engineering team capable of building what the product roadmap requires?
- Are there critical skill gaps? What roles need to be filled in the next six to twelve months?
- What is the team's equity split? Is it roughly fair given contributions, or are there imbalances that could cause problems later?
- How is the team structured for decision-making? Is there a clear leader, or is it consensus-driven?
Market Analysis
You are not just evaluating whether this company can succeed. You are evaluating whether this market can produce a venture-scale outcome. A great team building in a small or declining market is still a bad investment for a fund that needs large outcomes.
Market Size and Dynamics
- What is the total addressable market, and how is the company defining it? Is the TAM calculation bottoms-up (based on potential customers and pricing) or tops-down (based on industry reports)?
- What is the serviceable addressable market? Of the total market, what portion can this company realistically capture in the next five to seven years?
- Is the market growing, stable, or contracting? What is the growth rate, and what is driving it?
- Are there secular tailwinds that make this market more attractive today than it was five years ago? Regulatory changes, technology shifts, behavioral changes, and demographic trends all create openings.
Market Timing
- Why is now the right time for this product? What has changed that makes this solution viable or necessary today?
- Is the market too early (customers are not ready to buy), too late (incumbents are entrenched), or well-timed?
- Are there recent exits or funding rounds in adjacent spaces that validate market timing?
- What is the adoption curve likely to look like? Is this a land-and-expand play, a viral consumer product, or an enterprise sales motion?
Customer Segmentation
- Who is the ideal customer profile? How specifically can the founders describe their target buyer?
- What is the customer's current workflow or solution? What are they doing today to solve this problem?
- How much pain does this problem cause? Is it a "nice to have" improvement or a "must solve" urgency?
- What is the customer's willingness and ability to pay? Have the founders tested pricing, even informally?
Product and Technology Diligence
At the early stage, the product may be an MVP, a prototype, or even just a design mockup. The question is not whether the product is polished. It is whether the technical approach is sound and whether the team can build what needs to be built.
Product Status and Roadmap
- What is the current state of the product? Live with paying customers, in beta, prototype, or concept stage?
- Does the product work as demonstrated? Request a live demo rather than relying on recorded walkthroughs.
- What is the product roadmap for the next twelve months? Is it realistic given the team size and funding?
- What are the biggest technical risks on the roadmap? Which features or capabilities are genuinely hard to build?
Technology Architecture
- Is the technology architecture appropriate for the current stage and scalable for the next stage?
- Is the team building on proven technology stacks, or are they betting on experimental frameworks?
- What are the key technical dependencies? Are there third-party services or APIs that the product relies on heavily?
- Does the team own their core intellectual property, or are they building on top of someone else's platform in a way that creates risk?
Defensibility and Moats
- What makes this product technically difficult to replicate? Is there proprietary data, a novel algorithm, unique integrations, or deep domain-specific logic?
- Does the product create switching costs or network effects that strengthen over time?
- How long would it take a well-funded competitor to build something comparable? Months, years, or is it more about execution speed than technical barriers?
- Is there any protectable IP (patents, trade secrets, proprietary datasets)?
Financial Review
Early-stage financial diligence is less about auditing numbers and more about understanding the company's financial logic. You are evaluating whether the business model makes sense, whether the unit economics can work at scale, and whether the funding plan is realistic.
Current Financial Position
- What is the company's current monthly burn rate? How does it break down between payroll, infrastructure, and other costs?
- How much runway does the company have at the current burn rate? Is the raise they are doing sufficient to reach meaningful milestones?
- What revenue (if any) is the company generating? Is it recurring, one-time, or project-based?
- Are there any outstanding debts, convertible notes, or SAFEs from previous rounds?
Unit Economics
- What is the customer acquisition cost (CAC)? How is the company acquiring customers today, and what does each customer cost to acquire?
- What is the lifetime value (LTV) of a customer? Even at the early stage, there should be a thesis about how much revenue each customer will generate.
- What is the LTV:CAC ratio? For most SaaS businesses, you want to see a path to 3:1 or better.
- What is the gross margin? For software companies, this should be 70%+ at scale. For companies with significant COGS, understand the margin structure.
- What is the payback period on customer acquisition? How long does it take to recoup the cost of acquiring each customer?
Financial Projections
- Does the company have financial projections? Review them, but focus more on the assumptions than the numbers.
- Are the growth assumptions realistic? Compare projected growth rates to industry benchmarks and comparable companies.
- What is the path to profitability? Does the model eventually generate positive cash flow, and at what scale?
- How much total capital will the business need to reach profitability or a major liquidity event? Does this align with the fund's ability to follow on?
Use of Proceeds
- How will the company use the funds from this round? Is there a clear allocation between product development, hiring, sales, and operations?
- What milestones will this funding enable? Are the milestones specific and measurable?
- Does the funding plan provide enough runway to reach the next fundraising milestone with reasonable buffer?
Legal and Cap Table Review
Legal diligence at the early stage is relatively straightforward compared to later stages, but there are still critical items to verify.
Corporate Structure
- Is the company properly incorporated? Verify the entity type, jurisdiction, and good standing.
- Is the corporate structure clean? Are there any unusual subsidiary arrangements, holding companies, or international entities?
- Are all founders' roles, equity grants, and vesting schedules documented in written agreements?
- Is there a standard vesting schedule (typically four years with a one-year cliff)?
Cap Table
- Request and review the full cap table. Is it clean and well-organized?
- What is the fully diluted ownership breakdown? Founders, employees, advisors, and previous investors.
- Is there an employee option pool? What size is it, and has it been allocated?
- Are there any unusual cap table features? Warrants, multiple share classes, convertible instruments with unusual terms?
- What will the cap table look like post-investment? Does the founder ownership remain sufficient to keep them motivated through several more rounds?
Intellectual Property
- Has the company properly assigned all IP from founders and employees? Verify that invention assignment agreements are in place.
- Is there any IP that was developed at a previous employer or university that could create ownership disputes?
- Are there any open-source dependencies that could create licensing complications?
- Has the company filed any patents or trademark registrations?
Contracts and Agreements
- Review any significant customer contracts. Are there unusual terms, exclusivity clauses, or liability provisions?
- Review any partnership or vendor agreements. Are there dependencies on specific partners that create risk?
- Are there any pending or threatened legal disputes?
- Review the company's terms of service and privacy policy. Are they appropriate for the product and compliant with relevant regulations?
Customer References
Talking to actual customers (or potential customers, if the product is pre-revenue) is one of the highest-value activities in early-stage due diligence. Founders will tell you their product is amazing. Customers will tell you the truth.
For Companies with Existing Customers
- Ask to speak with three to five customers. Request both the company's best customers and at least one who has had challenges.
- How did the customer discover the product? What problem were they trying to solve?
- What alternatives did they consider? Why did they choose this product?
- How has the product performed relative to expectations? Where does it exceed and where does it fall short?
- Would they recommend the product to peers? Have they already done so?
- How responsive is the company to support requests and feature feedback?
- What would make them stop using the product?
For Pre-Revenue Companies
- Talk to potential customers in the target segment. Do they recognize the problem the company is solving?
- How are they handling the problem today? What do they spend (in time and money) on current solutions?
- Would they pay for the described solution? At what price point?
- What features or capabilities would be most important to them?
Competitive Landscape
Understanding the competitive environment helps you evaluate both the opportunity and the risks. No company operates in a vacuum, and founders who claim they have "no competitors" are either in a market that does not exist or have not done their research.
Direct Competitors
- Who are the direct competitors, and how do they compare on product, pricing, and go-to-market?
- How much funding have competitors raised? Who are their investors?
- What is each competitor's apparent trajectory? Growing fast, plateauing, or declining?
- What is this company's differentiation relative to each major competitor? Is it sustainable?
Indirect Competitors and Substitutes
- What non-obvious alternatives do customers use today? Spreadsheets, manual processes, and internal tools are often the real competition at the early stage.
- Are there adjacent companies that could easily expand into this market?
- Are any large incumbents likely to build or acquire in this space?
Competitive Dynamics
- Is this a winner-take-all market, or can multiple players coexist?
- What are the barriers to entry? How difficult is it for new competitors to enter?
- Is competition primarily on product, price, distribution, or brand?
Red Flags to Watch For
Experience teaches you to recognize patterns that predict trouble. None of these are automatic deal-killers, but each warrants serious attention and honest conversation.
Team Red Flags
- Founders who cannot clearly articulate why they are the right team to solve this problem
- Co-founder relationships that seem strained or poorly defined
- Founders who are dismissive of competitors or customer feedback
- Key team members who are not fully committed (still working other jobs, maintaining side projects)
- Back-channel references that are lukewarm or raise concerns about integrity
Business Red Flags
- A market size story that only works with tops-down math and aggressive assumptions
- Customer concentration risk: one or two customers representing the majority of revenue
- Unusually high churn that the team cannot adequately explain
- A business model that requires massive scale to achieve viable unit economics
- No clear path to repeatable, scalable customer acquisition
Financial Red Flags
- Burn rate that is inconsistent with the stage and progress
- Unexplained gaps in the financial history
- Previous funding rounds with unusual terms or investor disputes
- A funding plan that requires raising again in less than twelve months
- Founders who are vague or evasive about financial details
Legal Red Flags
- Messy or disputed cap table
- Missing founder vesting agreements
- IP that was developed before the company was formed without proper assignment
- Regulatory risks that the team has not adequately addressed
- Pending legal action or unresolved disputes
Putting It All Together
Due diligence is not a checklist to complete mechanically. It is a structured investigation that builds your conviction (or reveals dealbreakers) through a combination of data analysis, reference conversations, and direct interaction with the founding team.
The most important skill in early-stage diligence is knowing where to go deep and where surface-level review is sufficient. A serial founder with three exits needs less team diligence than a first-time founder. A company with $2M ARR needs more financial scrutiny than a pre-revenue startup. A deep tech company needs intensive product and IP review that a simple SaaS tool might not require.
Organize your findings in a structured format that your partnership can review efficiently. For each major area, summarize the key findings, highlight strengths, flag concerns, and note any open questions that need resolution before making a decision.
Tools like Roulette help you manage this process by centralizing deal information, tracking diligence tasks, and keeping your team aligned on where each evaluation stands. When your pitch deck data, meeting notes, customer reference summaries, and team assessments all live in one place, the partnership can review deals more effectively and make better-informed decisions.
The best diligence processes are thorough without being bureaucratic, structured without being rigid, and honest about both the opportunity and the risks. Your goal is not to eliminate uncertainty. That is impossible at the early stage. Your goal is to understand the uncertainty clearly enough to make a high-quality investment decision.