On August 14, 2026, SpaceX closed a $60 billion acquisition of Anysphere, the company behind Cursor — one of the most widely used AI coding tools, and by most accounts one of the fastest-growing software companies in history. Two weeks later, OpenAI told Cursor it was walking away. OpenAI notified SpaceX that it intends to wind down the contract supplying its models to Cursor, with a shutoff date of November 12, 2026. The reason wasn't a service failure or a missed payment. It was a change-of-control clause: the contract let OpenAI exit if Cursor's ownership changed hands in a way OpenAI didn't like, and OpenAI has said it doesn't trust that SpaceX will use its technology in line with its terms of service.
If you don't write code and have never heard of Cursor, it's tempting to file this under "tech industry drama." That would be a mistake. The mechanism here — a vendor cutting off access to the AI your product runs on, on contractual notice, for reasons that have nothing to do with how well the product works — isn't unique to Cursor. It's a risk sitting quietly underneath a lot of the AI tools small businesses have adopted over the past two years, most of which nobody has ever stopped to think about.
Anysphere wasn't a struggling startup that lost leverage. It was valued in the tens of billions of dollars, growing faster than almost any software company on record, with deep pockets and a sophisticated legal team. And it still couldn't stop its core AI supplier from pulling the plug on about 90 days' notice, over a dispute about who now owns the company — not over anything Cursor itself did wrong.
Scale down from a $60 billion acquisition to the reality of a small business, and the same structural risk is still there, just with far less leverage to negotiate around it. Most SMBs don't have a contract with OpenAI, Anthropic, or Google at all. They have a contract with a CRM, an accounting platform, a scheduling tool, or a customer-service inbox that happens to run an AI feature underneath — and that vendor's relationship with its own model supplier is invisible to you until something changes it.
Most of the AI capability small businesses use today doesn't come from a direct account with an AI lab. It comes bundled inside software you already pay for: an AI drafting feature in your email tool, an AI agent in your accounting software, an AI assistant built into your CRM. Each of those features is a small business (the vendor) that itself depends on a model provider, a hosting arrangement, and a contract that can change. When that underlying arrangement shifts — a price increase, a policy change, an acquisition, a shutoff — the change reaches you as a surprise, because you were never party to the relationship that broke.
This is the flip side of how convenient AI has become. Because these features arrive already integrated, it's easy to treat them as a permanent part of the tool rather than what they actually are: a layered dependency that can be renegotiated, restricted, or removed by parties you have no relationship with.
None of this means avoiding AI tools or over-engineering a small business's tech stack. It means treating AI-dependent tools the way you'd treat any other single point of failure — with a basic continuity habit, not a legal department.
For the two or three AI-powered tools your business genuinely couldn't operate without, ask the vendor directly: which model provider powers this feature, and is it exclusive or swappable on your end? Most vendors will answer a direct question like this, and the answer tells you how exposed you are if that one relationship changes.
If an AI feature drafts your customer replies, generates your invoices, or triages your inbox, make sure the underlying process — the templates, the rules, the logic — also exists somewhere you control, not only inside that one tool's AI layer. That way, if the AI feature disappears or degrades, the workflow keeps running manually or on a different tool while you sort out a replacement.
Export or back up what an AI tool produces for you — customer summaries, generated content, automated reports — on a regular schedule, not just when something breaks. A vendor cutoff rarely deletes your historical data overnight, but access can be interrupted with far less notice than you'd like, and having your own copy means a bad week doesn't become a bad quarter.
Most SMBs never read past the pricing page on a software contract. For any AI tool that becomes core to how you operate, it's worth five minutes to check what happens if the vendor is acquired, discontinues the AI feature, or changes its underlying model provider. You're not trying to predict the future — you're trying to know your notice period if it happens.
Pick the single AI tool your business would feel the most pain from losing with 90 days' notice. Spend fifteen minutes writing down what you'd do: which alternative tool you'd trial first, what would revert to manual, who on your team would own the transition. You don't need this plan for every tool you use — just the one or two that would actually hurt.
The OpenAI-Cursor story is a useful jolt precisely because it happened to a company with every advantage a small business doesn't have — money, lawyers, and leverage — and it still couldn't prevent a 90-day notice to rebuild a core dependency. That's not a reason to slow down AI adoption; the productivity gains are real and worth pursuing. It's a reason to treat "which AI tools would hurt if they disappeared" as a question worth answering once, in a calm moment, rather than for the first time during a scramble.
DAOVA helps small businesses build practical AI governance that accounts for vendor and continuity risk, not just data security. Explore AI Governance & Operations.