Installed is not implemented.
The word that closes projects too early
In many technology projects, "implemented" is the word that closes the project. The system is configured, connected and switched on. The training is done. Someone signs the acceptance form, and the project team moves on.
For an accounting package or a customer relationship management (CRM) system, that can be good enough. The software does what it did in the demo, and people learn their way around it.
An AI platform is different. Its job is to take on work: to read the enquiry, prepare the draft, chase the approval, match the payment to the invoice. On go-live day it has done none of that yet. It has only been given permission to start.
So here is our position: an AI platform is implemented when the work moves through it, and not before. Go-live is the start line.
Why the gap lands on IT
When "implemented" means "switched on", the chief information officer (CIO) inherits the gap. The project is closed and its budget is spent. The company that built the platform has met its milestone. But the business still runs the old way, with the new platform sitting beside it.
Nobody owns the space between the two, so IT does. You now have one more system to secure, license and support, doing little of the work it was bought for. That is how AI joins the list of tools a business pays for and works around.
Three tests for "implemented"
1. It is live in operations. The platform works where the work already happens: where enquiries arrive, where approvals are given, where month-end is prepared. It is connected to the systems that hold the data and to the people who make the decisions. If staff have to leave their normal tools to use it, it sits beside the work, not inside it.
2. It is adopted. People use it on an ordinary Tuesday, not only in launch week. One question tells you most of what you need: if the platform went down for a morning, would anyone notice? If nobody asks where it went, it was never part of the work.
Adoption depends on trust. AI agents should take on more only as they prove themselves, and a person should still approve what matters: money, customers and risk. People rely on a system whose limits they understand.
3. It is measured. Before the build starts, the business agrees what value means in business terms, and records today's baseline. That might be hours spent on a routine task, errors found late, the time from enquiry to first reply, or software spend that could be brought into one place. After go-live, the same measures are read again, in hours and in rand, never in model accuracy scores.
If any of the three is missing, the honest status is "installed".
Someone has to run it
There is a fourth condition, and it explains why implementation never quite ends. A business changes every month. Prices move, a supplier changes its terms, a new product launches, a policy is rewritten. An AI platform that does not change with the business slowly stops being right.
So "implemented" needs an owner after go-live: someone who watches how the platform performs, keeps its knowledge current, adjusts the rules its AI agents work under, and reports value against the baseline. Without that owner, a platform that was implemented in March can quietly become "installed" again by September.
Five questions before you sign off
- Which live processes now run through the platform, and which still run around it?
- Who uses it each week, and what happens when it is unavailable?
- What did we measure before the build, and what does the same measure show now?
- What may the AI agents do on their own, and what still needs a person's approval?
- Who runs the platform from here, and how often do they report on its value?
If the answers are vague, the project is not finished. It has reached the start line.
Build, implement and run
At Futuvara, we build, implement and run AI platforms where AI agents do defined work under rules your business sets.
If your AI platform has gone live but the work has not moved, start a conversation.
