{"version":"1.0","type":"agent_native_article","locale":"en","slug":"why-ai-contracts-keep-paying-hours-when-value-lies-elsewhere-mqxss83t","title":"Why AI Contracts Keep Paying for Hours When the Value Lies Elsewhere","primary_category":"innovation","author":{"name":"Lucía Navarro","slug":"lucia-navarro"},"published_at":"2026-06-28T12:02:24.622Z","total_votes":86,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/why-ai-contracts-keep-paying-hours-when-value-lies-elsewhere-mqxss83t","agent":"https://sustainabl.net/agent-native/en/articulo/why-ai-contracts-keep-paying-hours-when-value-lies-elsewhere-mqxss83t"},"summary":{"one_line":"Enterprise AI adoption stalls not because of technology but because time-and-materials contracts misalign vendor incentives with client outcomes, and outcome-based contracting is the structural fix.","core_question":"Why do most enterprise AI contracts reward time spent rather than value generated, and what does a better contract architecture look like?","main_thesis":"The dominant contracting models for AI (time-and-materials and fixed-price) were designed for linear software delivery and are structurally incompatible with AI's value logic. Outcome-based contracting realigns incentives, forces pre-contractual strategic clarity, and makes previously invisible costs visible — but requires vendors with genuine delivery conviction and clients willing to define business outcomes before selecting technology."},"content_markdown":"## Why AI Contracts Keep Paying for Hours When the Value Lies Elsewhere\n\nThe greatest source of friction in enterprise artificial intelligence adoption is not technical. It does not reside in the models, nor in the quality of the data, nor in computing capacity. It lies in the contract. While organisations invest hundreds of millions in AI implementations expecting structural returns, the majority continue to sign agreements that reward time invested, not impact generated. That misalignment is not an administrative detail: it is the root cause of why so many AI initiatives remain trapped between the promising pilot and the operational scale that never arrives.\n\nMcKinsey's most recent report on the state of AI confirms this with uncomfortable precision: adoption has spread, but scaling challenges persist, and the strongest correlation with real impact lies not in technological investment but in the redesign of workflows. Stated in economic terms: companies are paying for installation when they should be paying for transformation.\n\nOutcome-based contracting is not a trend. It is the structural response to an incentive architecture problem that traditional models are incapable of resolving.\n\n## The Problem Is Not the Vendor, It Is the Logic of the Contract\n\nTime and materials contracts, along with fixed-price agreements, were born to manage software delivery in contexts where deliverables were definable, timelines predictable, and value relatively linear in relation to effort. AI breaks all three conditions.\n\nAn AI system that automates incident management in infrastructure does not deliver a module. It delivers a reduction in resolution time, a drop in operational costs, a reduced dependence on on-call personnel, and eventually a reorganisation of the operations team. None of those outcomes appear on an invoice for hours. And none of them can be attributed with precision to a specific project milestone.\n\nThe result is predictable: the vendor charges for what it can measure, which is hours. The client pays for something it expected but which the contract never formally promised. When the ROI does not materialise, no one is technically responsible because the contract never required it.\n\nThere are three structural failures in this logic. The first is the absence of any correlation between the input and the value generated: spending more on consulting or on licences does not necessarily produce greater impact. The second is the lack of accountability mechanisms, because without a contractually defined outcome, the vendor has no incentive to pursue it. The third, and most frequently overlooked, is the total cost of ownership that traditional contracts render invisible: the management of organisational change, the team's AI literacy, the reconversion of processes, and the costs that disappear when the solution works well — such as the personnel or the software that the AI replaces. All of that remains off the balance sheet, even though it determines whether the investment was profitable.\n\n## The Logic of an Outcome-Oriented Contract\n\nAn outcome-based contract is not simply one in which the vendor earns a bonus if things go well. Its architecture is more precise and more demanding for both parties.\n\nThe starting point is the collaborative definition of the indicators that matter — not technical ones, but business ones: reduction in operational costs, an increase in the first-contact resolution rate with the client, a decrease in cycle time across the supply chain. On the basis of those indicators, verified baselines are established, with an agreed measurement methodology, and the attribution logic is constructed: what portion of the outcome can be reasonably connected to the AI solution and under what conditions.\n\nPayment is structured in layers. A fixed base covers the vendor's minimum operating costs. A variable component is activated when results surpass defined thresholds. In the most sophisticated implementations, variance bands are established — what some call tolerance corridors — within which the vendor absorbs downside risk but also captures upside value.\n\nThis design changes the power dynamic in the commercial relationship. The vendor ceases to be a task executor and becomes a partner with exposure to the outcome. That shift in position is not rhetorical: it has consequences for how teams are allocated, how quickly a model performance problem is responded to, and how much continued investment the vendor is willing to make in the account.\n\nFor this to work, the vendor must possess capabilities that traditional models never demanded. It needs consultants who understand the client's business before discussing technology. It needs engineers who build while the scope is being defined, not afterwards. And it needs the infrastructure to operate the model in production continuously, including governance of inference costs and monitoring of model performance degradation over time.\n\n## The Scaling Error That Repeats Itself Most Often\n\nThere is a pattern of failure in AI adoption that recurs with sufficient consistency to be considered structural: organisations do not know where to place their focus and oscillate between two equally costly extremes.\n\nSome bet on problems that are too narrowly scoped. They build an agent to automate vendor spend management without considering that the real problem lies across the entire procurement chain. The result is a solution that functions within its silo and cannot scale because it was not designed to connect with the processes that give it context.\n\nOther organisations attempt to optimise everything at the same time and without stages. They seek to transform operations at scale without having demonstrated the value model in a contained segment first. The result is a project that consumes resources for years, generates progress reports, and produces no observable changes in the indicators that matter to the board.\n\nWhat connects both extremes is the absence of an operating model before the technology is selected. Organisations that manage to scale AI in a sustained manner work with two simultaneous processes: process redesign and data and technology architecture. Not in sequence, but in parallel. And what keeps those two processes aligned is change management, organisational strategy, and product management as a permanent discipline.\n\nThis is the most compelling argument in favour of outcome-based contracting: it forces that clarity to exist before the contract is signed. A vendor that accepts being measured by the result needs to understand the process the client wants to improve. That pre-contractual conversation holds more strategic value than many subsequent months of consulting.\n\n## When the Right Incentive Builds the Right Partner\n\nOutcome-based contracting reorders who captures value in an AI implementation and how. But it also reveals something about vendors that very few organisations analyse before signing.\n\nA vendor operating under this logic must absorb risk. To absorb risk, it needs conviction in its own delivery capacity. That conviction cannot be merely commercial: it must be backed by technical architecture, by a history of execution, and by internal governance that allows it to manage model quality in production over months or years — not only at the moment of launch.\n\nFew vendors possess that capacity today. And that scarcity has implications for buyers: the market of vendors genuinely committed to outcomes is smaller than it appears if one reads only sales literature. Filtering who can actually operate under this model and who is simply announcing it as a commercial differentiator requires asking precisely the questions that outcome-based contracting forces both parties to answer before signing.\n\nFrom the perspective of value distribution, this model also possesses a virtue that traditional contracts do not: it makes visible what previously remained off the balance sheet. The costs of organisational change, the investment in training, the systems that become redundant, the personnel that are reassigned — all of that becomes part of the shared value analysis between client and vendor. That visibility does not guarantee equity, but it does eliminate the possibility that the vendor's success and the client's success operate in parallel universes.\n\nWhen incentives are aligned around the outcome, the centre of gravity of the commercial relationship shifts from cost management to the maximisation of return. That difference is not semantic. It is what determines whether enterprise AI produces verifiable impact or simply produces projects.","article_map":{"title":"Why AI Contracts Keep Paying for Hours When the Value Lies Elsewhere","entities":[{"name":"McKinsey","type":"institution","role_in_article":"Cited as source confirming that AI scaling challenges persist and that workflow redesign correlates more strongly with impact than technological investment."},{"name":"Lucía Navarro","type":"person","role_in_article":"Author of the article."},{"name":"Time-and-materials contracts","type":"technology","role_in_article":"Dominant contracting model critiqued as structurally incompatible with AI value delivery."},{"name":"Outcome-based contracting","type":"technology","role_in_article":"Central proposed solution; the structural alternative to traditional AI contracting models."},{"name":"Enterprise AI","type":"market","role_in_article":"The adoption context in which the contracting problem manifests and where the proposed solution applies."}],"tradeoffs":["Fixed base payment (vendor cost coverage) vs. variable component (outcome-linked upside) — balances vendor viability with client accountability.","Narrow problem scope (faster to deploy, easier to measure) vs. broad transformation scope (higher potential value, higher execution risk).","Vendor absorbs downside risk in tolerance corridors vs. vendor captures upside value — requires vendor conviction backed by technical architecture.","Pre-contractual clarity investment (time-consuming, requires business analysis) vs. faster contracting (lower upfront cost, higher probability of misaligned outcomes).","Outcome attribution precision (requires agreed methodology) vs. simplicity of measurement (easier to administer but may not reflect true causal contribution of AI)."],"key_claims":[{"claim":"The strongest correlation with real AI impact lies in workflow redesign, not technological investment (citing McKinsey).","confidence":"high","support_type":"reported_fact"},{"claim":"Most enterprise AI contracts still reward time invested, not impact generated.","confidence":"high","support_type":"reported_fact"},{"claim":"When ROI does not materialize under traditional contracts, no one is technically responsible because the contract never required it.","confidence":"high","support_type":"inference"},{"claim":"Outcome-based contracting forces strategic clarity before the contract is signed, making the pre-contractual conversation more valuable than many subsequent months of consulting.","confidence":"medium","support_type":"editorial_judgment"},{"claim":"Few vendors today possess the technical architecture, execution history, and production governance required to genuinely operate under outcome-based risk.","confidence":"medium","support_type":"editorial_judgment"},{"claim":"Organizations that scale AI sustainably run process redesign and data/technology architecture in parallel, not in sequence.","confidence":"medium","support_type":"inference"},{"claim":"The total cost of ownership in AI — change management, AI literacy, process reconversion, replaced systems — is systematically invisible in traditional contracts.","confidence":"high","support_type":"inference"},{"claim":"Outcome-based contracting changes the vendor's position from task executor to partner with exposure to the outcome, affecting team allocation and continued investment decisions.","confidence":"medium","support_type":"editorial_judgment"}],"main_thesis":"The dominant contracting models for AI (time-and-materials and fixed-price) were designed for linear software delivery and are structurally incompatible with AI's value logic. Outcome-based contracting realigns incentives, forces pre-contractual strategic clarity, and makes previously invisible costs visible — but requires vendors with genuine delivery conviction and clients willing to define business outcomes before selecting technology.","core_question":"Why do most enterprise AI contracts reward time spent rather than value generated, and what does a better contract architecture look like?","core_tensions":["Vendors are incentivized to measure and charge for inputs (hours, licenses) while clients expect and need outputs (operational transformation, cost reduction).","Outcome-based contracts require pre-contractual strategic clarity that most organizations lack before they engage a vendor.","The market of vendors capable of genuine outcome-based risk absorption is smaller than buyer demand, creating a filtering problem disguised as a pricing negotiation.","Scaling AI requires organizational change management as a permanent discipline, but most AI budgets and contracts treat it as a one-time project cost.","Attribution logic — determining what portion of a business outcome is causally connected to the AI solution — is technically and commercially contested."],"open_questions":["How should attribution logic be designed when AI is one of several simultaneous operational changes affecting the same KPI?","What governance structures allow vendors to monitor and respond to model performance degradation in production over months or years without triggering contract renegotiation?","How do SMEs, which lack the procurement sophistication of large enterprises, access outcome-based contracting structures without being exposed to vendor opportunism?","What does a credible vendor capability assessment look like before signing an outcome-based contract — what specific questions reveal genuine delivery conviction vs. commercial positioning?","As more vendors adopt outcome-based language, how do buyers distinguish structural commitment from marketing differentiation?"],"training_value":{"recommended_for":["Chief Procurement Officers and legal teams structuring AI vendor agreements.","CFOs and finance teams evaluating AI investment ROI and total cost of ownership.","CIOs and CTOs selecting AI vendors and designing implementation governance.","Strategy and transformation consultants advising on enterprise AI programs.","AI vendors designing their commercial and delivery models.","Business agents trained to reason about technology investment, vendor management, and value capture."],"when_this_article_is_useful":["When evaluating or renegotiating an AI vendor contract.","When diagnosing why an AI pilot has not scaled to operational deployment.","When building a procurement framework for enterprise AI engagements.","When assessing vendor capability beyond technical specifications.","When designing accountability mechanisms for AI ROI measurement.","When advising an organization on AI operating model design before technology selection."],"what_a_business_agent_can_learn":["How to diagnose whether an AI initiative's failure is contractual rather than technical.","The three structural failures of traditional AI contracts and how to identify them in existing agreements.","The architecture of an outcome-based contract: KPI definition, baseline verification, attribution logic, and layered payment structure.","How to filter vendors by genuine outcome-risk capacity rather than by technology features or sales claims.","Why process redesign and technology architecture must run in parallel for AI to scale, and how contracting structure enforces or undermines that parallelism.","How to make total cost of ownership visible in AI contracts, including change management and redundant system costs."]},"argument_outline":[{"label":"1. The real bottleneck","point":"The primary friction in enterprise AI scaling is contractual, not technical. Models, data, and compute are no longer the binding constraint.","why_it_matters":"Reframes where organizations should focus diagnostic energy when AI initiatives stall."},{"label":"2. Why traditional contracts fail AI","point":"Time-and-materials and fixed-price contracts assume definable deliverables, predictable timelines, and linear value — all three assumptions break down with AI systems.","why_it_matters":"Explains structurally why vendors charge for hours while clients expected transformation, and why no one is technically accountable when ROI doesn't materialize."},{"label":"3. Three structural failures","point":"(a) No correlation between input spend and value generated; (b) no accountability mechanism without a contractually defined outcome; (c) total cost of ownership — change management, AI literacy, process reconversion — remains off the balance sheet.","why_it_matters":"Gives buyers a diagnostic checklist to identify where their current contracts are exposed."},{"label":"4. Architecture of an outcome-based contract","point":"Starts with collaborative definition of business KPIs, establishes verified baselines with agreed attribution logic, and structures payment in layers: fixed base + variable component + tolerance corridors for downside/upside sharing.","why_it_matters":"Provides a concrete design template, not just a principle."},{"label":"5. The scaling failure pattern","point":"Organizations oscillate between over-narrow scope (silo solutions that can't connect to adjacent processes) and over-broad ambition (transform everything at once without a proven value model). Both fail for the same reason: no operating model before technology selection.","why_it_matters":"Identifies the most common and costly execution error in AI programs."},{"label":"6. Vendor filtering as a buyer skill","point":"The market of vendors genuinely capable of operating under outcome-based risk is smaller than sales literature suggests. Buyers must ask the questions that outcome-based contracting forces before signing.","why_it_matters":"Shifts procurement from feature comparison to capability and conviction assessment."}],"one_line_summary":"Enterprise AI adoption stalls not because of technology but because time-and-materials contracts misalign vendor incentives with client outcomes, and outcome-based contracting is the structural fix.","related_articles":[{"reason":"Directly complementary: examines why AI budgets reflect operational bets and why most AI initiatives stall before generating measurable value — the same scaling failure this article diagnoses from the contracting angle.","article_id":14231},{"reason":"Addresses the automation-without-redesign failure pattern, which this article identifies as the structural error that outcome-based contracting forces organizations to avoid before signing.","article_id":14259},{"reason":"Documents the enterprise AI deployment gap — widespread adoption with low executive visibility into what has been deployed — which is a symptom of the accountability absence this article attributes to traditional contracts.","article_id":14361},{"reason":"The data readiness gap (97% have AI projects, 5% have usable data) is a precondition problem that outcome-based contracting surfaces during the pre-contractual baseline-setting phase described in this article.","article_id":14241}],"business_patterns":["Incentive misalignment as the root cause of adoption failure — a pattern where the contracting structure, not the technology, determines whether value is captured.","Pilot-to-scale gap — AI initiatives that demonstrate value in pilots but cannot transition to operational scale due to structural rather than technical barriers.","Invisible total cost of ownership — costs that only become visible when the solution works (or fails), systematically excluded from traditional contract scopes.","Vendor capability filtering — the gap between vendors who announce outcome-based models as a differentiator and those who can actually execute under that risk structure.","Parallel workstream requirement — organizations that scale AI run process redesign and technology architecture simultaneously, not in sequence."],"business_decisions":["Choose contracting model before selecting AI vendor or technology stack.","Define business KPIs and verified baselines collaboratively with the vendor before signing.","Audit current AI contracts for the three structural failures: input-value decoupling, absence of accountability mechanisms, and invisible total cost of ownership.","Filter vendors by their capacity to absorb outcome risk, not just by their technology capabilities or sales claims.","Run process redesign and data/technology architecture in parallel, not sequentially.","Establish an operating model before technology selection to avoid both over-narrow and over-broad scoping errors.","Include change management, AI literacy investment, and redundant system costs in the shared value analysis with the vendor."]}}