Buy outcomes, not solutions: the enterprise case for intent-native services

This HFS Point of View is for CIOs, sourcing leaders, and enterprise transformation leaders redesigning how they buy services to own business outcomes as AI absorbs execution.

As AI absorbs execution, value moves to defining the outcome and governing how it is reached. To capture this value, the CIO must change the legacy ways of buying IT solutions and start composing solutions around the business intent.

Every enterprise CIO has lived this meeting: The provider’s quarterly review shows every service level green, yet the number the business cares about has not moved. This gap is not just a delivery failure, and switching providers will not close it.

It is the signature of a buying model from a different era, where enterprises are boxed in by the activities providers sell, providers execute them, and translating activities into business outcomes is the enterprise’s unpaid job. AI now makes this model defunct, as agents absorb execution and value, moving to composing solutions around business intent. We call this intent-native services. In this PoV, we will unpack examples from our market conversations and our work with enterprises in HFS AI-First Deal Labs, showing that the appetite to buy differently is already ahead of the contracts being signed and how enterprises should change their operating model to enable intent-native services.

The way enterprises buy services is defunct

Everything in the traditional model, from time-and-materials rates to managed services agreements to output-based pricing, prices human effort. Delivery methods have evolved, but the economics underneath have not, and the dissatisfaction is now measurable: Two-thirds of enterprise leaders expect to change the mix, scope, delivery, and commercial model of their providers.

The instinct is to blame providers, but the evidence points to four structural gaps (intent, orchestration, operational, and accountability) in how enterprises buy (see Exhibit 1). These gaps live in the buying model rather than in any supplier, which is why a better supplier cannot close them.

Exhibit 1: Four structural gaps prevent the current services model from delivering business outcomes

Source: HFS Research, survey of 505 enterprise business and IT leaders across the Global 2000, 2026

Intent-native services abstract orchestration and execution

Intent-native services are oriented around the business outcome an enterprise wants, not the activities a provider performs to deliver it. The enterprise declares the intent, meaning the outcome it needs together with the constraints, risk appetite, and success conditions that bound it. Everything required to meet the intent is abstracted beneath it: a delivery ecosystem orchestrating across platforms, agents, and providers.

The defining feature is the boundary between what the enterprise sees (see Exhibit 2). Above the line sit intent and governance, which remain visible to the business. Below it sit orchestration and execution, whose complexity is hidden from the business consuming the service, much as a cloud service hides its infrastructure. not ask the enterprise to specify or manage the work; it asks the enterprise to define and govern the outcome and holds the ecosystem accountable for reaching it.

Exhibit 2: The intent-native services operating model

Source: HFS Research, 2026

Enterprises need to reorient the buying process around business intent

The reorientation is to make the business outcome, rather than the solution, the unit the firm works in. In practice, it is three moves (see Exhibit 3):

• First, the firm defines the intent as a measurable business result before any solution is on the table, so the work begins with a goal like improving sales efficiency by a set amount rather than implementing a new application.
• Second, it composes the solution from whatever actually reaches that intent, which may be a platform, a process change, better data, new incentives, or removing a system that is in the way, and which deliberately ignores the provider’s own P&L structure.
• Third, it owns the realized outcome, so that “done” means the number moved and not that the system went live, with pricing and accountability following the result. Services-as-Software™ is the engine that delivers all of this.

The legacy answer to an aging core need not be a multi-year migration to SAP or Oracle. If what the business needs is decision-ready and audit-ready numbers at any moment, whatever system holds the ledger, then the composed solution is to keep the existing ledger in place as a headless system of record, run an agentic close and reporting layer over it, and drop the migration. The migration, however fast or slow, was never the outcome. It was an artifact the firm assumed it had to build.

Exhibit 3: Intent-native services define the, compose the solution, and own the outcome

Source: HFS Research, 2026

Intent-native services are already working in live enterprise engagements

Based on our market conversations and our work with enterprises in HFS AI-First Deal Labs reveals that enterprise appetite to buy differently is already ahead of the contracts being signed now, each following the same arc from the current model to defining the intent, composing the solution, and owning the outcome (see Exhibit 4).

Exhibit 4: Examples of enterprise engagements that demonstrate the intent-native model across industries and service lines

Source: HFS Research, 2026

Adoption happens through recurring trigger points, not an overnight transformation

Moving to intent-native services is not an overnight change. It alters what is contracted, how solutions are composed, how performance is measured, and how accountability is distributed. No enterprise can rewrite all of it at once, and attempting to make this transformation would create more risk than the model removes. Adoption instead happens at specific moments when those structures are already open for decision. HFS identifies such trigger points in Exhibit 5.

Exhibit 5: Trigger points give enterprises the opening to shift to intent-native services

Source: HFS Research, 2026

The plays differ, but the discipline is constant. Start where outcomes are easy to define and errors stay contained, then carry the proven model into other areas. The triggers also compound, because an enterprise that writes its intents in this year’s strategy cycle meets next year’s renewals knowing what to contract for, and that compounding is the real first-mover advantage.

Enterprises must control orchestration, directly or through a neutral partner

No participant in today’s supply ecosystem can deliver intent-native outcomes on its own. The reason is structural. The role calls for four capabilities at once: influence over the technology stack deep enough to stand behind the platform, delivery embedded enough to own the workflow, data and context the enterprise can build on, and governance that lets the enterprise verify before it delegates. No incumbent holds all four.

The supply side is converging on the role from two orthogonal directions (see Exhibit 6).

Exhibit 6: Intent orchestration is the unclaimed center every supply cohort is converging on

Source: HFS Research, 2026

Product-native players, the platform vendors, hyperscalers, and AI foundation labs, hold the lower stack and are building delivery and services arms to move up toward owning outcomes. Services-native players, the global service providers, and enterprises themselves hold the outcome and the context and are building software and product IP to move toward influence over the stack. Foundation labs standing up deployment units and a provider like HCLTech evolving its software arm are the same motion from different sides.

Neutrality is an advantage, so any cohort whose influence rests on its own stack pays a penalty as an orchestrator, which favors independent providers and enterprises.

The Bottom Line: Redesign how you buy services now, or inherit an operating model assembled from vendor defaults.

The shift from execution to intent is already underway. What remains open is who sets its terms. Left to default, the enterprise’s operating architecture is set by the platforms and providers it happens to buy from. Designed deliberately, it becomes an asset in its own right: the outcomes the enterprise declares, the intent it governs, and the orchestration it owns or co-owns.

That makes this an accountability decision before it is a technology one. The enterprises that move first will decide three things: which outcomes to own, how to share and delegate accountability as trust is earned, and whether to hold orchestration or hand it over. That choice will compound an advantage that the rest spend the decade trying to close. The clock started when execution became software. The only choice left is whether to lead the redesign or inherit someone else’s.