Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Compare material contracts for a seed equity financing by mapping the proposed purchase agreement’s disclosure categories to the company’s contracts, then recording comparable terms with clause-level evidence. Review complete amendment chains, distinguish operating risks from financing-triggered restrictions, and assign unresolved questions to named owners. The resulting diligence table should identify contracts requiring disclosure, investigation, consent analysis, or remediation—not merely list data-room documents. Company counsel should verify findings before using them in investor responses or disclosure schedules.
When to use this workflow
Use this workflow when a seed investor requests material contracts, a draft stock purchase agreement introduces contract representations, or company counsel must reconcile business-team responses with the data room. It serves company-side lawyers, in-house teams, and finance or operations personnel supplying evidence.
The scope covers commercial agreements and related instruments affecting disclosure accuracy, operating flexibility, or the proposed financing. Include prior financing documents where they create relevant consent or information-sharing restrictions; capitalization reconciliation remains separate.
This guide assumes a US private-company financing, using a Delaware corporation as the corporate baseline. It provides workflow recommendations, not requirements for every financing. Contract conclusions depend on operative language, governing law, and transaction facts. Test whether a share issuance meets a contractual assignment or change-of-control definition rather than assuming either result.
What you need
Collect these inputs before comparing terms:
- Deal documents: current purchase agreement, proposed disclosure schedules, term sheet, and financing facts needed to test contractual triggers.
- Contract families: signed master agreements, orders, statements of work, amendments, side letters, incorporated terms, and renewal or termination notices.
- Business records: committed expenditure, customer revenue, supplier dependencies, affiliate relationships, and business-owner explanations of performance.
- Existing rights: relevant investor agreements, debt instruments, and restrictions affecting financing disclosures.
- Document controls: persistent IDs, execution status, amendment relationships, and stable room locations.
Use the proposed representations to determine inclusion criteria. Defeye’s filed seed purchase agreement, for example, covers obligations or payments to the company exceeding $100,000, IP licenses, specified restrictions on product rights, and IP-infringement indemnities. It aggregates arrangements involving the same person, including persons the company has reason to believe are affiliated. These are example-specific provisions, not universal materiality rules. Defeye § 2.10
Also include explained business-critical exceptions. A modest license supporting the core product may warrant closer review than a larger, replaceable service contract.
Use the template
The companion template is Seed Equity Financing Rounds — Material contracts comparison. Copy this table into your working document or spreadsheet. Use one row per contract family and comparison issue; repeat the contract ID when provisions require separate decisions.
| Contract / ID | Version / evidence | Scope basis | Term compared | Finding / exception | Financing effect | Open question | Action / owner | Status / proof |
|---|---|---|---|---|---|---|---|---|
Version / evidence identifies the operative document, clause or page, and relevant amendment. A room link alone does not identify the supporting language. Scope basis records the draft representation or business reason for inclusion.
Use consistent categories in Term compared: payment, renewal, termination, assignment/change of control, exclusivity, IP, indemnity, liability, and consent. Preserve definitions, thresholds, exceptions, and dependencies in Finding / exception.
In Financing effect, distinguish disclosure candidates, possible consent dependencies, and operational concerns. Add priority and its rationale here. Action / owner should include the responsible person and target milestone. Status / proof records closure evidence, such as a reviewed amendment, signed consent, or approved schedule entry. Keep unknown, not applicable, and no relevant provision located distinct.
Step by step
1. Establish comparison criteria from the financing draft
Read the material-contract representations and schedule instructions together. Identify monetary and nonmonetary categories, aggregation language, exclusions, relevant dates, and measurement periods. Ask business owners how their arrangements map to those categories.
Do not substitute annual contract value for total obligations unless the drafting supports that measure. Distinguish payments to the company from expenditure obligations. Where language is ambiguous, record the interpretation requiring a decision.
Record: the draft version and representation reference in Scope basis. Put unresolved inclusion questions in Open question; identify discretionary business-critical reviews separately.
2. Assemble the operative contract families
Connect each master agreement to its orders, amendments, incorporated terms, and notices. Confirm the contracting entity, execution status, and order-of-precedence provisions. If an amendment references an unavailable schedule, retain the gap rather than assuming it is immaterial.
Ask finance and business owners about arrangements absent from the room. Recurring invoices, procurement records, and sales records can identify missing orders or extensions, but do not themselves establish every contractual term.
Record: document IDs, execution evidence, controlling amendments, and missing components in Version / evidence and Open question. A complete PDF is not necessarily a complete contract family.
3. Normalize economics and operating duration
Separate committed payments from usage estimates and contingent charges. Specify currency, period, minimum purchases, prepaid amounts, and termination charges. Explain aggregation by counterparty or affiliate where the review criteria require it; avoid counting the same obligation in both an order and its master agreement.
For duration, record the effective date, current term, renewal mechanism, notice window, and evidence of notices. Do not calculate a definitive exit date from uncertain dates or incomplete amendments.
Record: comparable economics and duration rows with assumptions and clause references. Assign uncertain dates for confirmation rather than presenting estimates as settled obligations.
4. Test restrictions against the actual seed financing
Extract assignment, change-of-control, equity-issuance, consent, and notice provisions separately. Read definitions and exceptions before assessing a trigger. Compare the wording with the issuance, resulting voting power, investor arrangements, and any accompanying restructuring.
Distinguish a notice obligation from a consent requirement. Identify the contractual recipient, required timing, and available exceptions where relevant. Also capture termination rights affecting continuity even without a financing trigger.
Record: the trigger, known transaction facts, missing facts, and provisional assessment. Use “trigger unresolved” rather than “consent required” where the language or ownership analysis remains incomplete.
5. Compare IP and risk allocation in commercial context
Distinguish core-platform ownership from customer deliverables, feedback, commissioned development, and third-party licenses. Describe exclusivity by product, territory, customer category, duration, and exceptions; “exclusive: yes” is insufficient.
Read indemnities alongside liability caps, exclusions, and any separate limits. Identify whether a broad customer license could affect the company’s ability to reuse technology, even where the ownership clause appears favorable. Capture defaults or disputes reported by business owners as separate factual questions.
Record: interacting clauses, business dependency, uncertainty, and proposed response. Separate observed wording from conclusions about enforceability or commercial acceptability.
6. Translate findings into disclosure and controlled responses
Map disclosure candidates to the current schedule sections. Defeye’s filed agreement requires corresponding schedule sections and limits cross-qualification to applicability readily apparent from the disclosure. That wording illustrates why room upload should not be assumed to satisfy negotiated disclosure mechanics. Defeye Section 2 introduction
Before sharing, check the commercial contract’s own confidentiality exceptions and the prospective recipient’s arrangements. An investor NDA should not be treated as automatically overriding third-party restrictions. Consider permitted redactions, summaries, or consent requests.
Separately, Gatsby’s filed investor-rights form conditions access to specified confidential information and permits withholding contractual information rights from specified competitors and associated investors. Those provisions concern rights under that agreement; they do not authorize prospective-investor diligence disclosure or establish privilege. Gatsby § 1.1(b)
Record: schedule destination, proposed sharing approach, restrictions requiring resolution, and reviewer. Keep internal legal assessments separate from investor-facing factual extracts where appropriate.
7. Resolve exceptions and approve the comparison
Review consequential rows with the business owner and financing counsel. Determine whether each requires factual correction, further documents, consent analysis, commercial negotiation, or schedule drafting. Disclosure and consent remain separate: completing one does not close the other.
Recheck affected rows when financing terms or source documents change. Preserve the version supporting each assessment so revised conclusions remain traceable.
Record: approved action, owner, target milestone, and closure evidence. Keep unresolved matters open with an assigned decision-maker; silence is not approval.
Worked example
Entirely fictional scenario: Alder Circuit, Inc. is preparing a $3 million seed preferred-stock financing. Its fictional purchase agreement requests disclosure of customer payments or company obligations exceeding $75,000, aggregating arrangements with the same counterparty, plus specified IP licenses and exclusivity arrangements. These invented terms are not market benchmarks.
The room contains a customer master agreement, two orders, a core software license, and a cloud-services agreement. Sales reports discussions about broader customer exclusivity, but no amendment has been produced. The final post-financing voting-power model is unavailable.
| Contract / ID | Version / evidence | Scope basis | Term compared | Finding / exception | Financing effect | Open question | Action / owner | Status / proof |
|---|---|---|---|---|---|---|---|---|
| Juniper Field customer / MC-01 | Signed MSA § 3; orders O1–O2 § 2 | Draft § 2.10(a): aggregate payments; § 2.10(c): exclusivity | Payments; exclusivity | Orders require $48,000 each in customer payments; exclusivity covers one listed application | Disclosure candidate; possible sales constraint | Was broader exclusivity agreed, and in what form? | Sales lead supplies correspondence before schedule approval; counsel evaluates | Open; no expansion document supplied |
| Cobalt Reed license / MC-02 | Signed license §§ 4, 11 | Draft § 2.10(b): IP license | Change of control | Prior-consent clause addresses acquisition of more than 50% of voting power | High priority because core product depends on license; trigger unresolved | Final voting power and application of full definition? | Financing counsel tests final model before consent decision | Open; no consent conclusion |
| Lantern Stack cloud / MC-03 | Signed services agreement §§ 6, 9, 12 | Business-critical infrastructure | Termination; liability | Provider has 30-day convenience termination; confidentiality claims excluded from stated cap | Continuity and exposure concern; no issuance trigger located | Replacement environment available? Any separate liability limit? | Operations assesses continuity; counsel checks full liability provisions before issue approval | Open; signed text located, analysis incomplete |
The customer orders total $96,000 and meet the fictional draft’s aggregation test, although neither does individually. Existing narrow exclusivity independently requires review; the reported expansion remains an evidence gap, not an established obligation.
The license receives priority because of product dependency, but the missing voting-power model prevents a supported consent conclusion. The cloud contract remains in scope for operating reasons. Neither its termination right nor its cap exception should be mislabeled a financing closing condition.
Common mistakes
- Applying a generic materiality cutoff. Use the current draft’s categories, aggregation rules, and measurement periods, supplemented by explained business-critical inclusions.
- Reviewing only master agreements. Collect orders and amendments, and identify which document controls each term.
- Reducing restrictions to yes/no fields. Preserve triggers, exceptions, and missing facts before assigning a financing consequence.
- Treating every finding as investor-facing. Separate verified disclosure facts from internal analysis and information requiring release approval.
- Closing issues when files arrive. Verify that the document answers the question and record the evidence supporting closure.
Final quality check
- Every contract has a representation-based or business-based scope reason.
- Findings cite operative clauses and relevant amendments; execution gaps remain visible.
- Economics state currency, measurement period, aggregation basis, and avoid double counting.
- Renewal and termination entries preserve uncertain dates and missing notices.
- Trigger assessments match contractual definitions and verified transaction facts.
- Schedule mapping and sharing restrictions have been reviewed separately.
- Open issues have owners and decision milestones; closed issues identify supporting evidence.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include bulk document classification to organize materials and prioritize human review; tabular review supports work across multiple documents. For follow-up, contract review findings can quote clauses, locate text, rank severity, and identify missing language. Counsel retains responsibility for version checks, trigger analysis, and disclosure decisions. Book a demo to discuss this comparison workflow.
Frequently asked questions
Should every contract appear in the table?
Keep a broader document index, but focus comparison rows on negotiated disclosure categories and explained business dependencies. Document exclusions sufficiently to make the review scope understandable.
What if the material-contract representation changes?
Identify the draft version supporting each inclusion decision. Recheck affected categories, thresholds, exclusions, and aggregation rules rather than assuming the original population remains complete.
Can the table become the disclosure schedule?
It can supply verified facts, but is not automatically the schedule. Adapt entries to negotiated disclosure mechanics, remove internal assessments, and verify section mapping and cross-references.
How should unsigned amendments be handled?
Label execution status and request signature evidence, correspondence, and performance context. Do not automatically treat the amendment as operative or irrelevant; assign counsel to assess its significance under applicable law and facts.
Sources
These SEC-filed exhibits illustrate contractual wording, not market standards or proof of operative rights. Both contain incomplete date fields; use executed company documents for matter-specific conclusions.
- Defeye, Inc., Series Seed Preferred Stock Purchase Agreement, Section 2 introduction and § 2.10
- Gatsby Digital, Inc., Amended and Restated Investor Rights Agreement, § 1.1(b)
This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.
