Most people picture startups as companies that build something and either grow or fail. A different kind of company has been growing alongside them: the software acquirer. Instead of building, it buys apps and services that already have users, then runs them for the long term with a lean team. If your favourite app or website was bought by one, you may have noticed changes in pricing, support, or ads. Here is how the model works and what it means for customers and sellers.
The basic idea
A software acquirer looks for products with steady revenue and loyal users but slowing growth. Often the original founders are tired, the app needs fresh investment the owners can’t provide, or the parent company is shedding non-core products. The acquirer pays a price, takes over the codebase and brand, and focuses on keeping the product alive and profitable.
The attraction is predictability. A mature app with a million users may have stable subscription income. The acquirer does not need it to explode; it only needs it to earn more than it costs to operate.
How they make money
Acquirers rely on several levers.
- Cost reduction. Merge teams, move infrastructure to cheaper systems, and shut down projects that lose money.
- Pricing changes. Adjust subscription tiers and remove very cheap legacy plans.
- Better monetisation. Add or optimise ads, in-app purchases, and upgrade prompts.
- Retention work. Improve onboarding and support to cut cancellations.
- Shared tools. Apply the same billing, analytics, and marketing systems across the portfolio.
Because the acquirer runs many products, it can spread the cost of such systems widely, which an individual small company cannot.
What changes for users
Customers sometimes see positive changes: more stable service, fixed bugs, and a clear roadmap. They may also see less welcome ones.
- Higher prices or new limits on free tiers.
- More ads or prompts to upgrade.
- Slower development of ambitious new features.
- Support moving to a central team or to automated help.
- Changes to privacy policies and data practices.
When an app you rely on is acquired, read the announcement and the revised terms. Check what happens to your data and whether you can export it.
What changes for employees
A deal often reduces headcount, since overlapping functions are merged. Some engineers stay to maintain the product. Others move to the acquirer’s central teams. Staff in such a deal should ask about retention terms and what the plan is for the team.
Why founders sell
Selling to an acquirer can offer a clean exit. Founders may get paid in cash, and the product continues to serve its users instead of withering. It also removes the pressure to chase venture-style growth. For some owners it is a better outcome than a slow decline.
But they should ask questions: Will the acquirer keep the brand? How will customers be treated? Is part of the payment tied to future performance? Founders who care about their users may negotiate commitments, though these are hard to enforce.
The risks of the model
- Product stagnation. If investment stops, a product can fall behind competitors.
- Customer backlash. Aggressive price increases can drive loyal users away.
- Concentration. A portfolio of ageing products depends on continuing cash flow, which can decline if users leave.
- Reputation. Over time, an acquirer’s name may become a warning sign among users.
How to protect yourself as a user
1. Keep a regular export of your data from any tool you depend on. 2. Avoid long prepayments after an acquisition notice. 3. Watch for changed terms and opt out of new data uses when possible. 4. Keep a shortlist of alternatives. 5. Support the creators you like by paying for good tools while they are independent.
How to evaluate an acquirer as a seller
Ask for references from past sellers, look at how products fared after purchase, and read about how users responded to changes. A buyer who has kept products healthy for years is better than one that cuts and drains.
Bottom line
Software acquirers buy stable apps and run them efficiently, which can extend a product’s life but also change its character. Users should stay alert to pricing and policy shifts, keep their data portable, and have a plan B. Sellers should weigh the price against the future of their product and its customers.
Further reading
Related on this site: Why Software for Plumbers and Electricians Keeps Attracting Funding and Why Big Platforms Buy Small Team-Chat and Collaboration Startups. For general background, see the Wikipedia overview.
