How to Build an MDM Business Case That Wins Executive Sponsorship

Master data management rarely loses funding because executives doubt that data matters. It loses funding because the case is framed too narrowly: as a data clean-up exercise, a platform implementation, or an information technology modernisation project. That is not how senior leaders allocate capital. They fund growth, margin improvement, risk reduction, regulatory resilience, faster execution, and stronger decision-making. That distinction matters even more now. Deloitte’s 2026 Chief Data and Analytics Officer survey found that 61% of respondents said that improving data quality and access is key to the success of artificial intelligence, while 56% reported intense pressure to prove direct business value and return on investment from data and artificial intelligence initiatives. IBM, meanwhile, reports that more than a quarter of organisations estimate losses exceeding USD 5 million per year due to poor data quality. PwC’s 2025 compliance survey adds a further layer of urgency: over half of executives ranked cybersecurity and data protection/privacy among their top compliance priorities.

For South African executives, the pressure is not abstract. It sits inside a governance environment shaped by POPIA enforcement, rising expectations around access to information, and more rigorous sustainability and climate disclosure requirements under IFRS S1 and IFRS S2. The Information Regulator is explicitly empowered to monitor and enforce compliance with POPIA and PAIA, while IFRS S1 and IFRS S2 require governance, strategy, risk management, and performance disclosures that depend on reliable, traceable underlying data. In other words, the quality of master data increasingly affects not just operations but also assurance, reporting credibility, and the cost of capital.

That is why the best MDM business cases do not begin with data models, golden records, or software categories. They begin with a business problem the executive committee already recognises: duplicate suppliers inflating procurement risk; inconsistent product hierarchies distorting margin analysis; fragmented customer records undermining service and compliance; or conflicting asset data slowing maintenance and capital decisions. As Deloitte’s Ashish Verma put it, effective data leadership is “a foundational element of AI success.” The same is true of operational trust. If the underlying master data is weak, artificial intelligence, analytics, controls, and reporting all inherit that weakness.

Why most MDM business cases fail

Most unsuccessful MDM business cases share three weaknesses. First, they describe capability rather than consequence: they explain what MDM is, but not what business failure it will stop or what enterprise value it will unlock. Second, they try to sell the end-state architecture before proving the economics of a first business domain. Third, they treat governance, stewardship, and adoption as secondary workstreams rather than core design choices. That combination makes the initiative look expensive, slow, and abstract. Practical MDM guidance from Profisee and Stibo makes the same point from a different angle: leadership buy-in depends on a quantified business case, a compelling vision, and repeated communication of what value each stakeholder will actually receive.

McKinsey’s 2024 research reinforces why that matters. In its survey of more than 80 large global organisations, only 29% had full upstream and downstream MDM integrations and all governance or stewardship roles in place. McKinsey also notes that while 69% of surveyed organisations already use artificial intelligence in their data management capabilities, only 31% use advanced artificial intelligence techniques to improve match-and-merge and, more broadly, master data quality. That gap is instructive: many organisations are trying to scale advanced analytics on top of incomplete data foundations. Executives see the ambition, but they also see the execution risk.

The executive lens: what leaders are actually buying

An executive sponsor is not buying MDM. They are buying a better operating outcome. In manufacturing, that may mean fewer material duplicates, cleaner bill-of-material structures, faster planning, and less waste. In mining, it may mean more reliable data on assets, locations, contractors, and materials to improve maintenance planning, safety reporting, inventory control, and joint-venture visibility. In fast-moving consumer goods and retail, it may be cleaner product, supplier, and customer data to improve ranging, promotions, replenishment, and omnichannel execution. In telecommunications and financial services, the case often centres on consistent customer, product, reference, and legal-entity data to support service, compliance, fraud controls, and reporting. The business case wins when those outcomes are made explicit in financial, operational, and risk terms.

