If your SaaS shut down tomorrow, could your business keep running?
The vendors you depend on assume they'll exist forever. Your business plan shouldn't. What "exit insurance" actually requires, in plain terms.
Here’s a question I ask every founder I respect, and it almost always earns a pause: if the tool your business runs on stopped operating tomorrow, how much of your business could you rebuild in a week?
Not a dramatic hypothetical, the way it sounds. SaaS companies shut down all the time. They get acquired and their products get killed; they run out of money quietly; they change strategy and orphan the feature you built your workflow around. None of them plan for it — every dashboard assumes it will be there next Tuesday. That assumption is exactly why the risk exists: it’s shared by everyone, which means nobody prices it into their decisions until it’s too late.
I’ve written about RFQ data as a balance sheet and where export inquiries actually land. This post is about the disaster case those two point toward, and what insurance against it actually requires — because “we care about your data” is not the same thing as “you could leave.”
The three things a business needs to survive a vendor
Strip away the marketing and a business running on a platform needs exactly three things from that platform to be portable:
- The data. Every record that constitutes the business — products, prices, customer history, inquiries, configuration. Not a summary of it; the thing itself.
- The domain. The address your customers use to reach you, and the reputation attached to it. If the domain is a subdomain of the platform, this is not yours, full stop.
- A usable format. Data you can’t actually open and move is data you don’t have. A proprietary blob that only the vendor’s own software reads is a museum, not an export.
Notice what’s not on the list: goodwill, promises, “we’ll always offer an export,” even contractual commitments. Those matter at the margin, but every dead SaaS had them too. What survives a shutdown is never a promise — it’s a file on a drive you control, a domain registered in your name, and a format you can open without the vendor’s help.
Why “we back up your data” misses the point
Platforms love to reassure you that your data is safe — backed up, redundant, replicated across regions. It’s true, and it’s almost entirely beside the point.
The failure mode that ends businesses isn’t a fire in a data center. It’s the vendor deciding, for entirely rational business reasons, that the product you depend on is no longer worth maintaining. At that moment, “your data is backed up” becomes “your data is backed up on our infrastructure, in our format, behind our login, which we are about to turn off.” The backups were never the insurance. The insurance was always the exit: a complete copy of your data, in a standard format, sitting somewhere the vendor can’t reach.
That’s the standard I hold Nodipe to, which is why our docs lead with a one-click data export guide rather than a reassurance page. The export contains the catalog, the media at original resolution, the inquiry history and the configuration — not a curated summary. If you want the reasoning spelled out, that guide explains exactly what an export packages and why a dedicated instance is what makes a complete export possible in the first place.
The honest limits of insurance
Let me be straight about what even good exit insurance cannot do, because this is where the “shut down tomorrow” framing can tip into fear-mongering.
Insurance does not protect you from disruption — only from loss. If a vendor shuts down, you will still have a bad quarter. You’ll migrate, you’ll rebuild workflows, you’ll re-announce your contact details to customers who had the old ones bookmarked. A complete export and an owned domain don’t prevent any of that. What they prevent is the irreversible version: the vendor closing and taking your catalog, your history and your address with them, leaving you to start from zero with no proof you ever had customers at all.
So the question isn’t “can insurance make a shutdown painless?” It can’t. The question is whether a shutdown is a bad quarter or an ending. That difference is decided by two assets — the data in a format you can open, and the domain — and by nothing else.
What this means for how you choose tools
If you take the argument seriously, it changes your purchasing criteria in a useful way. Before you build your business on a new tool, ask four questions of it:
- Can I export everything, not a summary? Ask what’s excluded. The exclusions are the real terms of service.
- Is my address mine? A domain you control is an asset. A subdomain or a profile URL is a lease that expires when they do.
- Is the format open? Standard files you can open anywhere beat a beautiful proprietary export nobody else reads.
- Who is on the other side? A tool run by people you can reach, whose business model doesn’t depend on keeping you in, is a different risk than a tool whose growth relies on your data staying inside its walls.
I have a stake in one answer to these questions, and I’ve said so plainly rather than hiding it. Nodipe’s whole design — a dedicated instance, an owned domain, an export that includes the buyer history other platforms withhold — is the answer to the four questions above. You should weigh that bias against the argument, not ignore it.
The test that never lies
Forget shutdowns for a moment; they’re the dramatic version of a quieter problem. The real test of any vendor relationship is simpler and you can run it this afternoon: export everything today, then imagine never logging in again. If the thought makes you panic about what you’d lose, you’ve found your risk — not in the fine print, but in the one file you can’t seem to download.