{"version":"1.0","type":"agent_native_article","locale":"en","slug":"when-ai-arrives-in-procurement-greatest-resistance-not-in-software-mqaxr2iu","title":"When AI Arrives in Procurement, the Greatest Resistance Isn't in the Software","primary_category":"transformation","author":{"name":"Valeria Cruz","slug":"valeria-cruz"},"published_at":"2026-06-12T12:03:41.938Z","total_votes":82,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/when-ai-arrives-in-procurement-greatest-resistance-not-in-software-mqaxr2iu","agent":"https://sustainabl.net/agent-native/en/articulo/when-ai-arrives-in-procurement-greatest-resistance-not-in-software-mqaxr2iu"},"summary":{"one_line":"AI adoption in procurement fails not because of bad software but because organizations lack the data architecture, governance, and role redesign needed before deployment.","core_question":"Why do AI implementations in procurement succeed in pilots but collapse at scale, and what does it take to build the organizational foundation that makes them work?","main_thesis":"The primary barrier to AI in procurement is not technological but organizational: fragmented data, undocumented governance, and roles built around tacit knowledge that was never converted into structured information. Organizations that skip foundational redesign before deployment amplify their existing dysfunction rather than solving it."},"content_markdown":"## When AI Arrives in Procurement, the Greatest Resistance Is Not in the Software\n\nThere is a pattern that repeats itself in almost every organization going through a deep technological transformation: the hardest part was not choosing the platform. It was discovering, weeks after the launch, that the underlying problem was not technological at all.\n\nIn the case of artificial intelligence applied to procurement and sourcing functions — what the industry calls procurement — that pattern is becoming so common that it already has a name of its own. McKinsey describes it with surgical precision: **the organizations that manage to scale AI in procurement are not those that chose the best software, but those that redesigned their workflows from end to end before asking a model to automate them.** Those that did not discovered that AI does not fix operational fragmentation. It amplifies it.\n\nWhat is happening in the world of corporate acquisitions is not a tool upgrade. It is a reordering of who makes decisions, with what information, at what speed, and with what level of human intervention. That cannot be solved by purchasing a license. It demands that the organization change what it understands by value, by control, and by accountability.\n\n---\n\n## The Illusion of the Successful Pilot\n\nPrajkta Waditwar, senior director of technology sourcing at Box and member of the Forbes Technology Council, described a scenario that any operations leader will recognize: a global organization implemented AI to improve supplier visibility and automate risk assessment across different regions. The models performed well in the test environment. But when the time came to scale, the system exposed inconsistent supplier data, fragmented approval workflows, and disconnected enterprise management systems that had survived for years thanks to human tolerance for ambiguity.\n\nThis type of post-pilot failure has an internal logic that is worth naming explicitly: **pilots work because variables are controlled**. An orderly spending category is selected, a motivated team, a collaborative supplier. The AI shines. The investment is validated. The decision to scale is made. And then the system comes into contact with the full operational reality, with all its accumulated history of improvised processes, mislabeled data, and decisions that used to be made over the phone.\n\nThe problem is not that the organization did something wrong. The problem is that for years, efficiency was sustained by the human judgment of people who knew the shortcuts, the exceptions, and the suppliers that were difficult to classify. That tacit knowledge was never documented, never structured, never converted into data. AI cannot operate on what does not exist as data.\n\nDeloitte documents this in its 2025 global survey of chief procurement officers: organizations with greater digital maturity are obtaining significantly higher returns on their investments in generative artificial intelligence. The gap is not in who has access to the technology. It is in who built the foundations beneath it.\n\n---\n\n## The Structural Problem That No One Has Named Yet\n\nThere is something that organizations tend to underestimate when embarking on this transformation, and it deserves to be named precisely: **operational fragmentation in procurement is not an accident. It is the result of years of rational decisions made locally.**\n\nEvery region that negotiated its own contracts had reasons to do so. Every business unit that built its own approval process was solving a real problem with the resources it had. Every team that maintained a spreadsheet parallel to the corporate system did so because the corporate system did not respond with the speed they needed. Fragmentation is, in many cases, the digital footprint of an organization that grew faster than its governance capacity.\n\nThe moment that organization introduces artificial intelligence into its procurement processes is precisely the moment when that history is exposed. And what is exposed is not only technical inefficiency. What is exposed is a governance model that depended on the individual judgment of specific people in order to function.\n\nThis connects to something McKinsey points to when describing the evolution toward what they call \"AI agents\": systems that can ingest context, plan complex tasks, and act with a certain degree of autonomy across multiple systems simultaneously. When that agent attempts to operate in an environment where supplier data exists in three different versions depending on which system you consult, where approval policies vary by region without any documented logic, and where the master contract sits on a local server that only one person knew about — someone who no longer works at the company — the agent does not fail due to technological limitations. It fails because the environment does not have the minimum architecture required to sustain automated decisions.\n\nThe question this raises for senior leadership is not whether to implement AI in procurement. It is how honest they are being about the true state of their data infrastructure and governance before asking the system to decide.\n\n---\n\n## When the Procurement Function Stops Being Operational\n\nZycus, in its 2026 artificial intelligence guide for procurement, describes the transition in terms that initially sound like marketing copy but, when read carefully, reveal something more structural: AI is not arriving in procurement to make what already exists more efficient. It is arriving to absorb the bulk of transactional work and free up human capacity for something different.\n\nThat \"something different\" is what Waditwar describes clearly from her direct experience: **procurement teams are being brought in increasingly earlier in strategic conversations**, not to negotiate prices, but to assess the long-term operational implications of a supplier decision. How much dependency does a deep integration with a software vendor generate? How complex would it be to exit that contract in three years? Does the technology architecture being purchased increase or reduce future flexibility?\n\nThose are not questions that historically belonged to a procurement function. They are questions of strategic risk management. And the fact that they are now part of the area's agenda reveals something important about what is changing: **the automation of transactional work does not only free up time — it redistributes authority.**\n\nHFS Research puts it in more direct terms: AI platforms are enabling procurement leadership to move from operational execution toward strategic enablement. That means the competency profile needed in the function is changing, that the indicators used to measure its success will have to change, and that the relationship between procurement, finance, legal, and operations will have to be redesigned, because the boundaries between those functions become more porous when there is a connected intelligence system that cuts across all of them.\n\nMcKinsey estimates that a procurement function that completes this transformation can be between 25% and 40% more efficient than current models. But that figure should not be read as a projected headcount reduction. It should be read as a reallocation of capacity: fewer people processing transactions, more people making decisions that systems still cannot make on their own.\n\n---\n\n## The Leadership This Change Needs and the One It Usually Finds\n\nThis is where the transformation becomes most interesting to analyze from an organizational perspective, because the leadership profile that historically dominated procurement functions was built around very specific competencies: hard negotiation, deep supplier knowledge, the ability to move contracts under pressure, the institutional memory of which supplier failed in which context ten years ago.\n\nThat profile has value. But it is not the same profile needed by a procurement function whose greatest contribution to the business lies in the quality of its risk analyses, the speed with which it can integrate market signals into sourcing decisions, and the ability to work with systems that generate recommendations that must be questioned when context demands it.\n\nThe transition is not comfortable, and it would be naive to describe it as if it were simply a growth opportunity for everyone. **There are people with twenty years of experience in procurement whose core value lay in doing well the things that a system can now do faster and with more consistency.** That generates real resistance, and that resistance is not irrational. It is a comprehensible response from someone who sees that the rules of the game have changed without anyone consulting them.\n\nDeloitte points to something that deserves attention: organizations that invest in preparing their teams alongside technological modernization consistently outperform those that focus exclusively on technology deployment. That is not a surprising finding. But the way it translates into organizational practice does matter. It is not about offering AI courses to teams who simultaneously watch their primary tasks being automated. It is about redesigning roles in such a way that people understand what kind of human judgment remains irreplaceable and at what point in the process that judgment is most valuable.\n\nThe risk facing many organizations is not that their procurement teams will reject AI. It is that they will adopt it superficially, using it to accelerate what they were already doing without changing the underlying logic, and that in the process they will lose the opportunity to build a function that truly operates as a layer of strategic intelligence within the business.\n\n---\n\n## Structural Maturity Cannot Be Improvised After Deployment\n\nWhat is happening in procurement is, at its core, a very specific version of something organizations face in almost all of their deep technological transformations: **the gap between the architecture they have and the architecture they need in order to sustain what they want to build.**\n\nAI in procurement is no exception. It is the use case where that gap becomes most visible most quickly, because the consequences of a poorly automated sourcing decision are concrete and costly. A supplier selected by an algorithm that operated on outdated data. A contract automatically renewed because the system did not have access to the risk signal that already existed in another system. An approval that processed itself because no one had clearly defined what level of spending required human oversight.\n\nThose are not AI errors. They are organizational design errors that AI executes with perfect precision.\n\nThe argument that deserves the most attention in this entire debate is not whether artificial intelligence is going to transform corporate procurement. That outcome appears sufficiently supported by the available evidence. The argument that deserves the most attention is how many organizations will arrive at that transformation with the data architecture, governance processes, and role redesign needed for the system to function as promised — and how many will discover that they installed sophisticated technology on a foundation that was not yet ready to support it.\n\nThe answer to that does not depend on the software vendor they choose. It depends on how much institutional honesty they are willing to apply before deployment, not after.","article_map":{"title":"When AI Arrives in Procurement, the Greatest Resistance Isn't in the Software","entities":[{"name":"McKinsey","type":"institution","role_in_article":"Primary research source cited for AI scaling conditions, workflow redesign requirements, and AI agent architecture concepts"},{"name":"Deloitte","type":"institution","role_in_article":"Source of 2025 global CPO survey data linking digital maturity to generative AI ROI and team preparation to transformation success"},{"name":"Zycus","type":"company","role_in_article":"Source of 2026 AI procurement guide describing the transition from transactional to strategic procurement function"},{"name":"HFS Research","type":"institution","role_in_article":"Cited for framing the shift from operational execution to strategic enablement in procurement leadership"},{"name":"Prajkta Waditwar","type":"person","role_in_article":"Senior director of technology sourcing at Box and Forbes Technology Council member; provides practitioner case study of post-pilot failure at scale"},{"name":"Box","type":"company","role_in_article":"Organization where Waditwar leads technology sourcing; context for the practitioner perspective on AI scaling failure"},{"name":"Forbes Technology Council","type":"institution","role_in_article":"Affiliation of Waditwar, lending practitioner credibility to the case described"},{"name":"AI agents","type":"technology","role_in_article":"McKinsey's concept of autonomous systems that ingest context and act across multiple systems; used to illustrate the governance requirements for AI in procurement"},{"name":"Generative AI","type":"technology","role_in_article":"The class of AI technology whose ROI gap between digitally mature and immature organizations is documented by Deloitte"},{"name":"Procurement","type":"market","role_in_article":"The organizational function and industry domain that is the subject of the entire analysis"}],"tradeoffs":["Speed of AI deployment vs. depth of foundational preparation: moving fast exposes fragmentation; moving slow delays competitive positioning","Pilot success as validation signal vs. pilot success as misleading signal: controlled pilots generate investment confidence that does not transfer to full operational reality","Efficiency gains from automation vs. loss of tacit knowledge: automating transactional work removes the human judgment that historically compensated for structural gaps","Preserving experienced procurement talent vs. redesigning roles that may no longer match their core competencies","Centralized governance for AI readiness vs. the local autonomy that created fragmentation but also solved real local problems","Investing in data infrastructure before deployment vs. discovering gaps through deployment failure"],"key_claims":[{"claim":"Organizations that scale AI in procurement are those that redesigned workflows end-to-end before asking a model to automate them, not those that chose the best software.","confidence":"high","support_type":"reported_fact"},{"claim":"Deloitte's 2025 global CPO survey shows organizations with greater digital maturity obtain significantly higher returns on generative AI investments.","confidence":"high","support_type":"reported_fact"},{"claim":"McKinsey estimates a fully transformed procurement function can be 25–40% more efficient than current models.","confidence":"high","support_type":"reported_fact"},{"claim":"The efficiency gain should be read as a reallocation of capacity, not a headcount reduction.","confidence":"medium","support_type":"editorial_judgment"},{"claim":"Fragmentation in procurement is the digital footprint of an organization that grew faster than its governance capacity.","confidence":"medium","support_type":"inference"},{"claim":"Organizations that invest in preparing teams alongside technological modernization consistently outperform those focused exclusively on technology deployment.","confidence":"high","support_type":"reported_fact"},{"claim":"The risk is not that procurement teams reject AI but that they adopt it superficially, accelerating existing logic without changing it.","confidence":"medium","support_type":"editorial_judgment"},{"claim":"AI errors in procurement are in most cases organizational design errors executed with machine precision.","confidence":"interpretive","support_type":"editorial_judgment"}],"main_thesis":"The primary barrier to AI in procurement is not technological but organizational: fragmented data, undocumented governance, and roles built around tacit knowledge that was never converted into structured information. Organizations that skip foundational redesign before deployment amplify their existing dysfunction rather than solving it.","core_question":"Why do AI implementations in procurement succeed in pilots but collapse at scale, and what does it take to build the organizational foundation that makes them work?","core_tensions":["Organizational readiness vs. deployment pressure: leadership wants to move on AI while the data and governance foundations are not yet in place","Institutional memory vs. system legibility: the knowledge that made procurement work for decades was never structured as data and cannot be transferred to AI","Efficiency narrative vs. role disruption reality: framing AI as a growth opportunity obscures the real displacement of people whose value was doing what systems now do","Strategic ambition vs. operational fragmentation: organizations want AI to enable strategic procurement while their operational architecture still reflects years of local improvisation","Human oversight vs. automation logic: defining where human judgment is required demands explicit governance that most organizations have never needed to formalize"],"open_questions":["How many organizations will complete the foundational redesign required before AI deployment versus discovering the gap through failure?","What is the right sequencing between data architecture investment, governance redesign, and AI deployment in procurement?","How should organizations capture and structure the tacit knowledge of experienced procurement professionals before it is lost to automation?","What new competency profile should procurement leaders be hiring and developing toward, and how long does that transition realistically take?","How do organizations measure the success of a procurement function that has shifted from transactional execution to strategic risk enablement?","At what point does the redistribution of authority between procurement, finance, legal, and operations require formal organizational redesign rather than informal collaboration?","Can SMEs with limited resources build the data and governance foundations required, or is this transformation structurally accessible only to large enterprises?"],"training_value":{"recommended_for":["Chief Procurement Officers and VP-level procurement leaders evaluating AI adoption","Chief Operating Officers overseeing supply chain and procurement transformation","Enterprise AI implementation teams assessing organizational readiness","HR and talent leaders redesigning competency frameworks for functions undergoing automation","Strategy consultants advising on digital transformation sequencing","Business agents reasoning about organizational change management in AI deployment contexts"],"when_this_article_is_useful":["When evaluating whether an organization is ready to scale AI beyond a successful pilot","When designing a procurement digital transformation roadmap and sequencing foundational work","When advising on change management for AI adoption in operations or supply chain functions","When assessing the governance and data architecture requirements for AI agent deployment","When building the business case for data infrastructure investment before AI deployment","When redesigning roles and competency frameworks in procurement or operations functions undergoing automation"],"what_a_business_agent_can_learn":["How to distinguish between pilot success and deployment readiness as separate organizational assessments","Why operational fragmentation in procurement is a governance problem, not a technology problem, and how to diagnose it before AI deployment","How to frame the 25–40% efficiency gain from AI procurement transformation as capacity reallocation rather than headcount reduction","How tacit knowledge gaps create AI failure modes that look like software errors but are organizational design errors","How to identify the competency profile shift required when a function moves from transactional execution to strategic enablement","Why investing in team preparation alongside technology deployment consistently outperforms technology-only deployment strategies"]},"argument_outline":[{"label":"1. The pilot illusion","point":"AI pilots succeed because variables are controlled — clean data, motivated teams, cooperative suppliers. Scaling exposes the full operational reality: inconsistent supplier data, fragmented approvals, and tacit knowledge that was never documented.","why_it_matters":"Leaders who validate investment based on pilot performance are making decisions on a sample that does not represent the system they are actually deploying into."},{"label":"2. Fragmentation is not an accident","point":"Operational fragmentation in procurement is the accumulated result of rational local decisions — regions negotiating their own contracts, business units building their own approval flows, teams maintaining parallel spreadsheets because the corporate system was too slow.","why_it_matters":"Treating fragmentation as a technical problem misses its organizational origin. AI does not dissolve it; it makes it visible and consequential at machine speed."},{"label":"3. AI agents need minimum viable architecture","point":"McKinsey's concept of AI agents — systems that ingest context, plan tasks, and act autonomously across multiple systems — breaks down when supplier data exists in three conflicting versions, approval policies are undocumented, and master contracts live on servers only one person knew about.","why_it_matters":"The failure mode is not a software bug. It is an environment that lacks the minimum structure required to sustain automated decisions."},{"label":"4. The function is being repositioned, not just automated","point":"As AI absorbs transactional procurement work, the function is being pulled earlier into strategic conversations: assessing long-term supplier dependency, exit complexity, and architectural flexibility — questions that historically belonged to risk management, not procurement.","why_it_matters":"This is a redistribution of authority, not just a productivity gain. It changes what procurement is for inside the organization."},{"label":"5. The leadership gap","point":"The competency profile that built successful procurement careers — hard negotiation, institutional memory, contract execution under pressure — is not the same profile needed to lead a function whose value now lies in risk analysis, signal integration, and working with AI-generated recommendations.","why_it_matters":"Resistance to AI in procurement is often rational, not irrational. People whose core value was doing well what systems now do faster are responding to a real change in the rules."},{"label":"6. Maturity cannot be improvised post-deployment","point":"Errors attributed to AI in procurement — wrong supplier selected, contract auto-renewed despite existing risk signals, approval processed without human oversight — are organizational design errors that AI executes with perfect precision.","why_it_matters":"The question is not whether AI will transform procurement. It is how many organizations will arrive at that transformation with the foundations in place versus how many will install sophisticated technology on an architecture that was not ready."}],"one_line_summary":"AI adoption in procurement fails not because of bad software but because organizations lack the data architecture, governance, and role redesign needed before deployment.","related_articles":[{"reason":"Directly parallel argument: analyzes why enterprise AI projects fail after the pilot phase, with the same structural logic about the gap between demo conditions and operational reality","article_id":13655},{"reason":"Governance as a prerequisite for enterprise AI deployment — the same foundational argument applied to the broader AI agent context","article_id":13647},{"reason":"Examines the moment AI leaves pilot mode and exposes which organizations have real foundations versus slide-deck readiness — the same core tension as this article applied to enterprise AI broadly","article_id":13567}],"business_patterns":["Pilot-to-scale failure: AI performs well in controlled conditions and breaks down when exposed to full operational complexity","Tacit knowledge gap: organizations sustain efficiency through undocumented human judgment that cannot be converted to training data without deliberate effort","Fragmentation as rational accumulation: operational silos are not accidents but the sum of locally rational decisions made without central coordination","Technology amplification of existing dysfunction: AI does not fix broken processes; it executes them faster and at greater scale","Maturity gap as competitive differentiator: access to AI technology is commoditized; the ability to absorb it is not","Function repositioning through automation: as transactional work is absorbed by systems, the function's strategic mandate expands and its authority redistributes"],"business_decisions":["Whether to scale AI in procurement before or after redesigning underlying workflows and data architecture","How to assess the true state of data infrastructure and governance before committing to AI deployment","Whether to treat the 25–40% efficiency gain from AI procurement transformation as headcount reduction or capacity reallocation","How to redesign procurement roles so that human judgment is positioned at the points where it remains irreplaceable","Whether to invest in team preparation alongside technology deployment or sequence them separately","How to handle the governance of approval thresholds and spending levels that require human oversight versus automated processing"]}}