What makes a Shopify app
worth acquiring?
I've been on both sides.

I sold getuptime.co to Tiny — the TSX-listed holding company that also owns Letterboxd, Dribbble, and a portfolio of other profitable internet businesses. The process taught me more about SaaS valuation in three months than fifteen years of building had.

What I learned: most founders who enter acquisition conversations are dramatically underprepared. Not because they haven't thought about exits — most have, at least in abstract terms — but because the specific things that move multiples are almost never what founders spend their time optimizing. You can build a genuinely good product with happy customers and still accept a substantially worse outcome than the business deserves because the financial packaging wasn't there.

This is the post I wish I'd had earlier. It's based on my own transaction, on the dozens of conversations I've had with app founders in the Shopify ecosystem since, and on advising companies as they navigate acquisition processes. The Shopify app ecosystem specifically has dynamics that generic SaaS acquisition advice doesn't account for — and those differences matter when someone is underwriting a multiple.

The acquirer cares about
one thing above all others.
It's not what you think.

Every acquisition conversation eventually comes down to a single question the acquirer is asking themselves: will this business be worth more in three to five years than what I'm paying today, and is the risk appropriate? Every metric, every due diligence request, every negotiation point is downstream of that question.

Founders often conflate "the acquirer loves our product" with "the acquirer will pay a premium." Those are different things. A buyer can love the product and still price it conservatively because the financials carry risk. The premium comes from eliminating uncertainty — about revenue quality, about team dependency, about customer concentration, about platform exposure. The more of those uncertainties you've resolved before the conversation starts, the better your outcome.

In the Shopify app ecosystem specifically, there are three categories of acquirer. Each underwrites differently, moves on different timelines, and values different things. Knowing which type you're talking to is step one of any process.

The financial metrics a sophisticated
buyer examines
in the first 24 hours.

When a holding company or PE firm receives your financials, they run a specific set of calculations in a specific order. Understanding that order matters because it tells you which improvements will move your multiple the most.

Net Revenue Retention — The Single Most Important Number

NRR is (Starting MRR + Expansion − Churn − Contraction) ÷ Starting MRR × 100. An NRR above 100% means your existing customer base is growing revenue even without new customers. A buyer who sees NRR of 110% is looking at a business that compounds — and that's worth a meaningfully higher multiple than a flat or declining base.

In the Shopify app ecosystem, NRR is harder to achieve than in traditional B2B SaaS because merchant plans are often fixed-price tiers with limited expansion opportunity. The apps that crack NRR above 100% do it through usage-based pricing overlays, tiered feature unlocks, and successful upsell paths to higher plan tiers. If your pricing structure doesn't create natural expansion, NRR improvement requires deliberate product work.

Revenue Quality and Predictability

Acquirers are not just buying ARR — they're buying predictability. Three years of clean, audited (or at minimum CPA-reviewed) financials showing consistent MRR growth with low variance tells a clear story. One year of hockey-stick growth followed by a flat year raises questions about whether the growth was sustainable or event-driven.

For Shopify apps specifically, seasonal revenue patterns are common — merchants install apps before Q4, churn them in January. Buyers discount this. If your MRR has a December spike and a January crater, model that out explicitly in your data room. Buyers who discover it themselves price it as a risk; buyers you've walked through it treat it as an acknowledged operational pattern.

The LTV:CAC Ratio

How much does it cost you to acquire a new merchant, and how long do they stay? A business with a 12-month CAC payback and 3-year average customer life is producing a reasonable LTV:CAC. A business with an 18-month payback on customers who churn at month 14 is destroying capital with every install. Know your numbers before someone else calculates them.

The things that move multiples
that no one tells you
to focus on.

The financial metrics are table stakes. Every founder going into an acquisition process knows they'll be asked about ARR, churn, and NRR. What catches founders off guard is the depth of scrutiny on the things they didn't think were due diligence items.

The Key-Man Dependency Problem

When I went through my own process, one of the first things an acquirer wants to understand is: what happens if the founder leaves on day one after close? For most bootstrapped app founders, the honest answer is "quite a lot breaks." You are the support escalation path. You have the customer relationships. You know the undocumented edge cases in the codebase. You are, in an operational sense, the business.

This is called key-man risk, and it is priced into the deal — either through a lower multiple, earnout structures that keep you tied to the business post-acquisition, or both. The way to neutralize it is to build a business that runs without you before you enter any process. Document support procedures. Delegate customer relationships. Write down every piece of institutional knowledge that only exists in your head.

App Store Dependency and Distribution Concentration

Shopify-specific buyers scrutinize App Store dependency closely. An app that gets 90% of new installs from organic App Store discovery has a distribution risk that a buyer will price. What if Shopify changes the App Store ranking algorithm? What if Shopify builds the feature natively? What if a well-funded competitor starts outbidding you for App Store placement?

The apps that command premium multiples have distribution that goes beyond the App Store — partner integrations, merchant community presence, direct relationships, and owned channels like email and SEO. This isn't just a growth strategy; it's a risk mitigation story that translates directly into valuation. See the full playbook in our piece on Shopify app distribution.

Technical Debt and Infrastructure

A PE firm doing diligence on a Shopify app will run a technical review. Not a deep audit — but enough to identify red flags: a codebase with no tests, infrastructure that requires the founder to manually restart processes, or a database architecture that will require significant refactoring to scale. These are all priced as risk. A clean, documented, maintainable codebase is worth more than an equally functional one that only the founder understands.

Every Shopify app has
platform risk. The question is
how much you've mitigated it.

Any app that lives inside the Shopify ecosystem has a fundamental exposure: Shopify can build the feature natively, change the App Store algorithm, deprecate the APIs you depend on, or adjust its pricing in ways that make your app unnecessary. Shopify has done all of these things before — the Scripts API sunset is a recent example that made this concrete for thousands of app builders.

The apps that trade at premium multiples have mitigated platform risk in demonstrable ways. Multi-platform distribution (the app works on not just Shopify but Woo, BigCommerce, or headless stacks) is one approach. Deep merchant data moats — where the app holds years of merchant-specific behavioral data that would be lost on churn — is another. And deep integrations with the rest of the merchant's stack (Klaviyo, Recharge, etc.) create lock-in that doesn't depend on any single platform.

The PE firms active in this space are aware of all of this. They are building discounts into their models for platform concentration that they don't build for comparable SaaS in other verticals. Be prepared to address it directly.

Acquisition readiness is
an 18-month project, not
a 60-day sprint.

The most common mistake I see from founders entering an acquisition process is trying to clean up in the data room. You get a term sheet, you start pulling together financials, and you discover that three years of bookkeeping needs to be reconstructed, that your MRR numbers in Stripe don't match your spreadsheet, and that your support process lives entirely in your head and two Notion pages nobody else can read.

Buyers have seen this before. The response isn't to pull out — it's to price the risk and slow the process. Both outcomes cost you.

I went through my own acquisition process with a lot of the right pieces in place — and it still surfaced things I hadn't expected. The founders who come out of these processes with the outcomes they wanted are the ones who spent twelve to eighteen months building acquisition readiness before the conversation started, not the ones who tried to package the business in the data room after the term sheet arrived.

The Shopify app M&A market is more active than it has been at any point in the ecosystem's history. The window where you're the one setting terms, not responding to them, is real — and it closes faster than most founders expect. See also: the PE activity reshaping the Shopify app ecosystem right now.