Lemon Squeezy Revenue: The $1M Number It Hit Before Selling to Its Biggest Rival (2026)

"Lemon Squeezy surpassed $1 million in annual recurring revenue nine months after its public launch." That line, reported by TechCrunch on the day Stripe bought the company in July 2024, is the number the internet has settled on. It is clean, it is fast, and it is the one figure almost every profile of Lemon Squeezy repeats.

It is also the least interesting number in the story.

The more revealing figures are the ones that are harder to find: the $50 million funding round its founder turned down, the 13 people who built the whole thing, and the acquisition price that, to this day, nobody outside the deal room knows. Lemon Squeezy is a rare case where the disclosed revenue tells you very little about what actually happened, or what an operator should learn from it. Here is the honest ledger, typed by source, and the part worth keeping.

Quick answer: what is Lemon Squeezy's revenue?

Lemon Squeezy reportedly surpassed $1 million in annual recurring revenue within nine months of its 2021 public launch, according to TechCrunch, Silicon Republic and FinTech Global (all July 2024). At the time Stripe acquired it in July 2024, it was a 13-person company that had turned down a reported $50 million Series A term sheet to stay independent. The acquisition price was never disclosed. Business trackers such as Crunchbase still list it in the broad "more than $1M in revenue" band, because Lemon Squeezy is private and publishes no audited figures. As of mid-2026 the product still operates and is being folded into Stripe's new "Stripe Managed Payments" offering. (2026)

The number everyone quotes, and the one no one can

Search "lemon squeezy revenue" and you get a tidy origin story: a merchant-of-record platform for digital products that hit $1 million in ARR in nine months, during the pandemic, and never looked back. That figure is real and well sourced. Three separate outlets reported it in July 2024, all tracing to founder JR Farr's own comments around the acquisition.

The trouble is that the number people quote as "Lemon Squeezy's revenue" is a milestone from roughly 2022, frozen in the coverage of a 2024 acquisition. It was never updated, because nine months after that milestone the company stopped being an independent business with its own reported numbers. There is no audited 2023, 2024 or 2025 revenue line, and there never will be, because the more important transaction, the sale to Stripe, closed on terms that were not disclosed.

So the honest position is this: the growth number is knowable and the outcome number is not. That gap is the whole point, and we will come back to why it matters for anyone building a small software business.

The revenue ledger, by year and by source type

Private companies file no audited revenue, so every line below is either something the company said, something a tracker reported, or an outside estimate. Keeping those categories separate is how you avoid repeating a bad number with false confidence. Here they are, typed:

One piece of texture the ledger cannot capture: Lemon Squeezy's revenue was never really the story its own customers cared about. In a 2026 r/SaaS thread, one seller running on the platform described "Revenue: $40K/month, take home: $6K/month" (self-reported, one merchant). That is a useful reminder of what the tool actually did for people, which turns out to be the real reason Stripe wanted it.

What Lemon Squeezy actually sold: the merchant-of-record moat

It is easy to file Lemon Squeezy under "nicer Stripe checkout." That misreads the product. Its wedge was being the merchant of record. As TechCrunch put it, "as a merchant of record, Lemon Squeezy calculates and pays global sales tax for digital products, handling legal processing and fees in every country."

That sentence is doing a lot of work. When you sell a digital product to a customer in Germany, Brazil or California, someone is legally on the hook to register for, collect and remit the local sales tax or VAT. If you use a raw payment processor, that someone is you. If you use a merchant of record, the platform becomes the seller of record and takes that liability off your plate, in exchange for a higher percentage of each transaction. Stripe itself is a processor, not a merchant of record, which is precisely the gap Lemon Squeezy filled and the reason indie sellers were willing to pay a premium of roughly 5% plus $0.50 per sale in 2026 pricing rather than a bare processing fee.

Competitors in the same merchant-of-record lane, Paddle and Polar among them, sold the identical promise: you make the product, we own the tax compliance. That is the category. Lemon Squeezy just wrapped it in the friendliest indie-founder branding of the bunch.

The exit: turning down $50M, then selling to the fee it was built to route around

Here is the tension the tidy version skips. Lemon Squeezy was built, in part, so small sellers could avoid stitching together Stripe plus a tax-compliance layer themselves. It routed around that complexity. And according to TechCrunch, founder JR Farr, a serial operator who previously ran MOJO Marketplace before it was acquired, turned down a reported $50 million Series A term sheet to keep the company independent and small.

Then, in July 2024, he sold it to Stripe.

There is no contradiction there, but there is a lesson. A 13-person, roughly $1M-ARR business does not command a headline acquisition on its revenue multiple alone. What Stripe bought was not the ARR. It was the merchant-of-record capability, the tax and compliance plumbing, and a team that had already built the seller-of-record experience Stripe itself lacked. The revenue was the smallest asset in the deal.

What happened after: Lemon Squeezy became Stripe's managed-payments engine

If you want to know what Stripe actually paid for, watch what it built. In 2025 Lemon Squeezy announced that its technology was becoming the foundation of Stripe Managed Payments, Stripe's own merchant-of-record product, launched in private preview. By January 2026, JR Farr confirmed the team was building migration paths from Lemon Squeezy over to Stripe Managed Payments, with public access on the way.

The clearest signal is buried in a Stripe support note: sellers on Stripe Managed Payments saw the legal entity on their invoices change, because "LemonSqueezy was the previous legal entity used for Stripe Managed Payments" before it moved to a new one. In other words, the thing Stripe acquired was not shut down and it was not left to drift. It became the merchant-of-record entity inside Stripe's own stack. As of mid-2026 the Lemon Squeezy product still runs, no shutdown, while the capability underneath it does the heavy lifting for a much larger company.

What an operator should take from this

Three things, none of which are the $1M number.

The disclosed number is rarely the one that matters. For a bootstrapped software business, ARR is a poor proxy for what the founder actually walks away with. Lemon Squeezy's revenue was public and modest; its outcome was private and, on the evidence of what Stripe built with it, significant. If you are benchmarking your own business against a competitor's "revenue," remember you are usually looking at the least consequential figure in their story.

Own the boring compliance layer, not the pretty checkout. Lemon Squeezy did not win, or get acquired, because its payment form looked nicer. It won because it absorbed global tax and VAT liability that its customers were terrified of. If you sell digital products across borders, the single most important question is not "which checkout looks best" but "who is the merchant of record," because that answer decides who is legally responsible for sales tax in dozens of jurisdictions. Boring, unglamorous plumbing is what strategic acquirers pay for.

Selling to your biggest competitor is a legitimate ending. Lemon Squeezy spent years helping sellers route around the friction of doing payments-plus-compliance yourself, then handed the whole capability to Stripe, the incumbent it defined itself against. That is not a defeat. It is a founder recognizing that distribution and integration inside a giant can be worth more than another decade of independent grind. Turning down $50 million to stay independent and then choosing a strategic exit two years later is not inconsistency. It is knowing which offer to take and when.

Keep reading

If the merchant-of-record and payments angle is what pulled you in, these first-person OperatorBook founder diaries sit right next to it:

• the-month-a-chargeback-wave-froze-my-stripe-at-23k-mrr , what it actually feels like when payment infrastructure turns against you overnight.
• the-month-i-made-refunds-one-click-and-my-churn-dropped-at-31k-mrr , a small payments-UX change with an outsized retention effect.
• the-month-one-customer-became-40-percent-of-my-mrr-36k , the concentration risk that hides inside a healthy-looking revenue number.