SAFE Valuation Cap vs Discount: Calculate Which Conversion Term Applies

Work through a simplified SAFE conversion using a valuation cap, discount, share price, dilution assumptions, and document-specific definitions.

In this article

SAFE Valuation Cap vs Discount: Calculate Which Conversion Term Applies

A SAFE often converts in a priced equity round using the more favorable share price produced by a valuation cap or discount, subject to the exact document. The calculation is easy to oversimplify because pre-money and post-money forms, company capitalization, option pools, other SAFEs, and round terms change the denominator.

The practical problem

Suppose new investors pay RM10 per share. A SAFE provides a 20% discount, producing RM8 per share. If its valuation-cap calculation under the agreement produces RM6.50 per share, the lower cap price is more favorable and would generally determine conversion. A RM650,000 investment would convert into 100,000 shares at RM6.50 in this simplified example. That result is not a full capitalization table because the document defines which securities count in company capitalization.

This scenario defines the boundary for safe valuation cap vs discount: the system of record, the component that enforces the decision, the asset or money at risk, and the condition that ends an exception. If one of those is unknown, discover it before changing production or presenting the number.

A step-by-step workflow

  1. Scope the system. Identify the exact SAFE form and governing terms.
  2. Establish the baseline. List investment amount, cap, discount, pro rata rights, side letters, and most-favored-nation provisions.
  3. Apply the control. Build the pre-round capitalization using the agreement’s definitions.
  4. Test failure paths. Calculate the priced-round share price.
  5. Verify the result. Calculate the discount price.
  6. Record ownership. Calculate the cap price with the correct denominator.
  7. Close the loop. Select the applicable conversion method.
  8. Review the change. Add new-money shares and option-pool changes.
  9. Complete the review. Test multiple round sizes and valuations.
  10. Complete the review. Reconcile every scenario to the legal documents..

Prove the failure paths

Start with a healthy case based on “Identify the exact SAFE form and governing terms”, then repeat the exercise while deliberately violating the assumption behind “calculate the priced-round share price”. Capture the observable result, the alert that should fire, and the person who decides whether to stop or continue. Next, simulate the most credible failure in this guide: dividing the cap by today’s basic shares may ignore included options or convertibles. The test passes only when the team detects the condition, limits its impact, and restores service or the decision model without relying on undocumented knowledge. A final replay should cover treating a post-money SAFE like a pre-money form distorts dilution; this is the check most likely to reveal that a control works in a diagram but not at the actual boundary.

Evidence worth keeping

  • Retain document version
  • Defined capitalization
  • Security-by-security assumptions
  • Calculation formulas
  • Scenario date
  • Legal review notes
  • And a fully diluted ownership bridge before and after the round.

Attach each record to the concrete object under review: the relevant asset, release, customer, contract, key, query, or configuration. Preserve timestamps and version identifiers so another reviewer can reconstruct the sequence. The evidence list above should answer three questions: what was true before the change, what changed, and what proves the intended outcome. For this topic, the most useful cross-check is “calculate the discount price”. Keep sensitive fields out of screenshots and tickets; retain structured exports or signed records when they provide stronger provenance. Set retention according to incident, audit, privacy, and contractual needs rather than keeping everything indefinitely.

Common mistakes

  • Dividing the cap by today’s basic shares may ignore included options or convertibles.
  • applying both cap and discount simultaneously may be wrong.
  • treating a post-money SAFE like a pre-money form distorts dilution.
  • ignoring an option-pool increase understates founder dilution.
  • a spreadsheet cannot resolve ambiguous drafting..

A focused operating checklist

  • Name the owner of the system and the owner of the decision.
  • Verify “list investment amount, cap, discount, pro rata rights, side letters, and most-favored-nation provisions” from the actual production or financial source.
  • Exercise the failure described by “Dividing the cap by today’s basic shares may ignore included options or convertibles”.
  • Reconcile the observed result with the evidence list above.
  • Put an expiry and rollback condition on every exception.
  • Monitor the user, security, reliability, or cash outcome—not only activity.
  • Revisit dependencies when the underlying product, contract, or standard changes.

Make this control sustainable

Assign the owner closest to the enforcement point described in “build the pre-round capitalization using the agreement’s definitions”, plus a backup who can execute the rollback. Review the control after a material release, supplier change, incident, financing event, or policy change that affects its assumptions. An alert is useful only when it names an action: inspect, throttle, revoke, reconcile, fail over, or escalate. Use the evidence measurements above to set thresholds from observed workload or financial behavior. Treat applying both cap and discount simultaneously may be wrong as a specific review trigger. Close temporary exceptions with an owner, expiry, compensating control, and proof that the normal path was restored.

Primary references and further verification

This is educational modeling, not legal, tax, or investment advice. Use the executed agreement and qualified counsel because small definition differences can materially change conversion.

For a current safe valuation cap vs discount decision, record the publication or effective date of the primary material and the version actually deployed or executed. Recheck vendor, standards-body, regulator, or accounting guidance when the product, protocol, vulnerability, or contract changes. Discovery summaries can point to an issue, but the decision record should link to the authoritative source and the organization’s own reproducible evidence.

Conclusion

The practical outcome is a control the team can explain and test: identify the exact SAFE form and governing terms, then reconcile every scenario to the legal documents.. Keep the assumptions and exception path visible. That is more useful than a generic checklist because the next reviewer can reproduce the decision, see where it can fail, and reverse it safely.

Advertisement