How to plan AI integration before the pilot, not after

The usual sequence is backwards. A team builds a pilot, the demo works, everyone gets excited, and only then does someone ask how it connects to the systems the company runs on. By that point the model has been designed as if it lives alone, and the integration has to be reverse-engineered into a thing that was never built to accept it.

The root cause is almost always the same. The data the AI needs is siloed across systems that were never designed to talk to each other. If you discover that after the pilot, you are not integrating, you are excavating. The right time to find those silos is before a single prompt is written.

Choosing what not to integrate

The most useful planning move is not deciding what to connect. It is deciding what to leave alone. The CEO of a brain-health AI startup made that call out loud. He knew that the richest data lived in enterprise health records, the kind of deep integration that eats years. His decision was to not start there. As he put it, an Epic-type infrastructure “where you have your health care records, we’re not starting with that.”

Instead he began with inputs the product could own directly, wearables and diaries, so the pilot could prove its value without taking on the heaviest integration first. That is planning. He mapped the systems the feature would eventually touch, saw which one would sink the timeline, and deliberately sequenced it for later. The alternative, starting with the deepest integration because it has the best data, is how pilots vanish into a two-year records project and never surface.

He also understood the fragmentation he was routing around. His own description of the problem was a patient filling out the same form “for the millionth time,” then talking to a provider who “haven’t looked at my records yet,” who then has to talk to someone else, and it “gets lost.” He knew that swamp intimately, which is exactly why he chose not to wade into it on day one.

Planning means sequencing, not avoiding

Choosing not to integrate a system in the pilot is not the same as ignoring it. The founder still mapped where the feature had to go eventually, and framed the current version as one piece of a broader ecosystem that would later represent the user to a care provider. The plan named every system, then ordered them by cost and risk. The pilot took the cheapest, highest-signal integration first. The expensive one got a place in the sequence, not a place in the surprise pile.

That is the difference between a plan and a hope. A plan knows the whole map and picks the order. A hope builds the fun part and prays the connections work out.

There is a second benefit to planning integration early, and it is political as much as technical. When you name the two-year records integration up front and schedule it for later, the executive who funded the pilot is not blindsided in month four by a timeline they never agreed to. The hard integration stops being a surprise that reads like failure and becomes a milestone everyone signed off on. Teams that skip this step do not just take on technical risk. They set themselves up to look like they missed something, when in fact the integration was always going to be long. Sequencing it in the open protects both the timeline and the credibility of the people running the pilot.

How we approach it at Density Labs

In the AI Readiness Assessment ($2,500), integration planning comes before the build, not after. We map every system the feature will eventually touch, mark which ones hold data that is siloed and hard to reach, and help sequence the pilot so it proves value on the cheapest integration first. The expensive, multi-year connections get named and scheduled instead of discovered in a panic three months in.

Plan the integration before the pilot and you get to choose your battles. Plan it after and the systems choose for you.