This is not a hypothetical
The AI tools market is early, crowded and funded by investors expecting consolidation. Products are acquired and shut down, free tiers are withdrawn, and prices rise sharply once a product is embedded. None of this is misconduct; it is what an immature market does.
For a small business the practical question is not whether one of your tools will go away, but which one, and what happens that morning.
Four ways it goes away
Shutdown. Usually thirty to ninety days’ notice, sometimes less. Your data is exportable during that window and not afterwards.
Acquisition. The product continues, the terms change, often including where data is processed and who the sub-processors are. The email describing this will be about an exciting new chapter.
Repricing. The most common. A tool at USD 15 becomes USD 49, or the feature you use moves to a higher tier. The vendor knows exactly how embedded you are.
Degradation. Nothing is announced. The model underneath is swapped for a cheaper one, limits tighten, quality drops. From the logging lesson, this is the failure you can only detect if you kept records.
The test worth applying before you depend on anything
How long would it take to work without this?
Under a day: fine, depend on it freely. This is most chat and drafting tools; you can move to another tomorrow because the thing you built was a prompt, and prompts travel.
A week: acceptable with an export in hand.
A month or more: you have a dependency, not a subscription, and it needs managing.
The costly dependencies are rarely the model. They are the tools holding your accumulated material: your customer conversations, your document library, your automations, your configuration.
Export monthly, and check the file
Schedule an export of anything holding your business’s material: customers, conversations, documents, automation configuration, prompt library.
Then do the part people skip: open it. A CSV you can read is an export. A proprietary archive that only the vendor’s own product can open is a backup of your lock-in. The month to discover which you have is not the month the product closes.
Storing the files costs nothing. Twenty minutes a month, or a scheduled job if the platform allows it.
Reduce lock-in where it is free to do so
Keep prompts in your own file, not only inside the product. They transfer to any tool.
Prefer tools that let you supply your own model key. Then a vendor’s pricing change does not strand you.
Keep your documents in your own storage, with the AI tool reading them, rather than uploading your only copy into somebody’s product.
Write down what each automation does in plain words. Rebuilding from a description takes an afternoon; rebuilding from memory takes a fortnight.
None of these costs anything at the time. All of them are expensive to do retrospectively, which is the pattern in this whole module.
The thirty-day drill
Once, for your most embedded tool, spend an hour answering the question as though the email had already arrived.
Where is the data, how do I get it out, what format is it in, what would I move to, and how long would the move take? Write the five answers down.
Most people find one of two things. Either the answer is comfortable, in which case the worry can be put down permanently. Or there is one step nobody can answer (usually the export format or where the configuration lives) and that step is now a twenty-minute job rather than a crisis.
This is the same discipline as knowing where the off switch is, from module six. Practised once, in a calm week, it costs an hour and removes an entire category of bad month.
Judging a vendor’s durability
You cannot assess a startup’s finances, and two cheap signals help. How long have they existed, and are they charging money: a product with no revenue model is being funded by someone who will eventually want one. And can you get your data out today, without asking. A product that makes export easy is one that expects you to stay because it is good.
The reasonable posture
Use new tools. The capability is real and the cost of waiting is also real.
Just do not build your business’s memory inside one. Your customer records, your documents and your written knowledge live in your own storage, and the AI tool is something that reads them, replaceable in a week, which is where you want every one of them to be.
Every lesson here is open. Your progress is recorded once you pass the AI at Work exam.
Check your understanding
A firm uses an AI document tool that stores its uploaded contracts and answers questions about them. The vendor announces a shutdown in sixty days. Which preparation would have most reduced the disruption?
Pick the one you would defend. Your answer stays private.
Stuck on something?Ask Yetunde, your AI tutor