Unit Rate Pricing
Definition
Unit Rate Pricing
Unit rate pricing multiplies an agreed rate by a counted quantity of a defined unit of work, and nothing else enters the invoice. Defining the unit is the whole job, because the rate can always be renegotiated and the unit usually cannot.
It is the parent structure behind most output-priced outsourcing — per transaction, per ticket, per minute and per document are all unit rates with a particular unit chosen.
The discipline is unglamorous — a unit has to be countable by a system, stable in effort, and bounded by a written list of what sits inside and outside it.
Buyers who spend their negotiating energy on the rate and none on the unit usually get the price they wanted — and then pay for a second stream of work nobody classified.
Key takeaways
- A good unit is system-countable, effort-stable and bounded by a written scope.
- Inclusions and exclusions matter more commercially than the rate itself.
- Rates should be supported by a cost build-up, not only by market comparison.
- Volume assumptions belong beside the rate, since fixed cost recovery depends on them.
How it works
Four tests decide whether a unit will hold. It must be counted automatically, take roughly the same effort each time, have an unambiguous completion point, and carry an explicit exclusion list. Units failing any of the four generate invoice disputes.
Unit prices are fixed prices in miniature. Federal rules describe a firm-fixed-price contract as providing “a price that is not subject to any adjustment on the basis of the contractor’s cost experience”, which is exactly the bargain a unit rate strikes.
Commercial software uses the same building block. Stripe’s documentation lists per-unit pricing among its core models, noting that in per-seat pricing “each pricing unit represents one user”.
| Test | The question to ask | Failure symptom |
|---|---|---|
| Countable | Can a system produce the number? | Monthly reconciliation meetings |
| Stable | Does effort vary by more than half? | One party losing consistently |
| Bounded | Is there a written exclusion list? | Scope creep inside the unit |
| Complete | Is the end point observable? | Arguments about partial work |
Rate build-up is the other half. A defensible rate starts from the cost of delivering one unit at expected volume, adds overhead recovery, then adds margin, so each component can be discussed separately.
Volume assumptions have to travel with the rate. A rate quoted for 100,000 units a year is not valid at 20,000, because fixed cost recovery per unit rises sharply as volume falls.
Examples
Unit rates succeed or fail on the definition long before anyone looks at the number. These four cases show a durable unit, two that collapsed, and one rebuilt around a better one.
A records bureau prices per page scanned and indexed, with a written exclusion for damaged originals. The unit has held unchanged through two contract renewals.
A payer prices per claim without stating whether a resubmission counts as a new claim. Roughly one in eight claims is resubmitted, and the annual argument costs more than the clause would have.
A retailer prices per order processed, then adds returns handling without repricing. The supplier absorbs the extra work for a year and then asks for a substantial correction.
A bank replaces per-application pricing with per-decision pricing. The end point becomes observable, incomplete applications stop being contentious, and disputes fall away.
Related terms
Unit-based commercials involve several terms that describe different layers of the same structure. The entries below separate the price, the cost and the method used to derive each.
- Unit cost of production: the supplier’s internal cost per unit, not the price charged.
- Rate card: the document that publishes the agreed unit rates.
- Activity based costing: the method that reveals what a unit actually costs to produce.
- Cost per contact: a unit measure used for benchmarking rather than for billing.
- Benchmarking: the external test of whether a unit rate is competitive.
- Procurement outsourcing: the function that negotiates units and rates together.
- Total cost: the view that catches unpriced work sitting outside the unit.
FAQ
What makes a unit durable?
Automatic counting, stable effort, an observable end point and a written exclusion list. A unit passing all four rarely needs renegotiating.
Should the rate be benchmarked or built up?
Both. A cost build-up tells you whether the rate is sustainable, and a benchmark tells you whether it is competitive. Either one alone is misleading.
Why do volume assumptions matter?
Because fixed costs are recovered across the units. A rate valid at high volume becomes loss-making at low volume, and the supplier will come back for it.
How is this different from transaction based pricing?
Unit rate pricing is the general structure. Transaction based pricing is the specific discipline of building a catalogue of transaction types and weighting them.
What belongs in an exclusion list?
Rework, exceptions, data remediation, ad hoc reporting and anything requiring a decision outside the standard path. Naming them protects both sides.
Can one contract use several units?
Yes, and most mature ones do. Different work streams usually need different units, which is where a weighted rate card becomes necessary.
See how unit-priced outsourcing contracts are being structured at Outsource Accelerator.
Independent
