Keeping agents on one platform, so staff aren't confused by silos
Pick one place where agents live and one place where people use them, and make the second one the tools your staff already have open. Silos come from agents living wherever their builder happened to build them.

Why silos happen
Nobody chooses a silo. They appear because the sales assistant got built in the CRM vendor's tool, the finance one in a spreadsheet add-on, the research one in a notebook on someone's laptop, and each was the easiest place for whoever built it. 6 months later your staff have four logins, three sets of rules and no idea which assistant to ask. The ones that are hard to find don't get used, and the confusion gets blamed on the technology.
The two decisions
Where agents live: one place where every agent is built, versioned and kept, that your systems owner controls and your AI lead can see. This is the home that one source of truth depends on. Which product it is doesn't matter much. What matters is that there's one.
Where agents are used: a different question. People should meet the agents inside the tools they've already got open. The quoting assistant turns up in the mailbox or the CRM. The meeting-notes agent turns up in the calendar or the chat tool. If staff have to open a separate portal to use an agent, most of them won't, and the ones who do will have forgotten it exists in a month.
So you're after one home with several doors into it. A silo is what you get when there are several homes.
What "one platform" doesn't mean
It doesn't mean one vendor for everything. It means one place where agents are kept and one way they reach people. You can use one company's assistant for personal productivity and a different company's models underneath the agents, as long as the agents themselves have one home and one front door. The confusion staff feel is about where to go, not about whose model answered.
Name the exceptions
There'll be one or two jobs the platform can't do well and a tool somewhere else that can. Allow it, in writing: this agent lives there, this is why, this is its owner, and it shows up in the same place staff use everything else. An exception with a name and a reason is a decision. An exception nobody wrote down is your first silo.
Moving what's already elsewhere
Most businesses asking this already have agents in three places. The order that works, in our experience:
- List them, with where each one lives and who uses it. Half an afternoon.
- Decide the home and the doors, on a page.
- Move the most-used agent first, and tell its users where it now lives and the date the old one gets switched off.
- Retire the rest one at a time. Anything with no users goes without a move.
What doesn't work is a migration project. It takes a quarter, the old copies stay alive "for safety", and you end up with one more silo than you started with.