Four days ago, Apple filed a federal lawsuit against OpenAI in Northern California court. Not a cease-and-desist. A full lawsuit alleging that OpenAI "at every level" coordinated the theft of Apple's trade secrets — hardware designs, manufacturing processes, supplier relationships.
The details are striking. OpenAI's hardware chief, Tang Tan — a former Apple VP — allegedly ran "show and tell" sessions where job candidates were told to bring physical Apple parts to their interviews. One former Apple engineer was accused of downloading confidential documents onto an Apple-issued laptop, then walking out the door to start at OpenAI.
You might read this and think: rich tech companies fighting over hardware blueprints, not my problem. But there's something underneath this story that small organizations need to understand right now.
The partnership that just blew up was built into your phone
In 2024, Apple and OpenAI announced something unusual: ChatGPT integrated directly into iOS 18. Siri could hand off queries to ChatGPT. Apple Intelligence could use it to draft emails, rewrite documents, summarize web content. Visual Intelligence let you point your camera at something and get a ChatGPT analysis.
It was baked into the operating system most of your team already carries in their pockets.
Since then, a lot of small organizations have quietly started depending on it. Not because they made a deliberate infrastructure decision — because the features were just there, on the device everyone owned, and they worked well enough.
Summarize that 40-email thread? Apple Intelligence. Draft a reply to a difficult grant officer? ChatGPT via Siri. Rewrite meeting notes in plain English? Right there in the Notes app.
That foundation is now shaky in ways you probably didn't plan for.
What actually happens when platform partnerships collapse
The relationship was already fracturing before this lawsuit. OpenAI had been complaining for months that Apple buried the ChatGPT features, making them hard to find, and that revenue from the integration was nowhere near projections. As of May, OpenAI was preparing its own legal action against Apple over the Siri deal. Apple filed first.
Two companies in active federal litigation do not coordinate on product integrations. Feature development stops. Engineers get pulled into legal reviews. Support deprioritizes. Eventually, one side pulls out — or a court forces a change.
The specific worst case: a court orders OpenAI to suspend its integrations with Apple products pending the lawsuit. It's not the likeliest outcome, but it's not theoretical either. Apple's complaint specifically targets the consumer hardware OpenAI is building after spending $6.4 billion to acquire Jony Ive's IO Products startup. The stakes are high enough that aggressive legal remedies are very much on the table.
Even short of that: any workflow your team depends on that routes through Apple Intelligence into ChatGPT now depends on a legal agreement that's actively contested in federal court. That's a fragile dependency you probably didn't think you were signing up for when you asked Siri to help write an email.
The real lesson here isn't about Apple or OpenAI
This is a pattern. Platform partnerships between large companies get announced with fanfare, get built into products that millions of small orgs start using, and then the business interests diverge. One side gets sued or pivots or pulls out. The small org has no voice in the outcome.
We've seen it with Twitter API shutdowns killing nonprofit monitoring tools overnight. We've seen it with Google deprecating Workspace features that hundreds of automation workflows relied on. The Apple-OpenAI split is the same dynamic at a different scale.
The teams that don't get hurt when these things happen are the ones who built at the application layer, not the platform layer. They connected to AI capabilities directly — via API calls, via tools they control, via workflows they own — rather than depending on a vendor's baked-in integration that can evaporate.
What to do in the next two weeks
Start with an audit. Which of your team's AI-assisted tasks rely on Apple Intelligence features or the Siri-ChatGPT handoff? Actually list them.
For each one: do you have an alternative that doesn't depend on the Apple-OpenAI partnership? If not, build one now.
Most of these workflows are easy to replace at the application layer. Email drafting works fine through a direct ChatGPT subscription or a local tool in your browser. Document summarization has half a dozen solid options that have zero exposure to Apple's litigation. Meeting transcription and summarization doesn't need to live in the Notes app.
None of this needs to happen this week. But doing the audit now — knowing where you're exposed — means you're not scrambling the day a court order or a product decision changes what your phone can do.
The posture shift that actually protects you
Treat any AI feature that lives inside a platform as temporary convenience, not infrastructure. Use it while it's there. Don't build critical processes on top of it.
The Apple Intelligence suite still works today. The ChatGPT-Siri integration still works today. But you should know which pieces of your team's workflow depend on a legal agreement between two companies that are currently suing each other in federal court.
By the time this makes mainstream business news, the alternatives will cost more to scramble for. Mapping your exposure now costs nothing.
This is exactly the kind of thing we walk teams through in a sprint — finding where AI dependencies actually live in your operations versus where you think they live. They don't always match.