How to Assemble Evidence for Due Diligence with a Knowledge System

What Due Diligence Evidence Assembly Requires

Due diligence is the process of gathering and evaluating evidence before a significant investment or acquisition decision. Whether it's venture capital diligence on a Series A company, private equity diligence on a buyout target, or corporate M&A diligence on an acquisition candidate, the process involves:

• Gathering a large volume of documents and information from multiple sources
• Organizing findings by domain (financial, legal, technical, commercial, people)
• Tracking what's been received, what's outstanding, and what red flags have been identified
• Synthesizing findings into a diligence report that supports the investment decision
• Maintaining a clear record of what was examined and what conclusions were drawn

Without a system, due diligence evidence accumulates in a shared data room folder hierarchy, email attachments, call notes scattered across platforms, and a diligence checklist in a spreadsheet that becomes the source of truth for status tracking. This works, but it makes synthesis difficult — the analyst who needs to write the "commercial" section of the diligence report has to re-read everything rather than working from organized, annotated findings.

A knowledge system complements the data room by providing the analytical layer: capturing key findings with annotations, tracking open questions, and organizing the evidence that supports specific conclusions in the report.

---

The Due Diligence Domains

Standard due diligence covers six domains. The depth in each depends on deal type, but all are present in most significant diligence processes:

1. Financial: Revenue quality, margins, cost structure, cash flow, accounting practices, tax position, financial projections and their assumptions.

2. Legal: Corporate structure, contracts, IP ownership, regulatory compliance, litigation history and exposure, employment matters.

3. Commercial/Market: Market size and dynamics, competitive position, customer concentration, NRR, churn, customer satisfaction, sales pipeline quality.

4. Technical (for tech companies): Architecture, technical debt, security posture, infrastructure costs, IP quality, development capacity.

5. People and Organization: Leadership team quality, key person dependency, org structure, compensation, culture, employee satisfaction, turnover.

6. Operational: Operational processes, vendor relationships, supply chain risks, facilities, key operational dependencies.

The knowledge system organizes evidence and findings by these domains.

---

Setting Up the Knowledge System

Collections structure

Create a primary Collection: "Due Diligence: [Target Company] — [Deal Name/Date]"

Sub-Collections by domain:

• "DD: Financial" — financial documents, model analysis notes, accounting findings
• "DD: Legal" — legal structure, contract reviews, litigation, IP
• "DD: Commercial" — market research, customer analysis, competitive positioning
• "DD: Technical" — technical architecture, security, code quality
• "DD: People" — leadership profiles, org analysis, key person risk
• "DD: Operational" — process documents, vendor relationships, operational risks

Plus functional Collections:

• "DD: Management Presentations" — materials from management meetings and presentations
• "DD: Data Room Documents" — captures of key documents from the data room
• "DD: Open Questions" — questions not yet answered
• "DD: Red Flags" — findings requiring closer examination or deal structuring response
• "DD: Comparable Companies" — benchmarks and comparables

Tags for due diligence

By domain:

• financial, legal, commercial, technical, people, operational

By finding type:

• confirmed-positive — fact that supports the investment thesis
• confirmed-risk — risk that needs to be addressed or priced
• open-question — fact not yet confirmed
• red-flag — potential deal-breaker requiring resolution
• needs-verification — claim made by management that requires independent verification

By source:

• data-room-doc — from the formal data room
• management-interview — from conversation with management
• customer-interview — from reference calls
• independent-research — from your own external research
• expert-interview — from technical or industry expert calls

---

Phase 1: Pre-Diligence Research

Before formally entering the data room, conduct external research on the target company. This primes you to ask better questions and helps you identify discrepancies between the company's narrative and external evidence.

External research before the data room

Company public information:

• Their website and product (use it if accessible)
• LinkedIn for headcount and team composition
• LinkedIn for leadership team backgrounds and tenure
• Press coverage and announcements
• Job postings (reveal investment areas, culture, challenges)
• App reviews, G2/Capterra reviews (for software companies)

Market and competitive context:

• The market they claim to operate in — is it real, and is it the right size?
• Who are their competitors, and how do they actually compare?
• Industry reports on their category

Customer reference pre-research:

• Who are their named customers (from website, case studies)?
• Can you speak with any before formal diligence begins?
• What do their reviews say?

Financial signals (public or inferrable):

• If any public funding, what does the cap table look like?
• What does headcount growth tell you about burn and stage?
• What do comparable companies' financials look like?

Capture pre-diligence research in the relevant domain Collections with annotations noting what's confirmed vs. what remains to be verified.

