AI RolloutTrack
Rules first, then your first team live.
Track is our AI rollout service and runs as two phases in a fixed order.
- Govern agrees the rules and who can reach what.
- Adopt brings your first team into daily use, and closes with a test on your own work.
We agree one fixed price up front and work inside the guardrails you set. Widening beyond that first team is a separate decision, taken after a permissions review.
Certified in the Claude Partner Network Microsoft Solutions Partner ISO 27001 ISO 9001 Independent since 1999
Two phases in a fixed order
Adopt starts only once Govern has set the rules and sign-in is under your company account.
Govern
Before anything goes live, we agree the rules and who can reach what.
We start by finding the AI tools your people already use, including personal accounts on your company email, and what those tools can reach. Then your leadership sets the policy in a half-day workshop and we agree the data guardrails. We also bring sign-in under your company account, so nobody can set up their own AI account on your domain.
You receive: a picture of where you stand, a written AI policy your people will follow and an approved tool register your team can point to.
Involved: whoever owns technology decisions on your side, and the Cardonet engineer who runs your onboarding.
Adopt
Your first team connected and in daily use, sounding like you, closed with a test on your own work.
We connect AI to your Microsoft 365 or Google Workspace for a named first team that is usually your leadership team. Then we build your company voice into it (the vocabulary, the tone, the lines nobody should cross) so that work comes back usable the first time. Track ends with a test we run on the work your first team does.
You receive: your first team connected and working, a company voice guide and the result of a test on your team's own work, which closes the phase.
Involved: your first team, in the roles that will use AI day to day, and the Cardonet engineer who connects them.
The boundary
What Track is not
Track does not replace your IT team or take over infrastructure you already run. It sets the rules for how AI gets used inside what you already have, and works alongside whoever manages that today.
Your IT lead stays the technical owner and the escalation point, while we add capacity and take the governance workload. Most IT teams already know AI is in use on accounts they do not manage, and Track gives them the time and the agreed rules to deal with it.
Permissions review
Nothing widens until someone checks
Three ways through it, from a signed waiver for your first team to a full review for the whole business.
Permissions review
We check who can see what before anyone's access grows.
A connected AI tool can open anything its user's account can when asked, and no setting narrows that. So the connected group is the only boundary that holds, which is why we check it before it grows and never skip the check to meet a deadline.
There are three ways through it. Your first team connects under a signed waiver that names them and caps its size. Widening to a defined team takes a review of that team's permissions. Rolling out across the business takes a full review of who can reach what. The waiver records an informed decision, although it does not count as an approval and does not cover anything we already know to be wrong.
Guardrails run through the whole route
Governance carries on past Govern and after Track ends. It stays active through Adopt, through everything Build connects to the tools you already run and through Trackside, the monthly service that starts once you are live. We check it at every step.
If Adopt would ever break a guardrail that Govern set, it does not proceed until that is resolved. The same rule holds for whatever Build or Trackside add later.
Commercials
How this is scoped
Track is one fixed price, Build is quoted per piece and Trackside is ongoing.
- Track One fixed price covering both phases, agreed before you start, with the outputs of each phase named. The term is set in your proposal.
- Build Quoted per piece of work once Discover, the first step of Build, has ranked what is worth building. It is never folded into Track's price, and you can stop after any one piece.
- Trackside A monthly service at a depth set for your business. The fair-use limits and how it is bought are both set in your proposal.
How this is scoped, in full, including what is not included →
Common questions
Before you commit
How do we know you are any good at AI when you are an IT company?
Ask us for process rather than claims. We are certified to ISO 27001 and ISO 9001, independent since 1999, with 98% customer satisfaction and 98% SLA achievement.
AI adoption fails on governance, data handling, access and change management. Those are not new disciplines and they are the ones we run daily. Nobody has a decade of AI delivery behind them, because the tools are not a decade old. We have been through this inside our own business, and we are running it now with existing clients. What we can evidence is on the Proof page.
Should we just wait until this settles down?
Waiting is a choice with a cost, because the use is already happening without oversight. Choosing to wait leaves the use running and removes your view of it.
The controls that matter are classification, access, logging, review and training, and none of them has changed much in decades.
We already have Copilot or Gemini. Is Track still relevant?
Yes. Having the tool answers the tool question, while the harder ones come next: what your people are allowed to put into it, what the connected accounts can already reach, how you evidence that to a client and whether anyone is measuring the value.
Is this another pilot?
No. A pilot usually has no owner, no measurement and no training, which is why most of them fade after a busy quarter. Adopt has all three, and it closes with a test on the work your first team does. Trackside then carries on from the day your first team is live.
Why only a first team? We have 200 people.
Because the connected group is the only boundary that holds, a capped first team is the only defensible way to start. Widening then happens team by team through a permissions review rather than to a rollout schedule.
What do you need from us?
Only one half-day of leadership time for the policy workshop, a questionnaire and engineer access, followed by your first team, in the roles that will use AI day to day.
How long does it take?
We will give you a date in the scoping conversation. The answer depends on how quickly your leadership team can get in a room.
For your board pack
Forward this
The whole of Track in one block you can paste into an email or a board pack.
Govern
We find what is already in use, agree the rules and bring sign-in under your company account.
Adopt
Your first team connected and sounding like you, closed with a test on your own work.
The download prints this block on its own. Choose "Save as PDF" when your browser's print options open.