SAFE Financing Transactions

How to compare material contracts in a diligence table for SAFE Financing Transactions

Compare material contracts for a company-side SAFE financing using a source-linked diligence table, stage-specific consent checks, and a worked example.

October 17, 2026  ·  10 min read
Book a Demo →

Compare material contracts for a SAFE financing by testing each operative agreement against three separate events: SAFE issuance, later conversion, and a potential exit. Record the controlling language, related documents, company exposure, unresolved questions, and required action in one source-linked table. The deliverable is a company-side comparison identifying restrictions requiring attention now, obligations reserved for later events, and evidence gaps preventing a reliable conclusion. It supports financing decisions without treating every diligence concern as a closing condition.

When to use this workflow

Use this workflow when company counsel or an in-house team needs to determine whether existing agreements constrain a proposed SAFE financing. Triggers include an investor diligence request, a lender consent question, a newly discovered side letter, or inconsistent restrictions across commercial contracts.

Include outstanding SAFEs, notes, investor agreements, credit documents, important customer and supplier contracts, and IP agreements. Assess materiality by transaction exposure and business dependence: an essential license may warrant review regardless of its contract value.

This is a general US workflow, with Delaware corporate authorization addressed where relevant. Other formation jurisdictions, negotiated governing law, and state securities requirements need separate analysis. Conclusions depend on operative language and transaction facts. The comparison does not replace corporate authorization, securities-exemption analysis, or a complete capitalization model.

What you need

Obtain the proposed SAFE, its form version, proposed side letters, financing amount, investor identities, and expected signing and acceptance sequence. Identify any associated governance rights, security, or simultaneous transactions rather than testing an abstract “SAFE round.”

Collect these supporting inputs:

  • Financing documents: executed SAFEs, notes, investor-rights agreements, credit facilities, amendments, waivers, and consents.
  • Corporate records: current charter, relevant approvals, capitalization records, and outstanding equity commitments.
  • Commercial and IP documents: material customer and supplier agreements, exclusive arrangements, licenses, assignments, and incorporated schedules.
  • Status evidence: signature pages, renewal records, termination notices, amendment chains, and custodian confirmation of document gaps.

Maintain a supporting index with stable document IDs, version, execution status, custodian, and related instruments. Preserve superseded documents without presenting them as operative. Distinguish an unavailable document from a document the company confirms was never created.

Use the template

Use the companion template SAFE Financing Transactions — Material contracts comparison. You can copy this table into your working document or spreadsheet. Create one row per material issue so different triggers and remedies remain visible.

Row / document IDs Contract / status Clause / evidence Trigger / beneficiary Company effect Uncertainty / priority Action / owner / target Resolution evidence

Link the base agreement and relevant amendments through document IDs. In the evidence column, provide section and page references plus a short quotation or faithful paraphrase. Preserve controlling defined terms; a section number alone may not explain the result.

The trigger field distinguishes issuance, conversion, exit, and continuing obligations, while identifying whose rights are implicated. Company effect states the practical consequence. Keep uncertainty separate from priority: incomplete evidence can justify urgent review without establishing a breach.

Assign an accountable owner and a transaction-linked target, such as “before company acceptance,” unless the source requires an earlier action. Resolution evidence should identify a consent, verified analysis, or handoff record—not merely say “done.”

Step by step

1. Fix the transaction assumptions and comparison perimeter

Prepare an assumptions sheet identifying the proposed SAFE package, investor identities, side-letter rights, and related transactions. Separate the contractual issuance now from any future share issuance under the instrument.

Select agreements by both restriction relevance and business importance. Include financing permissions, equity rights, essential IP, exclusivity, and relationships whose termination would materially affect operations. Record exclusions and reasons in the index.

Template output: identify each included contract, its operative status, and the event being tested. Flag assumptions requiring confirmation, including whether any concurrent transaction changes control or grants additional rights.

2. Establish the operative document chain

Read amendments, schedules, waivers, and consents alongside the base agreement. Determine whether a consent covers only an earlier financing and whether a later instrument changes the relevant definition or exception.

