Miro's $1.36B Exit: A Growth Valuation Stress Test
Use Miro's $1.36B Bending Spoons exit to stress-test user growth, enterprise ARR, cash, and headcount before paying a premium.
When a collaboration tool reports a big user jump, the valuation question is whether the growth is worth paying for. Miro, a collaboration tool, was valued at $17.5 billion in late 2021, and Bending Spoons' cash deal later valued it at $1.36 billion, with an equity value of about $1.79 billion after net cash. The gap gives a clean way to separate user-scale hype from durable revenue quality, and the exit puts the numbers in one place.
Paying users carry the premium
Total users can be free, trial, dormant, or hard to convert. Paying users are the part of the base that underwrites a price. Miro's user base reached 100 million total users, including more than 4 million paying users. A premium built on total users assumes conversion that may never show up in revenue. A defensible premium needs a ratio the investor can state and defend: how many of the total base actually pay, and whether that ratio is stable or rising.
Growth in the paying base matters more than growth in total users. Miro's user count rose from 5 million to roughly 30 million by 2022, over a two-year period, while its paying customer base grew 550%. That sequence shows the company was not just collecting signups; it was moving a larger share of its base into revenue. If paying growth slows while total users keep rising, the valuation is leaning on a future that the current base does not prove. The comparison to keep is whether the paying base grew faster, slower, or in line with total users.
A big user number can make a valuation look bigger than the paying base supports. If the free base is huge but the paying base is thin, the premium depends on future conversion, not current cash. The growth source also matters: if the company is buying users with free tiers, discounts, or aggressive sales, the revenue may not arrive on the schedule the valuation assumes. Label the growth as organic, sales-led, or discount-driven, and note which assumption is least defensible.
Enterprise ARR and profit set the ceiling
Enterprise ARR deserves more weight than consumer-style usage. Enterprise contracts are easier to model, renew, and defend. Consumer usage can spike and then flatten. Miro's annual recurring revenue was about $600 million, with business and enterprise customers accounting for nearly 90%, and the company is profitable. The mix matters because enterprise revenue is the part of the bridge that can be audited, forecast, and defended. A revenue bridge should name the enterprise share, the total ARR, and the portion discounted for lower retention.
Profitability changes the base case. The business can support itself without assuming another funding round. If profit depends on a one-time cost save or a promotional spike, the assumption needs a date and a trigger. The note to keep is the profit status and the assumption that keeps it true.
Enterprise ARR is only useful if the buyer can see why the contract stays. Ask whether the product is embedded in a workflow, whether the buyer has a named champion, and whether the tool can expand across teams. A short memo can name the workflow, the champion, and the expansion path, and mark which of those is missing.
Cash and headcount expose the multiple
Subtract the cash from the price before judging the multiple. At agreement, Miro held roughly $435 million in net cash. Net cash changes the effective price and the multiple the buyer actually pays for the business. The cash price and equity value show how much of the purchase was funded by the target's own balance sheet.
Headcount is a signal as well as a cost item. Miro employed about 1,200 people in 2022, then reduced headcount by 119 in February 2023 and reportedly by another 275 in October 2024. A company can grow users and revenue while trimming staff, which changes the cost base and the story of what the growth is buying.
The timing of cuts matters. A cut before a revenue inflection can be a cost reset. A cut after a revenue inflection can be a warning that the growth is not scaling the team. Place each cut next to the revenue milestone and say whether the cost base is moving closer or farther.
The drop from the 2021 mark to the exit is a checklist. Compare total users, paying users, enterprise ARR mix, profitability, net cash, and headcount cuts before assigning a growth premium. If they point the same way, the premium has a case; if not, lower the premium and ask for a longer revenue runway.