1. Skip the hard part: why buy instead of build?
Building an app from scratch is slow and expensive, and most of them never find a single paying user. Buying one skips that part and drops you into something that already has users, revenue, and a product that ships. The catch is that you have to know what you are looking at, or you will pay real money for a lemon.
This guide covers:
- Where to find apps for sale
- How to work out whether they are worth it
- What happens after you buy
- How to sell when you are done
- The mistakes that mark you out as a first-timer
If you are still weighing the two paths, we made the fuller case for acquiring over starting cold in why buying your next online business might make sense.
2. Deal hunting for indie hackers
The best deals tend to come from other indie founders – people building in public, working solo or in small teams, and occasionally ready to move on.
Start with a curated platform. Indiemaker lists indie projects that have been pre-screened for the basics, which is the quickest way to see genuine deals side by side without cold-emailing strangers and hoping. You get context, a paper trail, and a seller who already expects to sell.
From there, two harder routes are worth the effort:
Founder-to-founder deals mean reaching out directly to indie devs whose work you already follow. Cold outreach is the slowest of the lot: spot a solid App Store product that looks neglected but still ranks, and email the owner. Plenty of founders will sell if you catch them at the right moment. The trade-off is real, though – self-sourcing takes more time and legwork, and you carry all the diligence yourself, even if it sometimes means less competition on price.
Whichever route you take, be respectful and straightforward. Nobody sells to the person who opens with a lowball and a lecture.
3. Due diligence or due disaster
Do not fall for a shiny UI and vanity metrics. Dig deeper.
What you need to see before you take anything seriously: at least six months of clean revenue and expense history, an honest read on code quality (if it is a spaghetti mess, pay a developer to audit it), real user retention rather than one-time installs, and whether any marketing funnel exists at all. If there is no funnel, guess who gets to build one.
The warning signs are just as important. A sudden spike in revenue can be ads or bots rather than demand. A seller who will not give you access to analytics is an easy no. Source code written in a dead framework is a problem you inherit on day one.
And be clear on this: retention beats revenue. A high-revenue app with terrible retention is a slow-motion write-off. A low-revenue app with loyal, engaged users is an engine you can tune.
This is the part most first-timers rush. If you want the full method for reading past the demo, we walk through it in how to actually do technical due diligence.
4. From flop to fortune: why failing apps can win
"Failing" does not always mean "useless". Some apps are decent products buried under a bad interface and no marketing. Here is how to spot the potential:
- Are users sticking around despite everything?
- Can you monetise better than the last owner did?
- Is the tech salvageable without a full rebuild?
If you are willing to do the work, these fixer-uppers can pay off. Think of them like distressed property – rough on the outside, cheap to get into, and full of upside for whoever puts in the effort.
5. Congrats, you bought it. Now don't break it.
Your real job starts after the deal closes. Focus here first:
Get a clean handoff. That means source code, databases, App Store and Play Console access, analytics, and documentation, with no excuses accepted. Understand the stack, or pay someone who does. Fix the obvious pain points early – bad onboarding, an ugly interface, no push notifications are all low-hanging upgrades. And talk to users, because they will tell you exactly what works and what does not.
Treat the first 30 days like onboarding a new hire. You are learning its quirks, its strengths, and its bad habits before you change anything.
The handoff is where clean deals quietly go wrong, so get the mechanics right. We covered the whole transfer process – accounts, credentials, and the unglamorous admin that bites you if you skip it – in how to transfer digital assets like a pro. Contracts, IP assignment, and liability sit alongside that, and none of it is legal advice, so get a professional to look over anything you are unsure about.
6. From asset to income: your post-acquisition playbook
Buying the app is only the beginning. Now you turn a lukewarm side project into something that actually earns. Most first-time buyers stop at ownership. The ones who make money keep building.
Stabilise first
Do not sprint into new features or a rebrand. Start with stability:
- Patch bugs.
- Clean up bad UX.
- Fix the glaring performance issues.
Get users to stop bouncing before you do anything else.
Monetise better
Now look at how money flows, or does not. Plenty of apps are under-monetised out of inertia rather than strategy:
- Add a freemium tier.
- Introduce subscriptions.
- Use ads, sparingly.
- Offer one-time unlocks for power users.
If you would not pay for your own app, no one else will either.
Reboot the marketing
The previous owner probably did little marketing, or ran a few bad Facebook ads and called it a day:
- Rebrand if it needs it.
- Redo the App Store and Play Store listing.
- Get proper screenshots, a solid description, and genuine reviews.
- Build a basic SEO landing page.
- Start an email list, or at least some way to talk to users.
Ship your updates and say so publicly. An active app signals value to users and to future buyers.
Build in public (optional, but it works)
Post your updates. Share growth numbers. Ask users for feedback and show the work behind the scenes. It earns you free attention and a reputation that compounds, and in the indie app world that attention converts.
7. Sell like a pro, not a desperate flipper
Apps are assets, and at some point you will want to sell. Timing and preparation decide the price.
Do this first:
- Clean up the code.
- Streamline the costs.
- Get your analytics tidy and consistent.
- Write a playbook for the next owner.
Then price it honestly. Established tools and small apps with a steady track record tend to change hands on a multiple of trailing annual profit – roughly the 3–5x range for a healthy tools business, less if the numbers are thin or the app is young. Price on what the app has actually earned over the past twelve months, not on the hockey-stick forecast you would love to believe. Anything under about six months of history is priced on the value of the asset itself, at a discount rather than on a profit multiple. Buyers see through projected earnings, and pricing on them is the fastest way to kill trust.
Do not just list it and pray. Build the case: why it is a solid buy, who would grow it further, what the next owner inherits. If you are designing for a clean exit from the outset, why you should build to sell your micro-business makes the argument in full.
When you are ready, list it on a curated platform like Indiemaker, where buyers arrive already interested in indie projects. A tidy listing in front of the right audience beats a scattergun post to people who were never going to buy.
8. Rookie moves that will cost you
- Buying on gut instead of data.
- Ignoring hidden costs – Apple's annual developer fee, Google Play's one-off registration fee, server and API bills, and any third-party subscriptions the app depends on.
- Skipping due diligence because the demo looked polished.
- Overpaying on the strength of forecast revenue instead of trailing profit.
- Botching the handoff and losing access to accounts or code.
- Having no plan for the first 90 days once the deal closes.
Avoid those and you are already ahead of most first-time buyers.
Want to go deeper before your first deal? Browse the current listings to see what real apps are selling for, or get the weekly digest for new deals and playbooks as they land.