Most coverage of Fresha's $1 billion valuation is written for investors: free product, marketplace fee, KKR writes an $80 million cheque, done. That's the business story. It skips the part that's actually interesting if you build software for a living — what a decision like "give the core product away for free" actually costs and demands on the engineering side.
The facts, quickly: Fresha (founded 2015 as Shedul, out of the UAE, later headquartered in London) gave away its scheduling, client management, and point-of-sale software to salons and spas at zero cost. It monetised through a transaction fee on consumer bookings instead. In May 2026, KKR invested $80 million, valuing the company above $1 billion. By then it was processing more than 35 million appointments a month for roughly 130,000 businesses across 120 countries, with a revenue run-rate above $140 million growing 60%+ a year — and already profitable.
The rest of this isn't sourced from Fresha's engineering team — it's the set of problems that decision necessarily creates, worth thinking through if you're building anything similar.
Free doesn't mean cheap to run
"Free" is a pricing decision, not an infrastructure discount. Every one of those 130,000 businesses still needs onboarding, support, uptime, and data storage — and none of them are paying a subscription to cover it. When your monetisation is a thin percentage of transactions rather than a flat fee per account, the cost of serving a free user has to be low enough that the transaction fee on their eventual bookings covers it. That's a completely different constraint than SaaS teams building for a $99/month tier are used to designing against. It pushes hard toward low-touch onboarding, self-serve support, and infrastructure that scales close to linearly with usage — because there's no subscription cushion absorbing the difference.
Payments become the actual core product
Once revenue comes from a cut of every booking, payments isn't a bolt-on Stripe integration anymore — it's the thing the whole business stands on. At the volume Fresha is reportedly handling, that means reconciliation across multiple currencies and countries, handling refunds and no-shows without breaking revenue attribution, and keeping payment latency low enough that it doesn't get in the way of a customer booking a haircut. Scheduling software with payments bolted on and a payments platform with scheduling bolted on are architecturally different systems, even if the UI looks the same to the salon owner.
The lending product is really a data engineering problem
Fresha Capital — the lending product built on top of transaction history — is the part of this story that's easy to describe in a pitch deck and genuinely hard to build. Underwriting a loan off a business's real transaction data instead of a bank statement sounds simple until you have to do it reliably, in near-real time, across businesses with wildly different seasonality, in dozens of countries with different regulatory rules for consumer lending. That's not a feature you ship in a sprint. It's a data pipeline, a risk model, and a compliance surface all growing at the same time as the core product.
Why this is worth caring about even outside fintech
The broader pattern applies to any vertical SaaS product considering a free-plus-transaction-fee model: the free tier is a growth lever, but it quietly shifts your hardest engineering problems from "how do we build features people will pay for" to "how do we build infrastructure cheap and reliable enough to give away, on top of a payments layer solid enough to trust with someone else's income." That second problem is the one that actually determines whether the model works.
Fresha didn't get to a $1 billion valuation because giving software away is a clever growth hack. It got there because it apparently built the boring, expensive infrastructure underneath the free product well enough that the free product could scale without breaking the business. That part rarely makes the funding headline, but it's usually the part that decided whether the company survived long enough to get one.
Business figures above are drawn from KKR and Business Wire's May 2026 investment announcement and subsequent reporting (Sifted, The Next Web, TechFundingNews, EU-Startups). The engineering analysis is inference based on the scale and model described, not confirmed detail about Fresha's actual systems.
Tags: #saas #fintech #startup #discuss
Top comments (0)