Blog / Other resources

Hours, story points or outcomes: how to price a software project in 2026

Time and materials, fixed price, story points or outcomes: how to price a software project in 2026, now that AI agents write part of the code.

What are the main software pricing models in 2026?

Model The client pays for What AI changes
Time and materials Hours Fewer hours for the same scope, so less revenue for the firm
Fixed price A scope AI cost and rework are the firm's risk
Dedicated team People per month The client asks why the team does not shrink
Outcome-based Results or units of finished work Firm and client share the AI savings

Fixed price or time and materials now that AI writes code?

  • Time and materials is fair only when the scope is unclear. With agents, every saved hour is lost revenue.
  • Fixed price protects the client, but the firm carries the AI cost and the rework.
  • Per unit of finished work keeps the flexibility of time and materials and the price certainty of a fixed price.

Should you price per story point?

No. Story points are a relative estimate for one team, not a unit of work. Mike Cohn of Mountain Goat Software warns against equating points to hours. Two teams give different points to the same change, and the team that bills the points also sets them. So the client cannot compare vendors, and the price per point moves the hours problem into the estimate.

What are examples of outcome-based pricing in IT services?

  • Per unit of finished work: a price per delivery point, billed for the work the client accepts.
  • Per transaction or case: common in business process outsourcing, for example a price per ticket closed.
  • Shared savings: the firm gets a part of a cost reduction that both sides measure.
  • In November 2026, FPT Software told Nikkei Asia that its US clients are moving from paying for engineering hours to paying for outcomes.

How do you choose?

If Then
The scope is unclear and short Time and materials, with a cap
The scope is clear and AI does a large part Per delivery point
The client wants one number Fixed price, quoted in delivery points
You run a long engagement Per delivery point, re-priced at renewal from the history

Common mistakes

  • Pricing per story point. The estimate becomes the invoice.
  • Keeping hourly rates as agents take over work. Revenue falls as you get better.
  • Outcome pricing with no shared measure. Disputes start at the first invoice.

How Pensero helps

Sources

Frequently asked questions

Hours, story points or outcomes: which is best in 2026?

Outcomes, measured as units of finished work, when the scope is clear. Hours only for short, unclear work.

Fixed price or time and materials with AI?

Neither alone. Quote per unit of finished work, so the client gets price certainty and the firm keeps the AI savings.

How do I calculate the cost per story point?

Divide the team cost for a period by the points it finished. But do not price on it: points are team-specific estimates, so the number cannot compare vendors.

What are the main IT outsourcing pricing models?

Time and materials, fixed price, dedicated team and outcome-based pricing.