Hourly quotes punish efficiency: the faster you get, the less you earn. Per-deliverable pricing flips the frame — the client buys outcomes (a logo, a landing page, a blog post, a video edit), not your time, and your reward for working faster is a higher effective hourly rate. It also kills the most awkward client question in freelancing: "how many hours did that really take?" The method is straightforward but has one step hourly quoters skip: the revision buffer. A deliverable priced at exactly hours × rate assumes the first draft ships — it never does. This calculator builds the price as (hours per deliverable × hourly rate) + revision buffer %, with an optional rush multiplier, then scales to package totals for N deliverables and shows your effective hourly rate. The buffer is not padding; it is the actuarial price of the revision rounds that history says will happen. Use it two ways: to quote (give the client the per-deliverable and package numbers — never show the hourly math) and to check yourself (if the effective hourly rate falls below your minimum acceptable rate, the deliverable is underpriced no matter how nice the package total looks). Worked example 1 — blog post package: 5 hours per article at $75/hr, 20% revision buffer, 4 articles, standard timeline: Worked example 2 — the buffer pays for itself: the client requests a third revision round adding 1.5 hours. Without the buffer the article consumed 6.5 hours for $375 = $57.69/hr. With the $450 buffered price, 6.5 hours = $69.23/hr — the buffer absorbed the overrun instead of your margin. That is what the 20% buys. Worked example 3 — rush: same article on a 48-hour deadline at +50%: $450 × 1.5 = $675.00 per article, $2,700.00 for four, effective rate $135/hr. Quote the rush price with a straight face: the premium prices the evenings and weekends you are giving up (see our weekend premium calculator for the same logic applied to hourly work). Client-facing vs internal: the proposal says "4 articles × $450 = $1,800, two revision rounds included, 50% rush available." It never says "$75/hr" or "20% buffer." The moment hourly math appears, the negotiation becomes about hours — the frame you chose per-deliverable pricing to escape. Charging a fixed price per finished unit — per article, per logo, per landing page, per video — instead of per hour. The client buys an outcome with a known price; you keep the gains when experience lets you deliver faster. It is the natural pricing model for repeatable, well-defined work, and it pairs with packages ("4 articles for $1,800") that raise average order value without raising the sales effort. Three differences: (1) Incentives — hourly rewards slowness; per-deliverable rewards efficiency, since your effective rate rises as you get faster. (2) Conversation — hourly quotes invite "how many hours did that take?"; per-deliverable quotes invite "is this outcome worth $450?" (3) Risk — hourly shifts estimate risk to the client; per-deliverable keeps it with you, which is exactly why the revision buffer exists. Use hourly for undefined, exploratory work; per-deliverable for repeatable units. 15–30% covers most professional services: 15% for tight, well-defined deliverables with experienced clients; 25–30% for creative work with subjective revisions or new clients. Calibrate from data: if your last 10 projects averaged 1.8 extra hours per 8-hour deliverable, that is a 22.5% buffer. A buffer under 15% is decoration — one real revision round blows through it. And define "a revision round" in the contract, or the buffer subsidizes infinite tweaks. No. The proposal shows deliverable, unit price, quantity, package total, revision rounds included, timeline — never the hourly rate or the buffer percentage. Those are internal calibration tools. Revealing them reframes the negotiation around your costs ("your rate is too high") instead of the outcome's value ("is this worth $450 to me?"). Transparency about scope builds trust; transparency about cost structure just gives the client leverage. Then the deliverable is underpriced regardless of how good the package total looks — raise the buffer, raise the internal rate, or reduce the hours (better process, templates, tools). Never "make it up on volume": ten underpriced deliverables lose ten times the money. Check every new deliverable type against your minimum acceptable rate before quoting it to a client; existing clients can be repriced at renewal. Three layers: (1) the buffer absorbs minor drift automatically; (2) the contract defines the deliverable precisely — format, length/complexity bounds, number of revision rounds, what counts as a new deliverable; (3) the change-order clause prices anything beyond that at the same per-unit rate (or a stated extra-revision fee). Per-deliverable pricing without scope definition is just fixed-price work with extra exposure — the definition is the product. Yes — it is often the best structure: per-deliverable for the defined core ("logo: $900, two revision rounds"), hourly for the undefined edges ("additional revisions beyond scope: $95/hr"). This gives the client price certainty where it matters and protects you where scope is genuinely unknowable. State both in the proposal so the hourly rate doesn't appear as a surprise later. Conservatively: estimate hours generously (first attempts always run long), use a 30% buffer instead of 20%, and treat the first 2–3 units as data collection. Track actual hours ruthlessly, then recalibrate the hours-per-deliverable input — most freelancers find their "5-hour" deliverable is really 7 hours, which at the same price is a 29% pay cut they never noticed. After calibration, the buffer can come down as your estimates improve. Redefine the deliverable: a "strategy audit," a "roadmap document," a "workshop session" are all deliverables with definable scope. Pure open-ended advising resists unit pricing — use cost-plus or day rates there. The test: can you describe what "done" looks like in one sentence? If yes, it can be a deliverable; if done is "whenever we stop talking," it can't. Multiply the buffered unit price by the rush factor (1.25×–1.5× here) — and apply it per unit, so the client sees the rush cost scale with scope. Rush premiums compensate for disruption (cancelled plans, reshuffled clients, night work), not just speed; that is why the multiplier applies to the whole price rather than adding a few hours. For the hourly equivalent logic, see our rush fee calculator. Existing clients accept recalibrated prices when the deliverable definition improves (more included, faster turnaround, better quality) — reprice at natural renewal points with 30 days' notice. New clients simply see the current price. The freelancers who struggle are the ones who never raise the unit price while their hours-per-deliverable silently grow; annual recalibration from tracked data keeps the effective rate honest.Key takeaways
How it works
Worked example
Frequently asked questions
What is per-deliverable pricing?
How is this different from hourly quoting?
How big should the revision buffer be?
Should I tell the client about the buffer or my hourly rate?
What if the effective hourly rate is below my minimum?
How do I handle scope creep with per-deliverable pricing?
Can I mix per-deliverable and hourly pricing?
How do I price the very first deliverable of a new type?
Does per-deliverable pricing work for services like consulting?
How does rush pricing fit per-deliverable quotes?
Will clients accept higher per-deliverable prices over time?
Base price per deliverableHours × hourly rate, before buffer.
Revision buffer amountThe scope-creep insurance built into the price.
Price per deliverableWhat you quote the client per unit.
Package totalPer-deliverable price × number of units.
Your effective hourly rateUnit price ÷ hours per deliverable. Compare to your minimum rate.
Total project hoursHours per deliverable × units (for your planning).
Verdict