Nobody migrates a ledger.
Most groups have a story about a supplier who took six months, needed a project team, and never quite delivered. That is the fear worth answering before anything else — so here is exactly what happens, and exactly what we need from you.
Five stages. You control the last two.
Connect
We connect to your DMS and the UK data sources, and provision your group's node — a dedicated database and network boundary. Read-only to begin with. Your system of record is not touched.
What we need from youAn introduction to whoever manages your DMS relationship.
Load
Customer, vehicle and job-card history flows into the shared record. Your existing opt-out lists are reconciled into one consent ledger — usually the first time a group sees them in one place.
What we need from youConfirm which of your existing opt-out lists is authoritative.
Review
Every outbound template — voice script, text and email — is written, shown to you, and signed off before anything is capable of sending. Nothing goes to a customer on our judgement alone.
What we need from youSomeone to approve wording. Usually marketing, plus compliance.
Supervised launch
Modules start with a human on the loop. It drafts and your advisor sends, or it acts and your team supervises exceptions. You watch it work on your own customers before it works alone.
What we need from youCorrect it where it is wrong. That feedback is the tuning.
Step up
Autonomy increases module by module as confidence grows. Entirely your decision, reversible at any point, and never a switch we flip on your behalf.
What we need from youDecide when — and tell us to step back down if you change your mind.
Asked plainly, answered plainly.
Are we migrating anything?
No. Your DMS stays exactly where it is and remains your system of record. There is no cutover weekend, no data migration project, and no moment where the business runs on nothing.
What if it does not work?
You will know early, because it starts supervised on your own data with a human reading everything before it sends. Nothing is switched off until whatever replaces it has proved itself.
How much of our team's time does this take?
An introduction to your DMS contact, someone to sign off wording, and whatever time you choose to spend correcting it in the first weeks. We do not need a project team.
What happens to the suppliers we already pay?
Nothing, until you want it to. Modules go live alongside them, and you retire a supplier when its replacement has proved out — not on our timetable, and not on faith.
Nothing turns off until its replacement has proved itself.
That is the whole implementation philosophy. You are never between two systems, never dependent on something unproven, and never asked to take a supplier's word for it. If a module cannot earn its place against what you already run, it should not be there.
One module. Your own data.
Most groups start in the workshop with declined work, because it is measurable within weeks and needs nothing switched off to prove it.