Building the diligence question list

From your pre-diligence research, build a comprehensive list of questions for each domain before entering the data room:

Domain: [Financial / Legal / Commercial / Technical / People / Operational]
Question: [specific question]
Source of this question: [what prompted it — gap in public information / discrepancy / standard check]
Verification method: [data room document / management interview / customer reference / expert call]
Priority: [critical / important / standard]
Status: [outstanding / received / resolved]
Answer: [what was provided]
Verified: [yes — by / no — pending]

Maintain this as a living document throughout the diligence period. The status field tracks progress; the answer and verified fields record what you found and whether you've independently confirmed it.

---

Phase 2: Data Room Navigation

How to work through a data room

Data rooms are organized by the target company or seller. The quality of the organization varies enormously. Your job is to navigate it efficiently, identifying key documents, capturing critical findings, and noting what's missing.

Day 1-3 in the data room: Focus on the highest-priority documents:

• Most recent 2-3 years of audited financials
• Current cap table
• Key customer contracts (2-5 largest)
• Any existing legal disputes or outstanding claims
• Key employee contracts and equity arrangements
• Technical architecture documentation

Standard data room navigation:

• Download only what you need, not everything
• Capture key pages or sections as clips in WebSnips with annotations rather than downloading and reading entire documents repeatedly
• Note what you expected to find but didn't (absence of documents is itself information)

Annotation protocol for data room documents

For each significant document capture:

Document: [Title and description]
Domain: [Financial / Legal / Commercial / Technical / People / Operational]
Source: [data room folder path]
Date of document: [when created/dated]

Key finding: [the most important thing this document shows]
Significance: [why this matters for the investment decision]
Questions raised: [what this makes you want to investigate further]
Comparison to management claims: [does this confirm, modify, or contradict what management said?]
Red flag level: [none / watch / significant / potential deal issue]
Action required: [follow-up question / expert review / model update / no action]

The "comparison to management claims" field is critical. Due diligence is not just gathering documents — it's cross-checking what management has told you against what the documents actually show. Discrepancies between management representation and documentary evidence are significant.

---

Phase 3: Reference and Expert Interviews

Customer reference calls

Reference calls with customers are among the most valuable and underutilized sources in commercial diligence. Don't let the company select all your references — ask for a broader list and select your own calls.

Reference call annotation:

Reference: [Customer name, title — or anonymized]
Reference arranged by: [target company / independent]
Customer since: [date]
Contract value: [range, or decline to note]
Product used: [which features / how widely deployed]

NPS / satisfaction: [their rating and reasoning]
Specific strengths they cited: 
Specific limitations or complaints:
Whether they'd renew or expand: [yes/hesitant/no, with reason]
Whether they'd recommend to peers: [yes/no, with reason]
Red flags in the conversation: [anything that contradicted company narrative]
What they said that confirmed the investment thesis:
What they said that complicated the thesis:

Track reference call sentiment across all calls and compare to the company's NRR and NPS data. A company claiming 110% NRR with reference calls consistently citing concerns about support quality is a signal worth investigating.

Expert calls

Expert interviews with former employees, industry veterans, or technical specialists provide context that documents can't provide.

Expert interview annotation:

Expert: [role, background — or anonymized]
Area of expertise: [technical / market / competitive / people]
Connection to target: [former employee / industry expert / no direct connection]

