AI Solutions · Implementation & Change
The rollout decides whether any of it works.
A new system the team routes around is worse than the old one.
We manage the implementation itself: configuration, data migration, training, and the change management that gets people using it. This applies whether the fix was bought, built, or was already in the building and never switched on.
When this is the right answer
When the rollout is the risk.
- A system was chosen but the rollout keeps slipping.
- A previous rollout stalled and the team went back to spreadsheets.
- The business is moving off a legacy system and the data is messy.
- Several teams need to change how they work at once.
These rollouts need more than configuration. They need a plan with clear responsibilities, data checked before it moves, and people who understand what changes in their work. We coordinate those parts together, from the first readiness check through to the 90 day review.
The method
Prepare. Roll out. Measure.
Prepare
Check readiness and set a plan with dates the business can hold.
- Readiness check and data audit
- Who is affected, and how
- Dated implementation plan
More detail
We start by testing whether the business is ready, then audit the data that will move across. We list every person the change touches and what changes for them. The plan names owners and dates. We set those dates with you, against the real calendar, including leave, busy periods and vendor availability, so the business can hold them. Nothing moves to the next step until the plan is agreed in writing by the people who will carry it out.
Roll out
Configure, migrate, train and go live in stages.
- Configuration to the agreed requirements
- Data migration with checks
- One team first, then the rest
More detail
We configure the system to the requirements already agreed, then migrate the data and check it against the source. Training is written and delivered to each role, using your own work. Go live happens in stages. One team goes first, we review what they find, and then the next team follows when ready. That first group tests the process before it reaches everyone. We agree who handles questions in the first weeks and track issues with an owner and priority for each.
Measure
Compare before and after, then adjust. Reviews at 30 and 90 days.
- Before and after on key workflows
- Adjustments from real use
- 30 and 90 day reviews
More detail
Before anything changes, we record how the workflows that mattered run today. After go live, we measure the same things again and compare. What we find feeds adjustments to configuration, training or process. We then sit down with you at 30 days and again at 90 days to review use, remaining problems and what to change next. Each review ends with a short written note of what was found and what was agreed.
What you get
Set up, taught and measured.
- Implementation plan
- Data migration
- System configuration
- Training sessions and written guides
- Before and after measurement
- 30 and 90 day reviews
Why a project manager runs this
Ten years of rollouts in government.
Ethan Sandery spent ten years leading digital transformation in South Australian government, including as project management coordinator at the state work health and safety regulator. He ran a Microsoft Copilot rollout across a 200-person agency, and delivered digital licensing improvements that had to work for the public on day one. He was a Premier's Excellence Award finalist in 2024 and holds a Diploma of Project Management. The discipline is the same for a business of 10 to 50 people: clear scope, honest dates, trained users and a check on whether it worked. We bring that same approach to your rollout.
Working with your vendor
Your side of the table.
We sit on your side of the table. We brief the vendor, keep the plan in front of them and translate between their terms and yours, so you do not have to learn the vendor's language. Scope is written down, so each party knows what it is responsible for, and we raise slips early and coordinate the fix. The vendor remains responsible for its own product and delivery commitments. We coordinate them against the plan on your behalf, and report back to you plainly.
Questions about Implementation & Change
Do you implement software you did not choose?
Yes. It can be something you bought, something built for you, or a tool you already own that was never switched on. We start with the readiness check.
What if our data is messy?
The data audit comes first. We find the gaps and duplicates, agree with you what gets cleaned, and check the migrated data against the source before anyone relies on it.
Do you train the whole team?
Yes. Training is by role, run as sessions, and backed by written guides the team can keep using after we leave. Newcomers can use the same guides when they join later.
What happens after go live?
We measure the workflows we recorded before, adjust from what we see, and review with you at 30 and 90 days.