Assess. Prove. Then plan.
Most data methodologies are a sequence of phases with a business case at the front. Ours puts the evidence at the front, because the business case written before the evidence is a guess with a spreadsheet attached.
You can stop after any one of them and still be better off.
Each stage produces something that stands on its own. Nothing is engineered so that stopping early wastes what you've already paid for.
Establish ground truth
Stakeholder interviews, system walkthroughs, and profiling run against real extracts. We don't score you off a questionnaire — questionnaires measure what people believe, and the gap between belief and data is usually the finding.
Weeks 1–3Take the quick wins
Every assessment surfaces two or three fixes worth doing straight away — a duplicate rule, a broken feed, a field nobody has owned since 2019. We do those while the plan is being agreed.
First 30 daysRun the six-month plan
Sequenced by data domain, with a named deliverable every month and a formal checkpoint at month three where you can redirect or stop.
Months 1–6Hand it over
Runbooks, documentation, training, and a period of supported operation where your team drives and we watch. Ongoing support is a separate decision you make afterwards, not a dependency we designed in.
CloseoutWhere you are, per domain.
The same four states apply to every data domain, and the sequence you move them in is a real decision. Fixing product master data before customer master data can be exactly right — or exactly wrong — depending on which one your revenue runs through.
Unknown
No agreed inventory of what holds the data. Different teams give different answers, and no answer is provably current. Any roadmap written here is fiction.
Mapped
Systems, flows and dependencies are documented and agreed. You know where the data lives and how it moves. Nobody is yet accountable for its condition.
Owned
Every domain has a named steward with the authority to decide. Issues have somewhere to escalate to, and definitions have someone who can settle them.
Governed
Policy is enforced by controls rather than goodwill. Quality is measured continuously, exceptions are worked, and drift is visible before it reaches a report.
Most organisations that describe themselves as governed are at Mapped, with a policy document nobody has read since it was approved. That's not an insult — it's the ordinary result of buying the framework before establishing the inventory.
Long enough to change something. Short enough to still be true.
Multi-year data programs fail for an unglamorous reason: the organisation they were designed for stops existing. A restructure, an acquisition, a new finance system, a sponsor who leaves — and month nineteen of a thirty-month plan is now solving a problem the business no longer has.
Six months is roughly the horizon over which an enterprise environment stays stable enough to plan against honestly. It's also short enough that a sponsor can see the whole thing through and be held to the outcome.
If your problem genuinely needs two years, we'll tell you — and then we'll cut it into four blocks, each of which is worth having on its own.
- Month 1
- Quick wins live
- Month 2
- First domain modelled
- Month 3
- Match & merge in test · checkpoint
- Month 4
- Stewardship running
- Month 5
- Downstream consumers cut over
- Month 6
- Handover & measurement
Indicative only. The real sequence comes out of your assessment.
The awkward ones, answered.
What if the assessment says our current program is wrong?+
Do we have to use your software?+
Can you work alongside our existing systems integrator?+
What do you need from our team?+
Where does our data go during the engagement?+
How do you price it?+
Start with the assessment.
Two to three weeks. You get a map of your systems, named owners, a ranked list of gaps, and a costed 6-month plan. No obligation to run it with us.