{"version":"1.0","type":"agent_native_article","locale":"en","slug":"why-97-percent-companies-have-ai-projects-only-5-percent-data-ready-mqssqw65","title":"Why 97% of Companies Have AI Projects but Only 5% Have Data Ready to Use Them","primary_category":"ai","author":{"name":"Elena Costa","slug":"elena-costa"},"published_at":"2026-06-25T00:02:55.283Z","total_votes":84,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/why-97-percent-companies-have-ai-projects-only-5-percent-data-ready-mqssqw65","agent":"https://sustainabl.net/agent-native/en/articulo/why-97-percent-companies-have-ai-projects-only-5-percent-data-ready-mqssqw65"},"summary":{"one_line":"A 2026 Dun & Bradstreet survey of 10,000 companies reveals a structural gap between AI project adoption and data readiness, with only 5% of companies having data prepared to support their AI initiatives—exposing a systemic pattern of investment without operational results.","core_question":"Why do nearly all companies have AI projects but almost none have the data infrastructure to make them work in production?","main_thesis":"The AI implementation gap is not a technology problem but a fundamentals problem: most organizations approve AI pilots without clean data, redesigned workflows, or accountability structures, resulting in high visible activity and low operational transformation. The minority generating real value shares a different operating model, not a different model provider."},"content_markdown":"## Why 97% of Companies Have AI Projects and Only 5% Have Data Ready to Use Them\n\nThere is a statistic that should bring any boardroom discussion about artificial intelligence to a halt: according to a Dun & Bradstreet survey of 10,000 companies conducted in 2026, **97% declare that they have active AI initiatives**, while only **5% consider that their data is truly ready to sustain them**. That gap is not a minor technical detail. It is the distance between investing in infrastructure and having something that works reliably in production.\n\nWhat that number describes is a pattern well known to those who have observed how technology decisions are made in large organizations: first the pilot gets approved, then the problem that justifies having approved it is sought after the fact. The demonstration impresses. The room applauds. The project receives a budget. And somewhere between that moment and day-to-day operations, something breaks down without anyone having formally declared failure.\n\nBCG documented this with precision: **only 5% of companies obtain substantial value from AI**, while 60% report no material impact. McKinsey, for its part, found that more than 80% of respondents were not seeing any tangible effect on EBIT from generative artificial intelligence, even as declared adoption continued to grow. Those figures are not a condemnation of the technology. They are a snapshot of how investment is being managed.\n\n## The Illusion of the Perpetual Pilot\n\nThere is a silent form of organizational failure that does not appear in balance sheets or generate press releases: the pilot that never dies. It installs itself under the name of \"innovation,\" chronically consumes technical and human resources, produces reasonably attractive internal presentations, and never manages to become something that changes a single line on the income statement. Organizations with greater maturity in digital transformation have spent years learning that this dynamic is not accidental, but structural.\n\nThe problem begins at the origin of the project. When an AI initiative is approved because \"the use case is interesting\" or because a vendor gave a convincing demonstration, it lacks from the very beginning something that every investment program should have: a measurable baseline, an owner of the outcome, and an exit criterion if value does not materialize. Without those three elements, the pilot has no way to die with dignity or to scale with traceability.\n\nBCG identified that companies with the best AI results prioritize **between three and four use cases on average**, compared to six or seven at organizations with the worst returns. That difference does not arise from the available budget or the size of the technical team. It arises from the willingness to reject initiatives that cannot demonstrate strategic alignment and economic viability from the moment they request funding. Focus is not an abstract managerial virtue; in this context it is the only condition that makes scaling viable.\n\nWhat the BCG and McKinsey data reveal in combination is that the majority of organizations are in a phase that might be called **AI theater**: high visible activity, low operational transformation. Press releases talk about adoption. Internal metrics tell a different story.\n\n## The Problem Is Not in the Model, It Is Below the Model\n\nThere is an understandable tendency to analyze AI performance from the angle of the model: which architecture was used, which vendor, which version of the system. That analysis has utility in research contexts, but in most business environments the bottleneck is not in the model. It is in what the model needs to function reliably: clean data, shared definitions, redesigned workflows, and clear ownership over the decisions the system is meant to support.\n\nThe Dun & Bradstreet survey cited earlier puts it in terms that do not admit much alternative interpretation: if almost no company considers its data to be ready, then the massive problem is not one of technological experimentation but of fundamentals. An AI that receives fragmented data, without a single source of truth, with business rules buried in spreadsheets and exception processes that nobody documented, does not generate more reliable recommendations than the system it aims to improve. In many cases, it simply accelerates existing errors.\n\nPwC identified this pattern from another angle: **the most solid results come when companies redesign workflows** rather than layering AI on top of legacy processes. That distinction matters economically. Adding an artificial intelligence component to an inefficient process can make that process faster. But it does not change the cost logic or the structure of the operation. The economics of work remain the same, only executed at greater speed.\n\nThe case of highly demanding regulatory environments is especially clear. Finance, regulatory compliance, legal review, supply chain: these are contexts where two different responses to the same query are not a sign of system flexibility, but a control problem. Reliability in production has a different standard from that of experimentation. And that difference is what separates systems that get adopted from those that are quietly abandoned after the pilot.\n\n## When 70% of the Value Comes from Factors That Do Not Appear on the Technology Roadmap\n\nBCG documented something that tends to make technology teams uncomfortable: in AI-driven transformations that generated real results, **70% of the value came from actions related to people**, not technology. That includes redefinition of roles, changes in incentives, active management of the adoption process, and the building of capabilities within the teams that were supposed to use the systems in production.\n\nThat finding should not be read as an argument against technical investment. It should be read as a map of where the real blockage typically lies. A language model can process thousands of contracts per hour; but if the legal team does not trust its outputs, if the area's incentives have not changed, if nobody redefined what it means to \"review a contract\" when there is a system that performs the first pass, adoption does not occur in a sustained manner. The system exists. The value does not.\n\nThe Global 1000 companies that are reporting measurable impacts share some operational characteristics: they have redesigned specific processes before implementing the systems, they have established metrics against documented baselines, and they have assigned ownership of results to people with real accountability over those numbers. In some documented cases, the results are material: increases on the order of 30% in manufacturing efficiency, 80% reductions in document analysis times, improvements of 1.7 times in sales conversion rates. Those numbers do not come from superior models. They come from superior integrations.\n\nThe difference between a company that uses AI and a company that operates with AI does not lie in the model provider or the size of the innovation budget. It lies in whether the organization has been able to connect the system's output to a concrete decision, within a redesigned process, with someone responsible for measuring whether that moves the number it is supposed to move.\n\n## The Real Displacement That These Numbers Reveal\n\nThe current phase of the business cycle of artificial intelligence is not being defined by advances in foundation models. It is being defined by the capacity of organizations to move from the legitimacy of the experiment to the demand for results. And that transition is not yet the majority condition.\n\nWhat the data from BCG, McKinsey, PwC, and Dun & Bradstreet describe collectively is a market with an asymmetric distribution: a small minority of companies is generating measurable and compounding value with AI, while a broader majority continues to accumulate projects that do not touch the income statement. That gap does not close with more technology. It closes with portfolio discipline, with data fundamentals that are today clearly missing in most of the market, and with an organizational willingness to accept that real adoption requires redesign, not superimposition.\n\nThe displacement that is occurring, though still incomplete, points in a precise direction: AI is ceasing to be a signal of modernity and is becoming a demand for evidence. Organizations that cannot respond with numbers to the question of what changed operationally since they implemented their systems will face growing pressure — first internally, then from their boards of directors and their investors. The capital that previously flowed toward the experiment will begin migrating to where the experiment proved to be something more.","article_map":{"title":"Why 97% of Companies Have AI Projects but Only 5% Have Data Ready to Use Them","entities":[{"name":"Dun & Bradstreet","type":"company","role_in_article":"Source of the primary statistic: 2026 survey of 10,000 companies on AI data readiness"},{"name":"BCG","type":"institution","role_in_article":"Source of data on AI value concentration, use case prioritization, and the 70% people-factor finding"},{"name":"McKinsey","type":"institution","role_in_article":"Source of data showing 80%+ of respondents saw no EBIT impact from generative AI despite growing adoption"},{"name":"PwC","type":"institution","role_in_article":"Source of finding that redesigning workflows—rather than layering AI on legacy processes—drives the strongest results"},{"name":"Elena Costa","type":"person","role_in_article":"Author of the article"},{"name":"AI data readiness","type":"technology","role_in_article":"Central concept: the gap between AI project adoption and the data infrastructure required to make those projects work"},{"name":"Generative AI","type":"technology","role_in_article":"Specific AI category referenced in McKinsey data on EBIT impact"},{"name":"Global 1000","type":"market","role_in_article":"Reference group of large companies showing measurable AI results through process redesign and accountability structures"}],"tradeoffs":["Speed of AI adoption vs. depth of data readiness: moving fast on pilots without fixing data fundamentals produces systems that fail in production","Breadth of AI portfolio vs. depth of impact: more use cases correlates with worse returns; fewer use cases with better results","Technology investment vs. organizational investment: 70% of value comes from people factors, but most budgets are weighted toward technology","Visible innovation activity vs. measurable operational transformation: AI theater satisfies stakeholder optics but does not move the income statement","Layering AI on legacy processes (faster to deploy) vs. redesigning workflows (slower but changes cost structure)"],"key_claims":[{"claim":"97% of companies in a 2026 Dun & Bradstreet survey of 10,000 companies report active AI initiatives.","confidence":"high","support_type":"reported_fact"},{"claim":"Only 5% of those companies consider their data truly ready to support their AI initiatives.","confidence":"high","support_type":"reported_fact"},{"claim":"Only 5% of companies obtain substantial value from AI, while 60% report no material impact, per BCG.","confidence":"high","support_type":"reported_fact"},{"claim":"More than 80% of McKinsey respondents saw no tangible EBIT effect from generative AI despite growing declared adoption.","confidence":"high","support_type":"reported_fact"},{"claim":"Top AI performers prioritize 3–4 use cases versus 6–7 at underperformers, per BCG.","confidence":"high","support_type":"reported_fact"},{"claim":"70% of value in successful AI transformations came from people-related factors, not technology, per BCG.","confidence":"high","support_type":"reported_fact"},{"claim":"Documented results in leading companies include 30% manufacturing efficiency gains, 80% reductions in document analysis time, and 1.7x sales conversion improvements.","confidence":"medium","support_type":"reported_fact"},{"claim":"Adding AI to an inefficient process makes it faster but does not change its cost logic or operational structure.","confidence":"high","support_type":"inference"}],"main_thesis":"The AI implementation gap is not a technology problem but a fundamentals problem: most organizations approve AI pilots without clean data, redesigned workflows, or accountability structures, resulting in high visible activity and low operational transformation. The minority generating real value shares a different operating model, not a different model provider.","core_question":"Why do nearly all companies have AI projects but almost none have the data infrastructure to make them work in production?","core_tensions":["Investment legitimacy vs. operational results: organizations have strong incentives to announce AI adoption but weak incentives to measure its actual impact","Technology roadmap vs. organizational readiness: technical deployment timelines do not account for the people and process changes that determine whether value is realized","Board-level AI narrative vs. operational reality: declared adoption continues to grow while EBIT impact remains absent for the majority","Innovation culture vs. portfolio discipline: the pressure to experiment broadly conflicts with the evidence that focus is the condition for scaling","Speed to pilot vs. depth of data fundamentals: the fastest path to an AI announcement is the slowest path to production-grade reliability"],"open_questions":["What specific data infrastructure investments are required before an AI initiative can be considered production-ready?","How should organizations structure exit criteria for AI pilots to avoid the perpetual pilot trap?","What governance mechanisms allow boards to distinguish between AI theater and genuine operational transformation?","How do the 5% of companies with data-ready AI differ structurally from the 97% with active but unsupported initiatives?","Will capital markets develop the analytical frameworks to price the difference between AI adoption and AI operational impact?","How does the data readiness gap differ across company sizes—are SMEs more or less exposed than large enterprises?","What role do AI vendors play in perpetuating the pilot trap by optimizing for demo performance rather than production reliability?"],"training_value":{"recommended_for":["Chief Data Officers and Chief AI Officers designing AI governance frameworks","CFOs and boards evaluating AI investment portfolios and demanding evidence of EBIT impact","Strategy consultants advising organizations on AI transformation roadmaps","Product and engineering leaders deciding which AI use cases to prioritize","Investors assessing the operational credibility of AI adoption claims in portfolio companies","Business agents trained to evaluate technology investment decisions against operational outcomes"],"when_this_article_is_useful":["When evaluating whether to approve or expand an AI initiative budget","When diagnosing why an existing AI pilot has not scaled to production","When building the business case for data infrastructure investment as a prerequisite to AI","When designing governance frameworks for AI portfolio management","When advising boards or investors on how to assess AI adoption claims from management","When structuring accountability and measurement systems for AI programs"],"what_a_business_agent_can_learn":["How to identify the structural conditions that separate AI pilots from AI in production","The three minimum requirements for any AI initiative: measurable baseline, outcome owner, exit criterion","Why use case concentration (3–4 vs. 6–7) is a leading indicator of AI ROI, not a resource constraint","How to distinguish AI theater from operational transformation using EBIT impact as the primary filter","Why workflow redesign must precede AI deployment to change cost structure rather than just execution speed","How to weight organizational investment (roles, incentives, adoption) relative to technical investment in AI programs","The data readiness audit as a prerequisite step before AI budget approval"]},"argument_outline":[{"label":"The Gap","point":"97% of companies report active AI initiatives but only 5% consider their data truly ready, per Dun & Bradstreet 2026 survey of 10,000 companies.","why_it_matters":"This is not a marginal discrepancy—it means the vast majority of AI investment is built on a foundation that cannot support production-grade systems."},{"label":"The Pilot Trap","point":"Organizations approve AI pilots based on impressive demos without establishing measurable baselines, outcome owners, or exit criteria.","why_it_matters":"Without these three elements, pilots cannot scale with traceability or fail with dignity—they become chronic resource consumers that never touch the income statement."},{"label":"Focus as a Differentiator","point":"BCG found that top-performing AI companies prioritize 3–4 use cases versus 6–7 at underperformers.","why_it_matters":"Selectivity is not a budget constraint—it is the structural condition that makes scaling viable and forces strategic alignment from the funding stage."},{"label":"The Real Bottleneck","point":"The bottleneck in most business AI deployments is not the model but what sits below it: data quality, shared definitions, redesigned workflows, and decision ownership.","why_it_matters":"Layering AI on top of legacy processes accelerates existing errors rather than changing cost structure or operational logic."},{"label":"The 70% Rule","point":"BCG documented that 70% of value in successful AI transformations came from people-related factors: role redefinition, incentive changes, adoption management, and capability building.","why_it_matters":"Technical investment is necessary but insufficient—organizations that skip the human layer get systems that exist but generate no sustained value."},{"label":"The Asymmetric Market","point":"A small minority of companies generates measurable, compounding AI value while the majority accumulates projects with no EBIT impact.","why_it_matters":"The gap will not close with more technology—it requires portfolio discipline, data fundamentals, and organizational willingness to redesign rather than superimpose."}],"one_line_summary":"A 2026 Dun & Bradstreet survey of 10,000 companies reveals a structural gap between AI project adoption and data readiness, with only 5% of companies having data prepared to support their AI initiatives—exposing a systemic pattern of investment without operational results.","related_articles":[{"reason":"Directly complementary: examines why AI budgets stall before generating measurable value and documents the 42% abandonment rate of AI initiatives in 2025, extending the same structural argument about investment without results","article_id":14231},{"reason":"Relevant from the production reliability angle: explores how AI speed without accuracy erodes user trust in enterprise contexts, connecting to the article's argument that reliability standards in production differ fundamentally from experimentation","article_id":14121}],"business_patterns":["Pilot approval precedes problem definition: projects get funded based on demo impressions, then justification is constructed retroactively","The perpetual pilot: AI initiatives that never die and never scale, consuming resources while producing internal presentations instead of results","AI theater: high visible adoption activity combined with low or zero operational transformation","Asymmetric value distribution: a small minority captures compounding AI value while the majority sees no EBIT impact","Process superimposition vs. process redesign: most organizations add AI to existing workflows rather than redesigning them, limiting economic impact to speed rather than structure","Accountability vacuum: AI systems deployed without clear ownership of outcomes or metrics, making it impossible to measure or demand results"],"business_decisions":["Establish measurable baselines, outcome owners, and exit criteria before approving any AI pilot","Limit active AI use cases to 3–4 maximum to enable focus and strategic alignment","Audit data quality and infrastructure readiness before committing to AI implementation budgets","Redesign workflows before layering AI on top of existing processes","Assign result ownership to individuals with real accountability over the metrics the AI system is meant to move","Build internal capability and redefine roles before expecting sustained AI adoption","Create explicit criteria for when a pilot is declared a failure and resources are reallocated"]}}