The product you bought has a shipping schedule now
For most of software history, the thing you signed a contract for was the thing you got. This month is a useful illustration of why that assumption no longer holds. OpenAI's Codex team announced 28 consecutive days of shipping: every single day bringing either a clear improvement for users "or a full reset." Prediction features landed on day five. A 500,000-token context window arrived on day seven. The other major labs spent the same stretch shipping their own waves of new models and features.
Vendors frame this as a gift, and often it is. Read it as a buyer and it says something else: the product you evaluate during a trial is not the product you'll be running at renewal. Classic SaaS shipped a few times a year, with release notes and migration windows. AI tools change the model underneath, the usage limits, and sometimes the price — weekly, by design, with the vendor explicitly reserving the right to "reset."
The standard small-business response is a shrug: tech moves fast, nothing to be done. The shrug is where the money leaks. When the product can change monthly, the only stable thing in the relationship is the contract — and the only term that protects you from a change you didn't choose is the exit clause. It's the one term written for the world the vendor is describing out loud.
The exit-clause checklist
Run this before signing anything new, and bring it to every renewal — the renewal is where you have actual leverage. Five items.
1. Data export in a usable format — tested, not promised
Nearly every tool says "you can export your data." What matters is what that means: machine-readable CSV or JSON, covering your inputs, uploaded documents, generated outputs, and your custom instructions or workflows — not a PDF of your settings page. Then test the export during the trial, not during the breakup. Create three records, hit export, open the file. If export is ugly while things are good, it will be worse while things are bad.
2. A post-termination access window, in writing
Standard terms across the market give you anywhere from zero to 90 days to retrieve your data after cancellation — and that range is real, not theoretical. What good looks like: export stays available for at least 30 days after termination, nothing gets deleted inside that window, and retrieval isn't charged. If the standard terms don't say it, ask before you sign. If the answer is "call support," you've just learned what your data's exit looks like.
3. Notice and a remedy when the product changes mid-term
The AI-specific term, and the one almost nobody asks about. Two questions: how much notice do you get when the underlying model, price, or usage limits change — and what's the remedy if a feature you pay for is removed or degraded mid-term? Reasonable asks: advance notice of material changes, plus a downgrade-or-exit right — a pro-rated refund or penalty-free cancellation — if a change takes away what you signed up for. A vendor willing to "reset" the product on any given Tuesday should be able to answer that in one sentence. Vague silence tells you who eats the risk.
4. Every access point, and a way to revoke them
An AI subscription is rarely one login. It's OAuth grants to your Google or Microsoft account, API keys your automations run on, browser extensions, connected integrations, sub-agents with their own permissions. Each one is a door that stays open after you cancel. Ask for documentation of every access the tool takes and a revocation path for each — then make "revoke all access" a named step in your offboarding. A cancelled subscription with live credentials is a security hole and a recurring charge waiting to be rediscovered.
5. What the tool learned — yours and portable
If the assistant holds your custom instructions, learned workflows, and memory, the expensive part of leaving isn't the records — it's the context. Ask whether prompts, configurations, and memory export. If they don't, run the discipline that makes the question moot: write your processes in your own files and let the tool read them. Then an exit never costs you the knowledge, and the answer to "who owns the workflow" stops mattering.
The honest boundary
Custom contract terms need leverage, and leverage needs spend. Nobody is redlining your exit rights on a $30-a-month self-serve plan, and a checklist that pretends otherwise wastes your evening. At the low end, this list is a verification list: read the standard terms before you adopt, score the tool on the five items, and walk away from the ones that fail. The moment you're signing anything annual, per-seat, or four figures — that's when you send the list and expect written answers.
The 10-minute quarterly review
For tools already in your stack, the contract moment has passed — so the discipline shifts to a review. Once a quarter, per tool, ten minutes, five questions:
- Still the right tool? Knowing what you know now, would you adopt this today?
- What changed since last quarter — price, limits, model, features? Which of those changes did you actually choose?
- Does the export still work? Run it. Export formats change more often than contracts do.
- What access does it hold right now? List the integrations and keys. Revoke the dead ones.
- When is renewal, and what would leaving cost? Do the exit math before the auto-charge does it for you.
Question three is the one everyone skips and the one that saves the most grief — it converts "I think we could export if we needed to" into a fact you checked this quarter.
What not to do
- Don't sign multi-year AI contracts right now — not even for the discount. The discount is priced for a stability this market no longer sells. Annual at most, and only where the checklist passes.
- Don't confuse exporting data with exporting the workflow. Records are the easy part. Instructions, memory, and learned context are what actually trap you.
- Don't read the terms for the first time when you're unhappy. The exit clause is worth the most on the day you're happiest — that's the day the vendor still has to compete for you.
One line to keep
In the last era of software, stability was part of what you bought. In this one, the change rate is the product. The exit clause is the only term that prices that honestly — so read it first, test it first, and negotiate it first.
If you want the full framework for making any agent earn its seat — the permission ladder, the boring first assignment, and the one-page process format that keeps your context portable and your exits cheap — it's all written down in The AI Agent Owner's Playbook. $49 CAD, instant download.
Top comments (0)