MDM project timeline and cost depend on five drivers: domain count, source system count, data volume and complexity, stewardship maturity, and platform choice. Specific numbers duration and dollar ranges must come out of a discovery conversation; every number on this page is flagged because the honest answer is "it depends on your situation."
The Five Drivers
|
Driver |
How it affects timeline / cost |
|
Domain count |
Linear: each additional domain is a sub-project |
|
Source system count |
Super-linear: integration complexity compounds |
|
Data volume / complexity |
Affects matching cost and steward workload |
|
Stewardship maturity |
Mature governance shortens delivery |
|
Platform choice |
Cloud-native faster; enterprise platforms heavier |
Driver 1: Domain Count
First domain (typically customer) carries the platform setup cost. Subsequent domains (product, supplier, location, employee) are cheaper but not free each has its own model, sources, and stewardship. Sequence matters: start where business pain is highest.
Driver 2: Source System Count
Each additional source adds integration work, data-mapping work, matching tuning, and stewardship complexity. Twenty sources is not twice the work of ten it is more, because the combinations matter.
Driver 3: Data Volume and Complexity
Volume affects platform sizing and matching compute. Complexity (free-text addresses, multi-language, hierarchy depth, regulatory attributes) affects rule design and steward review effort.
Driver 4: Stewardship Maturity
Organizations with existing data governance, defined data owners, and steward bandwidth deliver MDM faster. Organizations starting both governance and MDM together take longer and that is fine, but it is two journeys not one. (See data governance vs master data management.)
Driver 5: Platform Choice
Cloud-native MDM (lighter setup, faster time to first value) versus enterprise-platform MDM (heavier setup, broader capability). The right choice depends on your data domains, latency, and existing stack. (See how to select the right MDM platform seven criteria.)
Scope Levers
Levers to reduce timeline and cost: start with one domain instead of three; start with the top five sources instead of all twenty; use cleansing tools and patterns from prior engagements; phase the stewardship organization. Levers that ADD cost: insisting on day-one real-time across all consumers; bespoke matching when packaged options work; overdesigning the platform.
Investment Categories
Centric engagement fees platform license or subscription internal stewardship FTEs ongoing run support integration build labor (may be Centric or client side). The full TCO conversation belongs in the discovery phase. (See Centric's MDM engagement model and delivery process.) Centric scopes MDM engagements through its master data management service.
Frequently Asked Questions
How long does MDM take?
First-domain delivery often runs months to quarters depending on sources and complexity. and expect a discovery conversation before committing.
How much does MDM cost?
Centric engagement, platform license, internal FTEs, run support. We recommend scoping discovery as a fixed-price engagement so the rest of the investment story is informed.
When do we start seeing value?
First operational value often comes during phase 3 (build) as the first domain goes live for a priority consumer. Business outcome lift typically lands post-launch.
Can we phase the investment?
Yes. Most engagements phase domains and sources to spread cost and reduce risk. Centric helps structure the phasing.
Conclusion
MDM timeline and investment are not standardized numbers they are outputs of the drivers and levers above. The honest answer is "let us run a discovery conversation," and the dishonest answer is "here is a fixed quote." Centric runs the conversation that produces a real number for your situation.
