What Buyers Actually Check Before Acquiring an App (2026)

Buyers acquiring an app in 2026 check five things, in roughly this order: revenue they can verify inside the developer console (not in a spreadsheet the seller made), the durability of that revenue (retention, churn, and how much of it depends on paid acquisition), clean ownership of the code and IP, the true cost of running the thing, and whether the app can actually be transferred without losing what makes it valuable. Everything else — the pitch deck, the roadmap, the "untapped potential" — is decoration. If you operate a portfolio and ever plan to sell an app out of it, or buy one into it, the checklist below is what the other side of the table is working through.

Verified revenue beats reported revenue, every time

The first thing serious buyers do is refuse to take the seller's numbers as given. Flippa's guide to acquiring a mobile app business is blunt about it: request direct access to the developer account — App Store Connect or Google Play Console — and verify download and revenue trends yourself, including refund rates and whether the downloads are organic or propped up by ad spend that stops the day the seller does.

The due diligence checklist at whatsthe.app puts a number on how far back to look: at least 6–12 months of historical console data, cross-checked against payment-processor statements from the likes of Stripe, RevenueCat, or Adapty, so you see net revenue after fees rather than gross top-line. The same checklist flags the quiet liabilities that follow an app to its new owner: pending refunds, chargebacks, and unpaid contractor obligations.

For subscription apps the interrogation goes one layer deeper: active subscriber counts, churn, lifetime value, and average revenue per paying user. A subscription business where half the MRR sits in a cohort acquired through a promo three months ago is a very different asset from one with two years of flat retention.

Multiples have collapsed, and that changed what gets scrutinized

The single most important market fact for anyone on either side of an app deal: multiples are a fraction of what they were. According to Flippa's mobile app valuation data, profit multiples on their marketplace fell from 9.92x in H2 2022 to 2.93x in H2 2024, and revenue multiples from 8.23x to 2.52x over the same window. Flippa's own read on the shift is that profitability and revenue stability are now the key drivers — buyers stopped paying for speculative growth.

That collapse explains buyer behavior. When you're paying 8x revenue, you're buying a story. When you're paying ~3x profit, you're buying a cash-flow machine, and you inspect it like one. The valuation methods themselves are standard — revenue multiple, EBITDA multiple, discounted cash flow for growth-stage apps, and per-user valuations for pre-profit scale plays — but the weighting has moved hard toward the boring ones. Retention and recurring revenue push the multiple up; dependence on paid installs and volatile month-to-month revenue pushes it down.

Acquire.com's due diligence checklist — written for online businesses generally — names the pattern buyers hunt for: unexplained revenue swings, aggressive accounting, and customer concentration. In app terms, concentration risk looks like one country, one keyword ranking, or one platform featuring driving most of the installs.

The metrics behind the metrics

Beyond the money, buyers read the app's public footprint as a diligence document. Flippa's acquisition guide recommends checking keyword rankings — apps ranking well organically "can expect to see a continuous flow of new users without any ad spend" — and reading the reviews, with particular attention to 3–4 star ratings, which is where honest, specific criticism lives. One-star reviews are noise; four-star reviews are a free product audit.

Acquisition channel mix gets the same treatment. The question a buyer is really asking: if I stop every paid campaign tomorrow, what does next month's revenue look like? An app whose installs are mostly organic search survives that test. An app that is a machine for converting ad spend into installs is a media-buying operation wearing an app costume, and it gets valued accordingly.

Code, IP, and the paperwork nobody enjoys

Technical and legal diligence is where indie-built apps most often stumble, because solo developers rarely kept the paperwork a buyer's lawyer will ask for. The whatsthe.app checklist covers the technical side — code quality and outdated dependencies, whether the stack is still supported, whether third-party API keys are actually transferable, and open-source license compliance in the codebase — and the legal side: ownership verified against the store console, trademark conflicts, privacy-policy and GDPR posture, and, critically, work-for-hire agreements that properly assigned IP from every contractor who ever touched the code. Acquire.com's framework adds litigation history and material contracts to the same pile.

The one that catches sellers off guard most often is the contractor question. If a freelancer built your onboarding flow in 2023 and there's no signed IP assignment, the buyer's position is that you're selling something you don't fully own.

The transfer itself is part of diligence

Sophisticated buyers check the mechanics of the handover before they wire anything, because not everything moves. On Google Play, the official transfer documentation is clear about what carries over — the user base, download statistics, ratings and reviews, subscriptions, and the store listing — and what doesn't: closed testing groups have to be recreated, permissions for integrated services like Firebase and AdMob have to be re-established, and historical payout and earnings reports stay with the old account. The transfer requires transaction IDs from both developer accounts, an active payments profile on the receiving account for paid apps, and typically takes about two business days of review. Apple runs its own transfer process through App Store Connect with its own eligibility criteria; buyers verify against Apple's current documentation before closing, and both checklists above recommend escrow for the payment leg regardless of platform.

The operational takeaway for portfolio operators: run your apps as if a transfer request could land next quarter. Keep integrated services documented, keep contractor IP assignments signed, and keep revenue legible in the console rather than reconstructed in spreadsheets. (This legibility problem — knowing what each app in a portfolio is actually doing without logging into five dashboards — is the territory Kintsu, currently in private beta and built for indie developers, works in.)

Sell-side conclusion: diligence is symmetric

Every item above doubles as a seller's prep list. Verified console revenue, 12 months of clean processor statements, documented churn, organic acquisition, assigned IP, and a transfer-ready account setup aren't just things that survive diligence — per Flippa's data, they're precisely the attributes that separate a 2.5x app from something better in a market that no longer pays for stories. The buyers didn't get meaner. The multiple compression just made them honest.