Acquirers care about three things in order: net revenue retention above 100 percent, customer concentration below 10 to 15 percent for any single account, and low founder dependency. Everything else in diligence is downstream of whether the honest answer to those three is yes.
- NRR above 100 percent proves the revenue base compounds without constant new acquisition.
- Low customer concentration removes the binary risk of a single churn event resetting the business.
- The factors that move the multiple are almost never what founders spend their time optimizing.
The top three things acquirers care about, in order: net revenue retention above 100% (proves the revenue base compounds without constant new customer acquisition), customer concentration below 10 to 15% for any single account (eliminates the binary risk of a single churn event), and low founder dependency (proves the business runs after you leave). Everything else in a diligence process is downstream of whether the honest answer to those three is yes.
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. A good first step is knowing your starting point: my free tool to estimate what your Shopify app is worth applies the same factors buyers diligence.
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. If you want to know which ones are still open in your business, score your app's exit readiness before a buyer does it for you.
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.
| Buyer Type | Primary Motivation | Typical Multiple | Timeline |
|---|---|---|---|
Holding Companies Tiny, Permanent Equity, etc. |
Durable cash flow at fair price. Will hold indefinitely. Low operational interference. |
3–6× ARR Higher for exceptional NRR |
Fast. 30–60 days if prepared. |
PE Roll-Ups Category consolidators |
Portfolio economics, combine revenue, reduce costs, exit in 3–5 years. Financial metrics dominant. |
4–8× ARR Compressed for low NRR |
60–120 days. Heavier diligence. |
Strategic Acquirers Larger apps, adjacent SaaS |
Product or customer synergy. Acquire capability they can't build in time. |
Variable. Can exceed ARR multiple if strategic fit is strong. |
3–9 months. Integration complexity drives timeline. |
Acqui-Hires Larger tech or SaaS |
Engineering talent or specific technical IP. Product value secondary. |
ARR + per-head team premium |
Variable. Often faster once decided. |
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. Margin sits near the top of that list, so work out your gross margin the way an acquirer does, net of revenue share and infrastructure, before anyone else runs it.
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.
This is the work I do, with Shopify app and SaaS founders. I ran the DTC brands your app was trying to win. That vantage point is harder to find than you'd expect. The form takes two minutes.
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.
"A business that runs without the founder is worth substantially more than an identical business that doesn't. The delta is not trivial, it's often 1–2 turns of ARR."
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 most acute platform risk for Shopify apps is "Shopify builds it themselves." It happened with abandoned cart recovery, discount codes, basic review functionality, and upsell flows, all previously served by third-party apps that lost significant revenue overnight when Shopify added the feature to core.
A buyer underwriting a Shopify app will ask, directly or implicitly: is there a version of Shopify's roadmap where this app becomes redundant? The best answers either demonstrate that the app's complexity is far beyond what Shopify would productize natively, or show that the merchant relationships and data lock-in create switching costs regardless of feature parity.
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 does not depend on any single platform.
The PE firms active in this space are aware of all of this. They build discounts into their models for platform concentration that they do not build for comparable SaaS in other verticals. Be prepared to address it directly. For the current landscape of which PE firms are active and how they underwrite, read how private equity is buying Shopify apps.
API version dependency as a specific risk
One platform risk that surfaces in technical diligence and rarely gets discussed is API version dependency. Shopify deprecates API versions on a rolling schedule. An app still relying on older or recently deprecated endpoints carries a technical remediation cost that a buyer has to price. If your app is not current on Shopify's latest supported API versions, document the gap and the estimated remediation effort before diligence begins. A known, quantified cost is far less damaging than one a buyer discovers themselves. The Shopify Scripts API sunset is a concrete recent example of how quickly this risk can materialize for whole categories of apps.
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.
Common
questions.
What do buyers look for when acquiring a Shopify app?
The top three criteria in order: (1) net revenue retention above 100%, proving the base compounds without constant new customer acquisition; (2) customer concentration below 10 to 15% for any single account; and (3) low founder dependency, where the business runs after you leave. Everything else in diligence is downstream of those three. Get clean on all three before any conversation starts. The full method is in how to value a Shopify app.
What multiple do Shopify apps sell for?
Holding companies like Tiny pay 3 to 6x ARR and close in 30 to 60 days for well-prepared businesses. PE roll-ups pay 4 to 8x ARR but compress for low NRR and run 60 to 120-day diligence processes. Strategic acquirers are variable and can exceed ARR multiples when product or customer fit is strong. Knowing your buyer type shapes how you prepare. Detailed ranges are in what Shopify apps sell for in 2026.
How does customer concentration affect an acquisition?
Any single customer above 10 to 15% of MRR represents a binary risk event that PE firms model explicitly. A buyer who sees one customer at 25% of MRR is pricing in the scenario where that customer churns the day after close. The fix is diversifying the customer base over 12 to 18 months before entering any process. The full mechanics are in how customer concentration kills valuation.
What is key-man risk and how much does it affect my valuation?
Key-man risk is the degree to which the business depends on the founder to function. If you are the only one handling escalations, knowing undocumented edge cases, and holding key customer relationships, a buyer is acquiring a job, not an asset. The delta between a business that runs without the founder and one that does not is often 1 to 2 turns of ARR in the final multiple. Document everything. Delegate deliberately before you start any process.
How long does acquisition preparation take?
Eighteen months minimum for a well-prepared process. The first months go to CPA-reviewed financials, NRR tracking, and key-man documentation. The following months go to reducing dependencies, building distribution beyond the App Store, and diversifying the customer base. Founders who compress this into 60 days of data room cleanup discover that buyers price that uncertainty into the offer. Run your preparation before any inbound conversation begins, not after.
I went through my own acquisition process with a lot of the right pieces in place, and it still surfaced things I had not 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 are 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 and the Shopify app M&A market in 2026 for a current read on who is buying and at what terms.
If an exit is anywhere on your roadmap, building toward what acquirers actually value should start well before you run a process. The Consumer SaaS practice helps you get there. The form takes two minutes: start the conversation.
Building in the Shopify ecosystem?
I helped build the Shopify Partner Program. I also ran the DTC brands your app is trying to win. That combination (ecosystem insider and the customer you're selling to) is a hard thing to find in one person. If you're building in the ecosystem, the form takes two minutes.
Start a conversation More about Taylor →