IBM recently described data integration as “the circulatory system of your business.” That is a useful way to think about executive sponsorship. When the circulatory system is fragmented, every initiative suffers: artificial intelligence, customer experience, compliance, finance, supply chain, and productivity. Poor master data does not normally appear as a line item called “bad data”; it appears as expediting costs, rework, stock discrepancies, inaccurate forecasts, failed reconciliations, delayed onboarding, inconsistent reporting, weak controls, and lost confidence in dashboards. IBM’s 2026 work on poor data quality makes exactly that point: the damage often appears downstream as inefficiency, lost revenue, and missed opportunities rather than at the point where the data issue originated.

What a winning MDM business case must contain

1. A clear strategic trigger

Start with the business event or pressure that makes action necessary now. It may be artificial intelligence readiness, ERP consolidation, operating model redesign, sustainability reporting, procurement transformation, customer experience improvement, or post-merger integration. Wipro’s 2025 State of Data4AI report is useful here: 79% of organisations see artificial intelligence as critical, yet only 14% believe their data maturity can support artificial intelligence at scale. That gap gives the executive team a credible reason to act. MDM becomes relevant not because it is fashionable, but because the organisation’s strategic ambitions already depend on trusted, shared data.

2. A quantified business pain statement

The most persuasive cases convert data defects into measurable business losses. Do not say, “customer data is inconsistent.” Say, “customer onboarding takes too long because legal-entity, branch, product, and party data are inconsistent across systems.” Do not say, “supplier records are duplicated.” Say, “duplicate and incomplete supplier records increase procurement cycle time, payment errors, control exceptions, and audit effort.” IBM’s evidence on the financial cost of poor data quality helps anchor this logic. Still, the winning move is to quantify your organisation’s exposure: working capital tied up in inventory errors, revenue leakage from product misclassification, service delays from fragmented customer records, or compliance effort due to manual reconciliations.

3. One domain, one use case, one accountable sponsor

Executives sponsor phased value, not multi-year abstraction. McKinsey explicitly recommends starting with a pilot in one domain so organisations can validate design, governance, and workflows before scaling. That approach also improves governance credibility. A first domain might be a product in retail, a supplier in manufacturing, an asset in mining, a customer in telecommunications, or party/reference data in financial services. The key is to choose a domain where the pain is visible, cross-functional, and economically defensible. Then name the executive sponsor who owns the outcome. Without a sponsor with both budget influence and operational accountability, MDM remains a well-meaning programme in search of authority.

4. A governance and operating model, not just a technology stack

Senior leaders know that most transformation programmes fail in the gap between design and behavioural adoption. McKinsey is clear that robust MDM requires defined roles and responsibilities, a governance council with representation from business units and information technology, and a business-backed, information technology-supported operating model. Stibo makes the same point more plainly: executive sponsorship is essential for maintaining accountability and aligning the initiative with business results. In South Africa, that governance case becomes even stronger where data feeds regulatory processes under POPIA, PAIA, audit trails, and increasingly formalised sustainability disclosures. If the business case does not specify ownership, stewardship, policy, issue resolution, and decision rights, executives will correctly conclude that the organisation is not ready.

5. Phased economics, the chief financial officer can interrogate

A credible MDM business case should separate foundation costs from use-case value. It should show what is required in phase one, what benefits are expected in the first 6 to 12 months, what assumptions underlie those benefits, and what must be true for scale to follow. Deloitte’s latest survey shows why this matters: more than half of data leaders feel intense pressure to prove direct return on investment. That means the economics must be testable. Include avoided costs, productivity gains, revenue protection, working-capital improvement, compliance-effort reduction, and risk reduction. Also include the less comfortable numbers: stewardship effort, data remediation effort, integration complexity, change management, and ongoing run costs. An executive committee is more likely to trust a case that surfaces the real cost profile than one that hides it behind hopeful language of transformation.

6. A delivery approach that reduces perceived risk

Large enterprises do not reject MDM because they reject trusted data. They reject it when the initiative appears to be a long, expensive interruption to business as usual. The answer is to show how risk will be contained: pilot first, integrate selectively, prioritise critical attributes, define quality rules early, and prove adoption before expanding scope. McKinsey recommends piloting one domain; IBM stresses the need for profiling, cleansing, standardisation, validation, governance, and regular audits; and its broader integration guidance warns that hybrid environments, security obligations, and real-time requirements can quickly increase complexity if not managed deliberately. The executive message should therefore be simple: this is a controlled sequence of value releases, not a speculative enterprise-wide rewrite.

