Pricing & packaging
Helena Marsh10 min read8 views

Pricing AI builds: from hourly to outcome-based

A pricing ladder for AI builds — hourly, fixed-scope, value-based and outcome-based — with the dollar ranges, margin math and risk controls to move up it without torching trust.

Updated on June 18, 2026

A calculator, pen and financial statements on a desk, representing agency pricing models
A calculator, pen and financial statements on a desk, representing agency pricing models
On this page

Quick Answer

Most agencies pricing AI builds are stuck selling hours when they should be selling outcomes. The fastest margin gains come from climbing a four-rung ladder — hourly ($120–$250/hr), fixed-scope ($40K–$250K), value-based (price set against the client's expected gain), and outcome-based (you share in measured results). Each rung trades delivery risk for margin upside. Move up one rung at a time, only after you can estimate the work within ±15%, and always anchor the price to a number the client already believes about their own business.

Why hourly pricing caps your agency

Hourly billing feels safe because it transfers all estimation risk to the client. It also quietly caps your business. When you bill time, your revenue is bounded by capacity — every dollar requires a staffed hour — and your incentive is misaligned with the client, who wants the work done faster while you are paid to take longer.

AI builds make this worse. A model-assisted team can compress a 400-hour integration into 120 hours. Under hourly billing, that efficiency is a 70% revenue cut. You are penalized precisely for the leverage that makes your agency valuable. The agencies winning right now have decoupled price from hours so that getting faster grows margin instead of shrinking the invoice.

That doesn't mean hourly has no place. It is the right instrument for genuinely open-ended discovery, staff augmentation, and retainers where scope is fluid. But it should be the floor of your pricing, not the ceiling. The strategic move is to treat hourly as a fallback for ambiguity and to convert every engagement you understand well into a fixed or value-based price.

There's a second, quieter cost to hourly billing: it commoditizes you. When the client sees a rate, they compare it to other rates — including offshore rates a fraction of yours. When the client sees an outcome, they compare it to the value of that outcome. The first conversation is a race to the bottom; the second is a negotiation about a share of upside. The pricing model you choose decides which conversation you're having.

The four-rung pricing ladder

Think of pricing as a ladder you climb as your estimation confidence and proof improve. Each rung moves risk from the client onto you, and pays you for absorbing it.

Scroll to see more

ModelTypical rangeWho carries scope riskGross margin targetUse when
Hourly / T&M$120–$250 / hrClient45–55%Discovery, staff aug, fluid scope
Fixed-scope$40K–$250K / projectAgency50–65%Scope is knowable within ±15%
Value-based$75K–$500K / projectShared60–75%Client can quantify the upside
Outcome-basedBase + 10–30% of resultAgency (mostly)65–80%+You can measure and influence the metric

The ranges assume a US/EU blended cost of $85–$130/hr. Offshore-heavy teams will see the same percentage margins on lower absolute prices. The key insight: each step up the ladder raises your margin ceiling by roughly 10–15 points, but only if your estimates hold.

Hourly and time-and-materials

Bill in half-day or full-day blocks rather than raw hours where you can — it reduces micro-accounting and signals seniority. Cap weekly hours in the contract so a "T&M" engagement can't silently become an unbounded liability. Use hourly deliberately, not by default: it's the right tool when neither you nor the client can yet describe the finished thing.

Fixed-scope

Fixed price rewards you for estimation skill and efficiency. The trap is scope creep: a fixed price with an unfixed scope is just a discount you didn't know you gave. Protect it with a written scope, a change-order clause, and a contingency buffer (see below). Done well, fixed-scope is where most agencies should spend the bulk of their delivery — it's predictable for the client and rewards your efficiency directly.

Value-based

Here you stop pricing the work and start pricing the result the work unlocks. If an AI intake agent saves a clinic 6,000 staff-hours a year, the build is worth a slice of that — not the 220 hours it took you. Value pricing requires a discovery conversation that surfaces a number the client already believes. The price then becomes a fraction of that number, which makes it feel like an obvious investment rather than a cost.

Outcome-based

The top rung. You take a smaller base fee plus a share of a measured outcome — leads generated, hours saved, revenue influenced. Margins can exceed 80% when it works, but you are now exposed to factors outside your control. Only the most mature agencies should price here, and only on metrics they can directly move. Never sign an outcome deal on a metric the client's own team can sabotage or that depends on their marketing, their sales follow-through, or their data hygiene.

How to estimate an AI build without getting burned

Outcome and value pricing both rest on one skill: estimating the build accurately. AI work has more variance than traditional development because model behavior is probabilistic and integration surfaces are messy.

Decompose every build into four cost buckets and estimate each as a range:

  • Discovery & data — 10–20% of total hours. Auditing data quality, access, and edge cases.
  • Core build — 40–55%. Prompts, pipelines, integrations, UI.
  • Evaluation & hardening — 20–30%. This is where AI projects overrun. Budget for it explicitly.
  • Handover & enablement — 5–10%. Docs, training, runbooks.

Then apply a contingency multiplier based on how novel the work is.

Scroll to see more

ConfidenceDescriptionContingencyPricing model fit
HighDone this 3+ times+10%Fixed, value, outcome
MediumFamiliar, new domain+20–25%Fixed, value
LowGenuinely novel+35–50%Hourly or phased

A 300-hour core build at medium confidence carries ~70 hours of contingency. If you can't justify a contingency under 25%, you are not ready to fix the price — sell a paid discovery sprint first ($8K–$20K) to buy down the uncertainty, then quote the build. Discovery sprints are not a tax on the client; they are the cheapest insurance both sides will ever buy against a mispriced project.

A useful discipline: estimate every bucket twice — once for the "everything goes well" case and once for the "realistic friction" case — and price off the second. The gap between the two numbers is your risk, and pricing off the optimistic figure is how agencies turn profitable projects into break-even ones.

Packaging the price so clients say yes

How you present the number matters as much as the number. Three rules:

  1. Always show three options. A single price invites a yes/no. Three tiers (e.g. $60K / $95K / $140K) invite a which one — and the middle tier is where most buyers land. The top tier reframes the middle as reasonable.
  2. Anchor to the client's own numbers. "This recovers roughly 5,000 staff-hours a year" beats "this costs $95,000" because it lives in their P&L, not yours.
  3. Separate price from payment. A $120K build can be three $40K milestones, easing cash-flow objections without discounting.

Clients don't resist high prices. They resist prices they can't connect to a result they care about. The job of packaging is to do that connecting for them.

The three-tier structure also protects your margin in negotiation. When a client pushes back on price, you don't discount — you move them to a smaller tier with less scope. The price and the value stay coupled, which trains the client to see your pricing as principled rather than padded.

Running the value-pricing discovery conversation

You cannot value-price without a number, and the number has to come from the client. The discovery conversation is where you find it. Ask, in order:

  • What does this problem cost you today? In hours, headcount, churn, or missed revenue — push until you get a figure.
  • What happens if you do nothing for another year? This quantifies urgency and frames inaction as the expensive option.
  • What would success be worth? Get the client to state the upside in their own words, so it's their number, not yours.

By the end you should be able to say: "So this is costing you roughly $X a year, and solving it is worth roughly $Y." Your price is then a comfortable fraction of $Y. If the client can't or won't quantify, that's your signal to fall back down the ladder to fixed-scope — value pricing without a value number is just guessing.

Common pricing mistakes

  • Quoting before discovery. A price given in the first call is a price given without information. Buy the information first.
  • Anchoring on cost. "It'll take us 200 hours so it's $36K" tells the client exactly how to negotiate you down. Lead with value, mention hours never.
  • One number, take it or leave it. Always three tiers.
  • No change-order clause. Without it, every "small addition" is unpaid work that eats the margin you carefully estimated.
  • Hourly by habit. Defaulting to time-and-materials because it's easy is the single most expensive habit in the agency world.

Contract guardrails

A good price is only as durable as the contract protecting it. Three clauses do most of the work: a written scope (what's in, what's explicitly out), a change-order process (any addition is re-quoted, not absorbed), and a milestone payment schedule (you're never carrying more than one unpaid milestone of risk). For value and outcome deals, add a measurement clause that defines exactly how the result is calculated and over what window — ambiguity here is where outcome deals go to die.

Migrating existing clients up the ladder

You don't have to wait for new clients to change how you price. Existing relationships are the easiest place to climb, because trust already exists. The move is to reframe the next engagement, not to renegotiate the current one. When a retained hourly client brings their next project, propose it as a fixed-scope or value-priced piece of work alongside the usual T&M option, and let them choose. Most will pick the fixed price for the predictability. Each migrated engagement is a proof point you can carry into the next, and within a year the bulk of your book can shift off pure hourly without a single uncomfortable "we're raising our rates" conversation.

A worked example

A 40-person logistics company wants an AI document-extraction tool. Hourly, you'd estimate ~260 hours at $160 = ~$41,600, with you absorbing every efficiency you find.

Reframed as value: the tool eliminates ~4 FTE-equivalents of manual data entry, worth ~$220K/year in loaded cost. A value price of $115K is ~6 months' payback for the client and nearly 3× your hourly figure — for the same work. The difference isn't the build; it's which number you anchored to. Package that $115K as three tiers ($85K / $115K / $155K), structure it as four milestones, and tie a small bonus to a measured accuracy threshold, and you've climbed three rungs of the ladder on a single deal.

Sources

  • Software Pricing Partners, "Value-Based Pricing in Professional Services" (2024).
  • Implisit / HubSpot, "B2B Proposal Win-Rate Benchmarks" (2023).
  • Pricing Council, "Outcome-Based Contracts in IT Services" (2024).
  • Bench / Bonsai, "Agency Rate & Margin Report" (2023).
  • McKinsey, "The Economic Potential of Generative AI" (2023).
Helena Marsh

Written by

Helena Marsh

Helena Marsh advises software agencies on pricing, packaging and margin. She spent a decade running delivery and commercial strategy at boutique consultancies billing $3M–$12M.

Frequently asked questions

When should an agency move from hourly to fixed pricing?

When you can estimate a build within roughly ±15% and your contingency buffer is under 25%. If you can't hit that confidence, sell a paid discovery sprint ($8K–$20K) first to buy down the uncertainty, then quote a fixed price.

Isn't outcome-based pricing too risky for most agencies?

For most, yes — it should be the last rung you climb. Only price on outcomes you can measure and directly influence, and always keep a base fee that covers your delivery cost so a bad month can't put you underwater.

How big should my contingency buffer be on an AI build?

10% for work you've done several times, 20–25% for familiar work in a new domain, and 35–50% for genuinely novel builds. AI evaluation and hardening is the most common source of overruns, so budget that bucket explicitly.

How do I justify a value price that's 2–3× my hourly estimate?

Anchor to the client's own numbers — hours saved, revenue influenced, FTEs avoided. When the price is a fraction of a gain the client already believes in, the multiple over your internal hours becomes irrelevant to the decision.