Series A-stage CFOs spend 40+ hours manually reconciling SAFE conversion scenarios because cap table tools don't model edge cases

finance0 views
A B2B startup's first CFO hire is trying to model how 6 different SAFEs with varying caps, discounts, MFN clauses, and pro-rata side letters will convert in a Series A priced round, but Carta and Pulley's scenario modeling breaks down when you stack post-money SAFEs issued at different times with an MFN clause that references a pre-money SAFE from 2 years earlier. So what? The CFO has to build a parallel spreadsheet to verify the cap table tool's outputs, effectively doing the work twice. So what? When the lead investor's counsel sends their own conversion waterfall, numbers don't match by 0.3-0.8%, and neither side can pinpoint which assumption diverges. So what? This discrepancy stalls legal closing by 2-3 weeks while lawyers bill $800/hour to reconcile spreadsheets. So what? The founder is distracted from running the business during the most critical post-term-sheet period, and every week of delay increases the risk of the deal falling apart. So what? In a down market, a 3-week delay can coincide with a macro event that gives the lead investor cold feet and triggers a re-trade on valuation. This problem persists structurally because SAFE instruments have proliferated into dozens of variants (YC post-money, pre-money, MFN, pro-rata side letters) faster than cap table software can build reliable conversion logic for every combination, and there is no industry-standard specification for how edge cases should resolve.

Evidence

Carta's own support forums show recurring questions about SAFE conversion discrepancies. YC updated the SAFE from pre-money to post-money in 2018, but many companies have both types outstanding. AngelList and Clerky have documented that MFN clauses interacting with post-money SAFEs create ambiguity that requires legal interpretation, not just arithmetic.

Comments