A practical board-level structure for the MDM case

A sponsorable MDM paper is usually shorter than the teams writing it expect. At board or executive committee level, six decisions matter.

First, what business problem are we solving?
Anchor the case in revenue, cost, risk, or compliance, not in architecture language.

Second, why now?
Link the case to a strategic trigger such as artificial intelligence, regulatory pressure, merger integration, ESG reporting, customer experience, or operating model redesign.

Third, what is the first domain and first use case?
Show where value will be proved first, how long it will take, and who owns it.

Fourth, what governance model will make the result durable?
Name sponsor, domain owner, steward roles, council structure, escalation path, and policy framework.

Fifth, what economics support the investment?
Present quantified benefits, assumptions, costs, risks, and milestones in a format a chief financial officer can challenge and still support.

Sixth, what does success look like in twelve months?
Define specific outcomes: fewer duplicates, faster onboarding, improved fill rates, cleaner spend visibility, stronger auditability, better reporting confidence, or reduced manual reconciliations. Those are the outcomes executive sponsors remember.

What this means for South African enterprises

For large South African organisations in manufacturing, mining, fast-moving consumer goods, telecommunications, financial services, and retail, the MDM case should be built with an unusual level of commercial discipline. Many of these organisations operate in federated structures, legacy estates, partner ecosystems, and regulated environments where data fragmentation is not an isolated inconvenience but a structural drag on execution. The business case, therefore, needs to connect master data directly to enterprise priorities: control over supplier and material data, confidence in customer and product reporting, readiness for artificial intelligence, resilience in assurance and disclosure, and faster execution across distributed operations. POPIA and IFRS-linked disclosure expectations only increase the cost of getting this wrong.

The organisations that win sponsorship do one thing especially well: they make MDM feel smaller and more consequential at the same time. Smaller, because the first decision is a focused, manageable investment with visible ownership. More consequential, because the outcome is tied to something the executive committee already cares about deeply: growth, risk, trust, or speed. That is the real discipline of the MDM business case. It is not a defence of data management. It is a clear investment argument for better business performance.

Conclusion

The executive sponsorship test for MDM is straightforward. Can the leadership team see a material business problem, a credible financial case, a named sponsor, a workable governance model, a contained first step, and a realistic path to scale? If the answer is yes, MDM moves from “important” to “fundable.” If the answer is no, even the most sophisticated platform demonstration will not rescue the proposal. In the current environment, where artificial intelligence ambitions are outpacing data maturity, where trust depends on strong data, processes, and controls, and where regulatory and disclosure expectations are becoming more exacting, that discipline is no longer optional.

If your leadership team is evaluating how to frame, quantify, or stress-test an MDM investment, contact Emergent Africa or request that we contact you to unpack how to structure the business case for your organisation.

Source references

1. Deloitte, “Deloitte’s Chief Data and Analytics Officer Survey Finds CDAOs Acting as AI ‘Trailblazers’ and Influential Leaders in Driving Long-Term AI Value”.

2. IBM, “The True Cost of Poor Data Quality”.

3. IBM, “Top Data Integration Challenges and Solutions”.

4. McKinsey, “Master Data Management: The Key to Getting More from Your Data”.

5. PwC, “Global Compliance Survey 2025”.

6. PwC, “The New Architecture of Trust”.

7. IFRS Foundation, “IFRS S1 General Requirements for Disclosure of Sustainability-related Financial Information”.

8. IFRS Foundation, “IFRS S2 Climate-related Disclosures”.

9. Information Regulator South Africa, POPIA / PAIA overview.

10. Wipro, “State of Data4AI Report 2025”.

11. World Economic Forum, “Scaling AI with Strategy, Data and Workforce Readiness”.

12. Profisee, “Selling Master Data Management to Leadership [6 Strategy Tips]”.

13. Stibo Systems, “How to Create a Master Data Management Roadmap in Five Steps” and “Getting Enterprise Data Modelling Right with Data Governance”.