Value pricing for AI-native delivery: what replaces time-and-materials

Value pricing for AI-native delivery: what replaces time-and-materials

Last updated: July 2026

Time-and-materials pricing survived four decades in professional services because the customer was buying labour. When the labour cost per unit of output dropped 5-10x for parts of an engagement in 2026, T&M stopped representing what the customer was buying and started representing what the provider was spending. Two very different things. The pricing conversation moved. This post is what the new conversation looks like — the mechanics of fixed-scope pricing when scope is credible, the mechanics of outcome-based pricing where the metric is clean, and the shrinking role T&M still plays for genuinely open-ended discovery work. It is a cluster child of our AI-native agency operating model pillar.

Key takeaways

  • T&M broke because it exposed the wrong number. When one senior engineer with an AI stack ships in a day what previously took a week, T&M invoices the day at the wrong hourly rate for the wrong deliverable.
  • Fixed-scope became the default because the estimation discipline caught up. The partner can commit to a scope and price honestly. The client gets an outcome, not an invoice.
  • Outcome-based pricing works where the metric is clean and attributable. Where it is, it is the fastest-growing pricing model in 2026. Where it is not, forcing it produces theatre.
  • T&M still fits open-ended discovery. Genuinely exploratory work where the scope legitimately cannot be nailed down at the start. Small share of engagements. Legitimate share.
  • The pricing conversation is a signal to the buyer about the partner. A partner that will only work T&M in 2026 is either hiding a variance problem or has not done the AI-native operating-model work. Neither is a good signal.

Why T&M broke

The classical services deal was: the customer buys a certain number of engineer-hours at a certain rate. The provider bills the hours. Both sides trust that the hours correspond to the output.

The correspondence held because the labour was the constraint. A senior engineer wrote code at a specific pace. Hours in, code out. The rate reflected the market for the engineer's skill. The unit of output — a working feature, a shipped integration — had a stable relationship to hours because the engineer's typing was most of the work.

The AI-augmentation shift broke the correspondence. The senior engineer is now producing 3-5x the output per hour on the parts where AI does the typing, and roughly the same on the parts where judgement dominates. The hour is no longer a stable unit relative to the output. Two things happen:

The customer notices the hours dropping. Not immediately, but eventually. When a T&M engagement that used to burn 40 hours a week starts burning 25 hours for more output, the customer asks why the invoice is smaller. Then they ask why the hourly rate was set for the pre-AI world. The rate conversation ends badly for the provider.

The provider notices the risk asymmetry. The provider is now delivering the same outcome at a fraction of the hours. Under T&M, the provider's revenue falls. But the provider still holds the risk of overrun, integration surprises, and the parts of the work AI does not compress. The provider is worse off than they were pre-AI. Providers respond by raising the hourly rate. Customers see the higher rate and negotiate down. Neither side is happy.

The T&M model does not survive both sides being unhappy. It survives when both sides trust the number. When the AI-augmentation shift breaks that trust, T&M breaks.

Fixed-scope, done right

Our main pricing model in 2026 is fixed-scope. The mechanics that make it work:

Honest estimation. From the estimation post: AI produces the first cut, senior engineer overrides the assumptions, the team commits to a scope and a number. Variance track record 70-90% within 10% of estimate.

Scoped exclusions in writing. Everything that is not in scope, named. Integrations to specific systems, feature variants, data cleanup work. If something is outside the fixed-scope wall, it is a change order.

Change order economics. Change orders are priced the same way as the initial scope — AI-first estimate, senior review, commit. Not billed at a T&M multiplier. This is what stops the "fixed-scope plus lots of change orders" pattern that used to make fixed-scope a fiction.

Milestone payments. Payment schedule follows delivery milestones, not calendar dates. The client pays for output, not elapsed time. A milestone that lands early gets paid early; a milestone that lands late gets paid late.

Capability transfer criteria. From the capability-transfer-default post. A portion of the final payment is tied to the transfer criteria being met. The engagement is not closed until the client team can run the system.

The result is a contract that both sides can trust. The client knows the maximum they will spend and the outcome they will get. The provider knows the revenue they will earn and the exit criteria they need to meet. Neither is surprised at the end.

Outcome-based pricing, done carefully

Outcome-based pricing ties a portion of the fee to a specific business metric. When the metric is clean, this is the fastest-growing pricing model in 2026 — clients like it because they pay for value, providers like it because their upside is uncapped when they deliver well.

The metric criteria that make it work:

Clean. The metric is a specific business number — conversion rate, revenue per user, cost per transaction. Not "customer satisfaction," not "productivity." Numbers that already exist in the client's dashboard, not new numbers invented for the contract.

Attributable. The change the partner ships is causally responsible for moving the metric. If the metric moves for reasons the partner did not cause (a marketing campaign, a competitor's price change, seasonal effect), the pricing model is not tracking the value of the work.

Baselined. The pre-engagement baseline is measured for enough time to be honest. Metrics have natural variance; a baseline of two weeks does not represent the underlying rate.

Timeboxed. The measurement window is finite. Six months, twelve months. Not "in perpetuity" — that is a licence deal, not an outcome-based delivery deal.

When those four conditions hold, outcome-based works. The mechanics: a base fee that covers the delivery cost with a modest margin, plus a bonus tied to metric movement. The bonus is a percentage of the metric-driven value, structured so the client pays more when they benefit more.

When any of the four conditions fail, outcome-based produces theatre. The pricing model exists, but neither side actually believes the number, so the base fee grows to cover the risk and the bonus becomes ceremonial. Better to use fixed-scope than to fake outcome-based.

Where T&M still fits

Genuinely open-ended discovery work. The scope cannot be nailed down at the start because the point of the engagement is to figure out what the scope should be. AI advisory, technology-strategy work, deep-dive research engagements.

T&M for this work is honest. The client pays for the discovery hours, gets a recommendation, decides what to do next. Neither side is pretending to know a scope that they do not. The hourly rate reflects the seniority of the person doing the discovery — usually a principal-level engineer or advisor, priced accordingly.

Small share of our engagements. Legitimate share. The pattern that fails is using T&M for delivery work where a fixed scope is possible but the partner does not have the estimation discipline to commit.

The pricing conversation as a signal

An enterprise evaluating a partner in 2026 can read the pricing conversation as a signal about the partner's operational maturity.

A partner that offers only T&M for delivery work has either not adjusted to the AI-augmentation shift or is hiding a variance problem. Neither is a good signal.

A partner that offers fixed-scope with a clean change-order process has the estimation discipline. Their variance track record is worth asking about.

A partner that offers outcome-based on specific engagements where the metric is clean is genuinely aligning their incentive with the client's. Their willingness to put revenue at risk is a signal of confidence.

A partner that offers all three — T&M for discovery, fixed-scope for delivery, outcome-based where the metric is clean — has the operational maturity to match the shape of the pricing to the shape of the work. This is what mature AI-native services firms look like in 2026.

The enterprise that reads the pricing conversation this way ends up with partners who match the actual shape of the engagement. The enterprise that treats pricing as a discount negotiation gets partners who are optimising for hours billed, not for value delivered. The former is where the AI-native shift is going. The latter is where the pre-AI professional services market was, and where it will not stay.

let's talk

Ready to build?

AI agents, data platforms, or cloud-native products — tell us what you're working on and we'll take it from there.