VC Due Diligence: An Investor Evidence Checklist

Evaluate startup claims with an investor-focused VC due diligence checklist covering ownership, customers, runway, technology and decision records.

A VC due diligence checklist should help an investor decide what to believe, what remains uncertain and what would change the investment decision. Collecting a large folder of startup documents is only the starting point.

This guide focuses on the investor's evidence review, rather than teaching founders how to set up a fundraising room. Use it to organize requests, test management claims and write a decision memo that distinguishes verified facts from assumptions. Scale the depth to the stage, business model, proposed investment and expertise available.

Write the investment questions first

Start with a one-page thesis. Describe the customer problem, why the product could win, what growth depends on and which risks would make the opportunity unsuitable for your fund. Keep questions concrete enough that evidence could contradict your view.

For an early software company, a useful question might be whether customers keep using the product after the initial pilot. For a hardware business, manufacturing yield or supplier dependence may matter more. Do not ask every company for the same SaaS metric spreadsheet simply because it is available in a template.

Define your review period and what the investment would fund. Historical performance, current operating capacity and the future plan should be separate. A company can have an encouraging product and still require more cash than the proposed round provides.

Assign owners for commercial, financial, technical and legal questions. An associate can coordinate the request list, but unfamiliar legal rights or specialist technical claims need appropriate review. Time pressure is a reason to prioritize questions, not to silently mark unreviewed issues as cleared.

Use an evidence checklist with a test for every claim

Request a defined period, document type and explanation of exclusions. A question such as send metrics invites a polished presentation. A question such as explain customer additions, cancellations and expansion during these twelve months produces a testable request.

This is an editorial starting checklist, not a statutory standard or an exhaustive diligence programme. Add sector-specific questions and drop irrelevant requests with an explicit reason. Preserve the boundaries of the review so the final memo does not imply more work than was performed.

Reconcile ownership before discussing headline valuation

Ask counsel to compare the cap table with executed documents and the relevant company records. Include outstanding options, promised grants, convertible instruments and side arrangements where applicable. A spreadsheet can accurately describe someone's understanding while still omitting an unresolved obligation.

Explain how the proposed financing changes ownership under documented assumptions. Do not treat every convertible instrument as interchangeable. Conversion mechanics and investor rights can vary, and the relevant documents determine the result.

For U.S. venture financings, NVCA publishes model legal documents. These are useful reference materials for financing structure, not evidence that a particular startup's documents are complete or valid. Have qualified counsel assess the actual executed instruments. NVCA Model Legal Documents

Separate a correctable documentation gap from a disagreement about ownership. Record who will resolve it, what evidence will close the issue and whether resolution is required before investment. A verbal promise that the lawyer will handle it should remain an open item until the agreed evidence is received.

Test customer traction with consistent definitions

Write down what the company means by customer, active user, revenue and recurring revenue. Count trial accounts separately from paying customers. Separate contracted commitments from cash received and distinguish recurring fees from implementation or other one-time work.

Ask for a reconciliation from summary slides to underlying systems for a suitable sample. This is not an instruction to download every customer record. Start with aggregated data, investigate material discrepancies and handle identifiable information through an approved process.

Review cohorts over comparable periods. If older customers leave but new customers arrive quickly, total growth can hide retention weakness. If one enterprise account drives expansion, an attractive aggregate retention figure may tell you little about the rest of the customer base.

Customer references should test actual use, buying process and replacement options. Ask management how references were selected, then seek a balanced sample where consent and process allow. A delighted customer is useful evidence, but it is not proof that every account shares the same experience.

Check runway against the operating plan

Use cash available for operations, not a presentation's headline balance without context. Ask about restrictions, overdue liabilities, committed payments and financing assumptions. Make dates explicit so a rapidly changing balance is not treated as current indefinitely.

Calculate a simplified cash runway only when its assumptions are clear. For example, cash divided by expected monthly net cash outflow is a planning estimate. It becomes misleading if burn changes materially, seasonal receipts dominate or large one-off payments are ignored.

Review the proposed hiring and acquisition plan alongside the cash forecast. If the plan assumes hiring immediately, selling faster and raising another round before reaching a milestone, record each dependency separately. Do not call all three assumptions a single growth strategy.

Request a downside case. Ask management which spending can actually be reduced, how quickly and with what consequence. Cutting product development can extend runway while delaying the very milestone investors expect. The trade-off belongs in the investment decision rather than disappearing inside a lower expense line.

Review product and technology without overclaiming assurance