Key insight provided:
Confirmed or contradicted: [what this confirmed or contradicted in the company's narrative]
Technical or market red flags raised:
Recommended further investigation:
Confidence in this expert's assessment: [high / medium / calibrate further]

---

Phase 4: Finding Synthesis and Report Preparation

The red flags tracker

Maintain a dedicated "Red Flags" collection throughout diligence. For each:

Red flag: [description]
Domain: [Financial / Legal / Commercial / Technical / People / Operational]
Source: [document / interview / analysis]
Severity: [potential deal-breaker / requires resolution / should be priced / watch item]
Current status: [under investigation / resolved / outstanding]
Resolution: [if resolved — how was this addressed?]
Deal implication: [if unresolved — impact on pricing, structure, or decision]

The red flags tracker becomes the basis for deal structuring discussions: which risks need to be addressed in representations and warranties? Which require price adjustments? Which are acceptable given the upside?

The synthesis session

After the core diligence period, run a synthesis session for each domain:

1. Review all captures and annotations in the domain Collection
2. Identify the 3-5 most significant findings (positive and negative)
3. Assess: what does the totality of evidence say about this dimension of the investment?
4. Draft the domain section of the diligence report

Domain summary structure:

DOMAIN: [Financial / Legal / Commercial / Technical / People / Operational]
Overall assessment: [Strong / Adequate / Concerns / Material Issues]

KEY FINDINGS:
  1. [Finding] — [evidence source] — [significance]
  2.
  3.

RISKS AND MITIGANTS:
  1. [Risk] — [how it's mitigated or what action it requires]
  2.

OUTSTANDING QUESTIONS:
  1. [Question not yet resolved]
  2.

DEAL IMPLICATIONS:
  [What this domain's findings mean for pricing, structure, or decision]

Using Creator Studio for report drafting

With the domain-organized captures and annotations in WebSnips, Creator Studio can accelerate the diligence report drafting:

"Based on these 12 captures from the Commercial domain of this due diligence, draft a commercial diligence summary covering market position, customer dynamics, and competitive risk."

Edit the output substantially to ensure accuracy — the draft is a starting point, not a final report. Every claim in the diligence report needs to be traceable to a specific evidence source.

---

Worked Example: Software Company Series B Due Diligence

The scenario: A venture capital analyst is leading commercial and market diligence on a $15M Series B investment in a B2B SaaS company with $4.2M ARR.

Pre-diligence research (1 week before data room access):

External research captured:

• 6 customer reviews on G2 — annotated: "4.2/5 overall; recurring complaint about API documentation quality"
• 3 competitor website captures — annotated with positioning comparison
• LinkedIn headcount analysis: 47 employees (vs. 52 claimed) — raised as verification question
• 2 customers identified from their case study page for independent reference calls

Data room navigation (weeks 1-2):

Commercial domain captures:

• Customer contract for largest customer (23% of ARR) — annotated: "18-month remaining term; renewal clause requires 60-day notice; no auto-renew — significant concentration risk with non-auto renewing contract"
• NRR calculation model — annotated: "Model excludes partial-year expansions in the NRR numerator; actual NRR is 107% not 112% as stated in management materials"
• Pipeline report — annotated: "Enterprise pipeline at $1.2M, but 65% is in 'stage 3' for more than 90 days; average enterprise sales cycle should be 90-120 days — some stale pipe"

Open questions raised: 4 questions sent to management; 3 answered satisfactorily, 1 outstanding (customer concentration mitigation plan).

Reference calls (week 3):

8 reference calls completed (4 company-arranged, 4 independent).

Key finding from reference synthesis: 6 of 8 references mentioned the API documentation issue (consistent with G2 reviews). 3 of 8 mentioned price as a concern at renewal. 2 of 8 mentioned that they'd considered switching but stayed due to migration cost.

Red flags identified (2):

1. Customer concentration: Top customer = 23% ARR with non-auto-renewing contract expiring in 18 months — priced into deal terms via milestone-based tranche
2. NRR calculation method: 107% actual vs. 112% stated — management agreed to restate; note added to reps and warranties

Commercial section of diligence report: Drafted from Creator Studio synthesis of domain Collection captures in 45 minutes; edited to final form in 90 minutes.

---

Key Takeaways

1. Pre-diligence external research primes better data room navigation: knowing what questions to ask before entering the data room makes the 2-week diligence window much more productive.
2. Annotate all data room captures with "comparison to management claims": discrepancies between documents and management representations are the most important findings to surface.
3. Independent customer references reveal what arranged references don't: independent calls (not arranged by the target) produce more candid assessments; the consistency between arranged and independent references is itself informative.
4. Maintain a dedicated red flag tracker throughout diligence: red flags identified in weeks 1 and 3 need to be tracked and resolved before a decision; a running log prevents any from falling through the cracks.
5. Domain-organized captures make report drafting significantly faster: when evidence is organized by domain with annotations on significance, the report draft draws from organized material rather than from re-reading everything.

---

Conclusion

Due diligence is evidence-based decision support for high-stakes investment decisions. The quality of the decision correlates directly with the quality of the evidence-gathering and synthesis process — how thoroughly the evidence was gathered, how rigorously it was cross-checked against management claims, and how clearly the findings were synthesized into actionable conclusions. A knowledge system that organizes diligence evidence by domain, maintains a red flags tracker, and supports synthesis from annotated captures produces a diligence process that's more thorough and a report that's more defensible. The investment in an organized, annotated evidence library pays off not just in the current deal but in every future process where past diligence findings provide benchmarks and context.

Start your due diligence knowledge system in WebSnips — create domain-organized Collections, capture data room findings with annotations comparing them to management claims, and build the structured evidence library that supports better investment decisions.