An unsigned draft or business summary may identify a question but does not establish executed terms. Request omitted definitions and cross-references before concluding that a restriction applies or does not apply. Record the review boundary when only excerpts are available.

Template output: link the document chain, cite the controlling text, and label missing evidence. Assign the company custodian responsible for supplying it, rather than leaving the request with an unnamed “business team.”

3. Extract comparable restrictions without flattening their meaning

Compare financing restrictions, issuance consents, change-of-control definitions, assignment provisions, termination rights, exclusivity, and IP ownership. Record the beneficiary, exceptions, thresholds, notice requirements, and consent procedure.

Avoid reducing every provision to “consent required.” A securities-issuance restriction, indebtedness covenant, and control-transfer provision pose different questions. Test the proposed SAFE against each agreement’s definitions rather than assuming that its financing label answers them.

For existing investor instruments, check whether issuing the proposed SAFE creates a present notice, consent, or most-favored-nation issue; do not restrict review to conversion rights.

Template output: state the trigger, relevant exception, beneficiary, and exposure. Add linked rows when one contract presents distinct issues with different remedies or timing.

4. Separate issuance, conversion, and exit consequences

Test each provision independently at each relevant stage. The SEC-filed CapCO2 SAFE form, Exhibit A §1(a) places qualified financing-document execution obligations at conversion. That wording does not establish a condition to initial SAFE funding. It is a contractual example from a crowdfunding filing, not a general rule or market-standard finding. (sec.gov)

Likewise, compare the actual scope of participation rights: a right limited to the financing where an existing SAFE converts is different from a right covering additional SAFE issuances. For exit provisions, read assignment and control definitions separately; do not assume they describe the same event.

Template output: assign a stage-specific conclusion and identify future dependencies. Explain whether present action is required, deferred, or unresolved because evidence is missing.

5. Separate contractual permissions from corporate authorization

Keep corporate approvals distinct from third-party consents. Use separate rows or cross-references so the evidence supporting one is not mistaken for evidence supporting the other.

For Delaware corporations, DGCL §157(a)–(b) addresses stock-acquisition rights and options, subject to the charter, with specified issuance matters governed by board resolutions. Counsel must assess its application to the particular SAFE; the section alone does not establish complete authorization. (delcode.delaware.gov)

Cross-reference the authorization workstream instead of reproducing it. Identify any contractual investor approval separately and check its threshold and amendment or waiver mechanism.

Template output: distinguish contractual consent, corporate authorization, express condition, covenant, representation, and internal recommendation. Record the source and the evidence still required for the relevant classification.

6. Set the company response and priority

Rank issues by consequence, trigger proximity, and evidentiary confidence. A restriction potentially affecting current issuance differs from a future conversion notice. Missing ownership evidence for essential technology may still require immediate escalation even without an issuance trigger.

Choose a specific response: obtain evidence, seek consent, negotiate a limited waiver, revise proposed terms, or escalate a documented risk to the authorized decision-maker. Identify who may grant consent or waiver and verify the required form. A business decision to accept risk is not evidence of contractual permission.

Template output: state the action, owner, target, and rationale. Explain which fact or document would change the recommendation and whether the proposed response addresses only this financing or future events too.

7. Verify conclusions and preserve open dependencies

Have the responsible lawyer re-read controlling text and cross-references for material conclusions. Reconcile the table against the final proposed SAFE package: changed investor identities, side-letter rights, or associated transactions may alter earlier findings.

Close an issue only when the disposition has supporting evidence. For future obligations, distinguish “assigned for later review” from “satisfied.” Record the source-defined trigger and handoff owner rather than substituting a generic calendar date.

Template output: cite resolution evidence and assign every remaining question. Prepare a concise decision summary separating current impediments, unresolved evidence gaps, accepted risks, and future obligations. Preserve the version of the proposed financing tested.

Worked example

Fictional scenario: Alder Circuit, Inc., a Delaware company, proposes a $1.8 million SAFE financing under package S-01. Counsel reviews a credit agreement, an existing investor’s SAFE and side letter, and a license supporting the company’s principal product. All parties, documents, amounts, and clause descriptions in this example are fictional.