Observe the product completing a real task using approved demonstration data. Ask what was manual, simulated or outside the released product. A compelling interface can coexist with unfinished operational work, which may be acceptable if it is disclosed and appropriately valued.

For material technical risks, appoint a qualified reviewer and agree scope. Their output should state the systems examined, sample depth, limitations and unresolved questions. A short architecture call is not a security audit, code ownership opinion or scalability certification.

Map key dependencies: external APIs, cloud services, models, licensed data, contractors and specialist employees. Ask what happens if a provider changes terms or a key engineer leaves. The aim is not to eliminate every dependency but to understand those that affect cost, service continuity or defensibility.

Keep sensitive source code and security details in an appropriate restricted process. Investors do not automatically need broad access to every technical file. The request should follow the risk being examined and the reviewer's actual assignment.

Worked example: growth that needs a closer look

This example is fictional. An investor reviews a startup reporting $60,000 in monthly recurring revenue. Its summary includes $10,000 of one-time onboarding work, so the investor records $50,000 of recurring revenue under the agreed definition rather than treating the full amount as recurring.

The company has $900,000 of unrestricted operating cash and expects $75,000 of monthly net outflow before the proposed hiring plan. A simple steady-state estimate is twelve months. Planned hires add $25,000 of monthly outflow, reducing that simplified estimate to nine months. Both calculations exclude future growth, one-off payments and any new financing; they are scenarios, not forecasts of actual survival.

Customer review finds that one account supplies $15,000 of the $50,000 recurring total, or 30%. That concentration is not an automatic rejection. The investor requests the relevant renewal context and examines whether the financing plan can withstand losing it.

The resulting memo does not say traction verified and move on. It records the revised revenue definition, the cash sensitivity and the concentration question, then identifies evidence still needed before the committee can decide.

Turn issues into a decision record

A useful issue log shows the claim, the evidence, the remaining uncertainty and the consequence. Traffic-light colours alone compress too much information. A green label can conceal a weak sample or a review completed by someone without the right expertise.

State whether an issue changes valuation, terms, timing or suitability. Some uncertainty remains in every investment. The committee needs to know which uncertainty it is accepting, not simply that the room contains enough documents.

Handle the review process responsibly

Keep investor analysis separate from the company's shared materials. Limit access to the investment team and appointed advisers who need it. Disclose and manage relevant conflicts, including competitive portfolio exposure, through the fund's established process.

Track request changes and evidence dates. When a company updates a metric, keep the explanation of the change. Do not cite an earlier screenshot while using a later spreadsheet without reconciling the difference.

Decide what records the fund retains after declining or completing the deal. Respect agreed confidentiality and handling obligations. Closing a data-room invitation does not itself remove copies held in the investor's systems.

Know what the checklist cannot settle

A complete request list cannot guarantee founder honesty, future market demand or investment returns. Independent checks can reduce uncertainty, but every method has scope and limits. Report those limits rather than dressing them up as a comprehensive audit.

Avoid rewarding confident answers over supported answers. A founder who identifies an unresolved issue and provides a workable resolution may be more informative than one who says everything is already handled. Your job is to assess the evidence and economics, not the neatness of the folder structure.

Frequently asked questions

How much diligence does a seed-stage startup need?+

Match the review to the stage, investment size, sector and thesis. Focus first on ownership, founder and customer evidence, cash needs and the key technical or regulatory dependencies. Explain exclusions instead of pretending a limited review covers every risk.

Should investors ask for every customer contract immediately?+

Not automatically. Start with the question being tested and request a proportionate sample or aggregated schedule. Escalate access when the evidence requires it and applicable handling requirements permit it.

Does a clean data room mean a startup is investment-ready?+

No. Organization improves review, but it does not establish accuracy or commercial viability. Reconcile important claims, investigate discrepancies and preserve unresolved questions in the committee record.

Before you proceed

Use the checklist to connect investment claims to evidence. A clear memo about what was tested and what remains uncertain is more valuable than a large collection of unexplained files.

Related articles

• Protect Your IP During Fundraising

• Commercial Due Diligence: Test the Revenue Story

• How to Set Up a VDR: Launch Checklist

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. The operational templates and worked examples are editorial recommendations, not claims of completed transactions or product testing.

• NVCA Model Legal Documents

VDR Directory is published by the team behind SendNow. This ownership is relevant when considering product recommendations. Stock photos illustrate general workflows. Legal, tax, regulatory and security decisions depend on the transaction and applicable requirements; involve the responsible specialist. No platform can guarantee confidentiality, transaction success or search rankings.