For most of the last two decades, the dominant commercial model in software outsourcing was time and materials. The client bought hours. The vendor sold them. Risk, accountability and ownership stayed largely on the buyer's side of the table. It was a model designed for scarcity of engineering talent, not for maturity of software delivery.
The market is moving, quietly, but decisively, toward output-based and accountability-based engagements. The shift sounds commercial, but it is operational. It changes what a vendor is, what a client expects, and what a partnership has to look like to work.
Why hours were always the wrong unit
Hours measure activity. Activity is not delivery. A team can be fully booked, fully invoiced and fully ineffective. In a time-and-materials model, the financial incentive sits on the wrong side of the relationship: the vendor is paid more when delivery slows, not less. Even with good intent on both sides, the structure pulls against the outcome.
The deeper problem is ownership. When the contract is hours, the vendor's obligation ends when the timesheet does. Decisions, trade-offs and quality thresholds remain the client's responsibility, including the ones the client lacks the operational depth to make well.
A vendor paid for hours is, by design, indifferent to outcomes. A partner accountable for outcomes is, by design, structured around them.
What output-based delivery actually means
Output-based delivery is not the same as fixed price. Fixed price tries to predict scope; output-based delivery tries to commit to value. The unit becomes something the buyer can recognize as progress: a released capability, a measurable improvement in stability, a closed-out modernization phase, a working AI workflow embedded in operations.
Operationally, this requires:
- A clear definition of what "done" looks like, in business terms, not ticket counts.
- A team stable enough to carry the work across the full delivery arc.
- A vendor willing to be accountable for trade-offs, not just execution.
- Governance that operates at the cadence of delivery, not the cadence of contracts.
Why this changes the vendor relationship
Output-based delivery cannot be staffed with rotating contractors. It requires continuity. It cannot be governed from a distance. It requires embedded collaboration. It cannot be defended through scope arguments. It requires shared ownership of the outcome.
This is incompatible with the commodity outsourcing model. It is the reason mature European organizations are increasingly looking past hourly outsourcers toward partners that behave as an operational extension of the organization, long-term, accountable and governed inside European contractual frameworks.
The European governance dimension
In European environments, accountability is not only commercial; it is contractual and regulatory. Output-based engagements work particularly well here because they collapse the distance between the work and the obligation. A single accountable partner under EU law, with clear continuity terms and operational ownership, fits the way European boards already think about risk.
This is the model we operate: dedicated engineering teams with European delivery oversight, structured to take ownership of outcomes rather than to sell hours against a backlog.
Closing
The vendor relationship that suited the last cycle is not the one that suits this one. As AI compresses execution cost and raises the importance of judgement, the buyers that benefit most will be the ones who stop buying hours and start buying accountability. The change is quiet, but the consequences are not.
