Rescue Software: Making Money From the Products Everyone Else Abandoned

Software companies kill products all the time. Roadmaps get “consolidated,” features get “sunset,” and somewhere a product manager writes a cheerful blog post about focusing on what matters. Here’s what those posts never mention: the users don’t disappear, and neither do their files. Millions of documents, project plans, message histories, and integrations keep existing after the product that created them is gone. Someone has to open those files, export that data, or replace that workflow, and the company that caused the problem has explicitly announced it won’t be helping.

We’ve started calling this category rescue software, and the opportunity data we track keeps surfacing it. Four separate concepts in this vein showed up in both of our research pipelines independently, which almost never happens. Each one targets a different corporate abandonment, and together they sketch out a repeatable business model: build the small paid utility that does the one thing the dead product’s users desperately need.

Why dead products leave live customers

The economics are almost unfair. When a big company deprecates something, it does your marketing for you: every affected user gets an email telling them they have a problem and a deadline. The company won’t build the fix, because the whole point of killing the product was to stop spending money on it. Big competitors won’t build it either, because a migration tool for a discontinued product looks like a small, shrinking market on a spreadsheet. But it doesn’t shrink the way spreadsheets predict. Files outlive software by decades, and stragglers keep discovering the problem years after the shutdown, usually at the worst possible moment, which is exactly when people pay for software without comparison shopping.

Here are the four concepts from our tracking, each a live example of the pattern.

The Microsoft Publisher file opener

Microsoft discontinued Publisher, its desktop publishing app, and offered no real successor. But Publisher was the default tool for a generation of church newsletters, school flyers, small-business menus, and community group posters. There are decades of .pub files sitting on hard drives, and the number of programs that can open the format properly rounds to zero. A clean tool that opens a .pub file and converts it to PDF, Word, or an editable modern format solves an urgent, recurring problem. The person who needs it isn’t a designer; it’s a volunteer who inherited the newsletter file from someone who retired. They’ll pay $15 to 30 once, or a few dollars per conversion, and they’ll find you through one search: “how to open pub file.”

The MS Project Online exit kit

Microsoft is retiring Project Online, stranding organizations that ran years of project portfolios through it. Microsoft’s suggested path is its newer planning products, which don’t map cleanly, and the users affected are project managers at companies too small to fund a consulting engagement. The rescue play here has two parts: an export tool that pulls plans, tasks, resources, and history out intact, and a lightweight planner that can actually open what was exported. This is the priciest example of the four, because the buyers are businesses with budgets and deadlines. An exit kit at $200 to 500 per organization, or a modest subscription for the planner, is an easy purchase against the alternative of losing ten years of project history.

The Samsung Messages escape hatch

Samsung has been pushing users from its own Messages app to Google Messages, and phone upgrades force the issue. What Samsung didn’t build is a serious way to carry years of short message service (SMS) history along, and text messages are some of the most sentimental data people own: conversations with parents who’ve passed, the thread where a relationship started, records people need for court or work. A tool that backs up, exports to readable formats, and migrates message history cleanly sells itself in phone-store parking lots. Consumer pricing, $10 to 20, huge volume, and every phone upgrade cycle refreshes the audience.

The self-hosted GIF picker

When Google shut down the Tenor application programming interface (API) tiers that thousands of apps and communities relied on for Graphics Interchange Format (GIF) search, every chat app, forum, and Discord-adjacent tool that had embedded a GIF picker suddenly had a broken feature. The rescue here is developer-facing: a self-hosted GIF search and picker component that product teams can drop in without depending on anyone’s API surviving. Developers are the easiest rescue customers of all, because they’ve just been burned by a dependency and are actively shopping for one they control. A licensed component or a small hosted service at $10 to 50 a month per project fits how dev teams already buy.

How to spot the next one

The beautiful thing about this category is that the leads are published in advance. Deprecation announcements are public roadmaps for rescue software. Microsoft, Google, Atlassian, and Salesforce all maintain official deprecation pages and send end-of-life notices months or years ahead. Subscribe to them the way an investor reads earnings calls. When an announcement drops, ask three questions. Does the dying product hold data users will still need afterward, in files, exports, or histories? Is the official migration path missing, ugly, or suspiciously convenient for the vendor? And are the affected users individuals and small teams rather than enterprises with information technology (IT) departments who’ll handle it internally?

Three yeses means you’ve found a candidate. Then check the panic signal: search forums, Reddit, and the product’s own community pages for people asking what to do. If the same desperate question appears twenty times with no good answer, the market research is done. You didn’t have to guess whether people want it; they’re publicly begging for it. Build the smallest version that answers the question, put a price on it, and put it where the search traffic already lands.

The honest downsides

We’ll be honest about what makes rescue software unglamorous. First, the ceiling: each individual rescue is a product, not a platform, and most will top out somewhere between side income and a modest full-time living. You get bigger by stacking rescues, not by scaling one. Second, some of these are technically nasty. Reverse-engineering a proprietary format like .pub is real work, and getting message data off a locked-down phone involves platform restrictions that shift under you. Third, timing cuts both ways: arrive too early and users are still hoping the vendor changes its mind, too late and a free open-source script may have soaked up the demand.

Who this isn’t for: anyone who needs their product to be impressive at parties, anyone unwilling to grind through format documentation and edge cases, and anyone who wants one product they can ride for a decade. Rescue software rewards a different temperament, the person who reads a shutdown announcement and sees a customer list with a deadline attached.

The deprecations won’t stop. If anything, the current era of companies pruning products to fund artificial intelligence (AI) initiatives is producing more abandonments per year than any period we can remember tracking. Every one of them leaves users holding data they can’t open and workflows that no longer work. Somebody small and unsentimental gets paid to catch them.