Every operation already has a system of record. It is usually old, partially documented, and load-bearing in ways nobody fully remembers. The instinct, especially among vendors, is to treat that system as the obstacle: migrate first, modernise first, then do the AI. We have watched that sequencing kill more AI initiatives than any model limitation ever has. The migration becomes the project. The AI becomes a line item in year two of a plan that does not survive year one.
The alternative is to treat the existing stack as the substrate, not the obstacle. AI systems are unusually good at sitting on top of things: they read from the CRM without replacing it, draft into the inbox without owning it, reconcile against the ERP without touching its schema. The integration surface (APIs, webhooks, exports, even structured email) is almost always richer than teams assume. When we scoped the Meta Ads integration for our own ad platform, the answer was not a new ads manager; it was a tool server exposing thirty-four operations over the API the team already used. The workflow changed. The system of record did not.
Working this way changes what an integration is. It stops being plumbing and becomes the product decision: which systems does the AI read from, which does it write to, and which does it only ever draft into with a human pressing send. In our video pipeline, the connective tissue is exactly this: Slack for approvals across seven channels, Drive and Sheets and Docs for the assets and the records, the ad platform for delivery. None of those tools were replaced. All of them became more valuable, because the work now flows through them instead of around them.
There is a governance dividend too. When the AI layers over the stack, every action it takes lands in systems the organisation already audits, already backs up, already controls access to. Rip-and-replace resets all of that to zero and asks the company to re-trust a new vendor with everything at once. Layering asks for trust in increments, which is the only way operational trust is actually granted.
If a proposal starts with a migration, it is not an AI proposal: it is an infrastructure proposal wearing a costume.
The rule we hold: the AI adapts to the operation, not the other way round. If a proposal starts with a migration, it is not an AI proposal: it is an infrastructure proposal wearing a costume. There are moments when replacing a system is right. But that decision should be made on its own merits, on its own timeline, and never as the toll a company has to pay before the useful work is allowed to start.