The initial issue list calls all three matters “financing consents.” Document review produces different conclusions and next steps.

Row / document IDs Contract / status Clause / evidence Trigger / beneficiary Company effect Uncertainty / priority Action / owner / target Resolution evidence
R1 / D-04, S-01 Brook Lantern credit agreement; signed §6.4, p. 18: written consent for issuing securities convertible into stock SAFE issuance / lender Proposed SAFE appears within restriction; no exception located High; amendment completeness unconfirmed Confirm chain and seek specific consent; company counsel; before acceptance Open; no consent supplied
R2 / SL-02, S-00 Existing SAFE and side letter; signed SL-02 §2, p. 2 and S-00 definition: participation limited to priced preferred financing where S-00 converts Conversion / existing investor Supplied wording does not cover S-01 issuance Future-stage; supplied instruments reviewed Assign conversion-financing review; general counsel; before that financing Text verified; future review assigned, not satisfied
R3 / IP-07 Ember Loom license; signed base only §9.2, p. 11: termination tied to Control Event; definition schedule absent Control event / licensor Effect on essential license cannot be determined High; missing definition Obtain schedule and amendments; business owner; before diligence sign-off Open; trigger conclusion unsupported

R1 supports seeking transaction-specific consent, subject to confirming the operative chain. The draft consent should identify S-01 accurately; consent to a differently structured transaction would not resolve the recorded issue.

R2 should leave the present-consent list because the supplied right is limited to a later priced financing. That does not establish that every agreement with this investor is clear; the conclusion is bounded by the reviewed instruments.

R3 remains an evidence gap, not a confirmed prohibition or clearance. Because the license supports the principal product, missing evidence receives high priority. The table changes both the work plan and the precision of the risk report.

Common mistakes

  • Combining financing events. Replace “financing consent” with the actual issuance, conversion, or exit trigger and controlling definition.
  • Comparing labels rather than language. Test the proposed SAFE and side rights against each restriction, including exceptions and incorporated definitions.
  • Treating missing text as permission. State the review boundary and request omitted schedules before clearing the issue.
  • Calling every concern a closing condition. Identify its actual legal or contractual category and explain why present action is recommended.
  • Closing on an informal assurance. Obtain appropriate evidence and verify that consent covers the actual package, beneficiary, and required timing.

Final quality check

  • Every material conclusion has an operative document ID and section/page citation.
  • Amendments, schedules, side letters, and waivers are reconciled.
  • Each restriction identifies its event, beneficiary, and controlling definitions.
  • Verified facts, missing evidence, and interpretive questions remain distinct.
  • Corporate approvals are separate from contractual permissions.
  • Priorities explain company exposure and timing.
  • Closed issues have evidence; open issues have an owner and target.
  • The final comparison identifies the financing version tested and assigns future dependencies.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities support bulk document classification to organize review, while tabular review supports work across multiple documents. Use contract review for focused analysis with company-specific instructions. Keep operative-document selection, trigger interpretation, and final disposition with counsel; the comparison table remains the team’s work product. To assess this workflow for your practice, book a demo.

Frequently asked questions

Should every company contract appear in the comparison?

Maintain an inventory, then select contracts by transaction relevance and business dependence. Record exclusions. Expand review when definitions, cross-references, or new documents reveal additional exposure.

Should existing SAFEs and side letters share one row?

Link their document IDs, but separate issues with different triggers or responses. A present most-favored-nation question and a future participation right should not disappear into one summary.

Can a familiar SAFE form establish that no consent is needed?

No. Confirm the version and proposed changes, then test them against the existing agreement’s restriction. Form familiarity is not a substitute for that comparison.

How should the table handle missing pages?

Identify the pages, the conclusion they prevent, and the custodian responsible. Prioritize by potential exposure. Keep the issue open until evidence supports a conclusion or the unresolved risk is explicitly escalated and assigned.

Sources

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo