One workflow goes live for a first group. You see whether they keep using it.
The idea works and the shape is settled. Before the whole organisation changes how it works, one workflow goes into production for a defined group, on live matters, with a security review behind it and a lawyer checking what the model writes.
Why adoption is the question a rollout rests on.
A pilot people liked and a product they still open at six on a Friday are different things. Nothing built so far can tell you which one you have. A rollout before that answer commits every team to software nobody has relied on yet.
How it works
We pick one workflow and one group
Narrow enough to finish, complete enough to rely on.
We build it to be maintained
Security review, data handling and an operations runbook, from the first release.
The group works with it on live matters
Their own documents and their own deadlines, with a lawyer reviewing what the model wrote.
We watch what people keep doing
What the group keeps doing tells you more than what it says in the first week.
We recommend and hand over
Scale, rework or stop, in writing. The code and the runbook go to your own team.
What you get
Live software
In production, used by a defined first group on its own work.
Production discipline
Security reviewed, data handling agreed, operations written down.
A recommendation
Scale, rework or stop, with the group's use and feedback behind it.
A handover
Code, documentation and runbook, handed to your own engineers or IT.
Frequently asked questions
Why not buy something off the shelf?
Sometimes you should, and we say so. This is for the workflow no product covers, once the shape is settled and the only question left is whether people keep using it.
Can't our own engineers ship this?
Where they can, they should, and one of ours can join them as an Embedded AI Builder. Where they cannot be spared from the systems nobody may break, we build it and hand it over.
Who runs it once it is live?
Your own team. The code, the documentation and the runbook go to your engineers or IT, and we agree support for the handover before we start.
How long until it is live?
Often three to six months to a first group. It depends on the workflow, the systems it touches and the security review. We size it once the scope is clear.
Is this the finished product?
No. It is narrow on purpose, and it needs looking after. If the group keeps using it, a Custom Application builds what it left out. If not, you stop with the reason in writing.
Should we start here?
Only if the main risk is answered and the shape is settled. If the shape is still open, a Prototype costs less than finding out in production.
More in this track
Tell us which group would work with the first version.
Include what has been tested so far. If the workflow still needs shaping, a Prototype comes before production, and we scope that instead.