Convertir un SAFE: los tres precios candidatos

Por el equipo de OrgGen AI

Un SAFE no convierte «al límite» ni «al descuento»: convierte al más bajo de tres precios candidatos. Esta guía da el cálculo exacto, muestra por qué un límite post-money de 8 M no es un límite pre-money de 8 M, y nombra las dos situaciones en que el límite no cambia nada.

Esta guía solo está disponible en inglés. El título y el resumen de arriba sí están traducidos.

The calculation: three candidates, the lowest wins

When a priced round closes, every outstanding SAFE turns into shares. The number of shares issued depends on a conversion price, and that price is not chosen: it is the minimum of three candidates.

roundPrice      = preMoneyValuation / sharesBeforeRound
discountPrice   = roundPrice × (1 − discount)
capPrice        = effectiveCap / sharesBeforeRound

conversionPrice = min(roundPrice, discountPrice, capPrice)
sharesIssued    = amountInvested / conversionPrice
The effective conversion price

The lowest of the three wins, and that is the only rule. A SAFE that carries both a cap and a discount never stacks the two benefits: it takes the one that gives it more shares, which means the lower price.

Two practical consequences. A SAFE with no discount has only two candidates: the round price and the cap. A SAFE with no cap has two as well. And a SAFE with neither cap nor discount converts at the round price, like any ordinary investor: all it ever gave its holder was having come in earlier.

Pre-money or post-money: the same number, two outcomes

This is where people go wrong most often, because both contracts show the same figure in the same place. Since 2018, the standard Y Combinator SAFE (v2) is a post-money SAFE. The original SAFE, still being signed, is pre-money.

Basis of the capWhat the cap guaranteesDenominator of the calculation
post-money (YC v2, since 2018)a share of the capital AFTER conversion: amount ÷ capcap − amount invested
pre-money (original)a price per share, not a share of the capitalcap

A post-money SAFE of €500k with an €8M cap guarantees 6.25% of the capital once converted, whatever happens to the rest of the round. The same figure on a pre-money contract guarantees nothing of the kind: it sets a price per share, and the final stake depends on everything else that dilutes alongside it, other SAFEs included.

The practical conclusion is short: before you simulate, check on the contract which of the two regimes applies. It is a single checkbox, and it moves the result by several percentage points of ownership.

The two cases where the cap does not bind

A cap written into the contract is not necessarily a cap that applies. Two situations neutralize it, and neither raises an error: the calculation carries on, and the cap simply stops being among the candidates that can win.

  1. The round is priced BELOW the cap. If the round price is already lower than the price the cap would imply, the round price (or the discount) wins. The cap never came into play, and that is the normal case for a modest round.
  2. The post-money cap is less than or equal to the amount invested. The pre-money equivalent becomes zero or negative: the cap stops being a candidate. This is a malformed contract, not a scenario to model, but the calculation does not stop on it.

The second case deserves a closer look: it raises no accounting alert. If you see a conversion that returns far fewer shares than expected, compare the cap to the amount before looking anywhere else.

Doing it in OrgGen

The conversion is a tool your agent calls, either in the OrgGen chat or from your own client over MCP. It takes the SAFE identifier and the price per share of the next round.

convert_safe({
  safeId: "safe-business-angels",
  nextRoundPricePerShare: 12.50
})
Pure simulation: nothing is written

By default, the call changes NOTHING: it returns the effective price, the candidate that won and the number of shares, and the schema stays untouched. This is the mode you want for comparing several price assumptions before settling on one.

To make the conversion real, you have to ask for it explicitly: the holder then moves from the SAFE type to the preferred stock type, and their share count becomes the one just calculated. The switch is a separate parameter, precisely so that an exploration can never change the cap table by accident.

Pruébalo con tu propio caso

Describe tu situación en una frase — OrgGen construye el diagrama y hace el cálculo.

Pruébalo con tu propio caso

← Todas las guías