Value-Based Pricing: Stop Charging by the Hour
- Value-based pricing charges for the outcome you create, not the hours you log - so getting faster raises your income instead of cutting it.
- Price the result: estimate what the build is worth to the client's business, then charge a fair slice of that, not a multiple of your hours.
- When a client asks your hourly rate, move the conversation to the outcome before you ever name a number.
Value-Based Pricing: Charge for the Outcome, Not the Hours
Value-based pricing means you set your fee based on what the finished build is worth to the client, not on how many hours it took you to make it. If a tool saves a client forty hours of manual work every month, its value is measured in that saved time and the revenue it unlocks - not in the afternoon it took you to ship it with Claude Code. You estimate the outcome, then charge a fair slice of it. That is the whole idea, and it is the single biggest lever on how much a builder earns.
The reason this matters more now than ever: the faster you build, the more hourly billing punishes you. Claude Code compressed the work of a week into an afternoon. If you charge by the hour, that speed is a discount you hand the client for free. Value-based pricing flips it - the outcome is the same whether it took you two days or two hours, so your fee stays tied to the result and your effective rate climbs as your skill does.
This is not a trick to overcharge. It is a fairer trade for both sides. The client pays for a result they can measure, and you get paid for the value you deliver instead of being penalized for delivering it quickly.
Why Hourly Billing Quietly Caps Your Income
Hourly billing has a hard ceiling built into it: there are only so many hours in a week, and the better you get, the fewer hours each project takes. You are punished twice - once because you can only sell time you actually have, and again because every efficiency you gain shrinks the invoice. The builder who gets twice as fast on hourly billing does not double their income. They halve it.
| Hourly billing | Value-based pricing | |
|---|---|---|
| What you charge for | Time you spent | Result the client gets |
| Effect of getting faster | Invoice shrinks | Effective rate rises |
| Income ceiling | Hours in your week | Value you can create |
| What the client debates | Your rate and your hours | Whether the outcome is worth it |
The same build, priced two ways
There is a second, quieter cost. Hourly invoices invite the client to audit your time instead of your results. Every line item becomes a negotiation about whether that task really took that long. Price the outcome and the conversation changes completely - now you are both looking at the result and asking whether it is worth the fee, which is the only question that should matter.
How to Find the Value in a Build
You cannot price an outcome you have not measured, so the first job is to make the value concrete. Before you name a number, get the client to tell you what solving this problem is worth. Three questions do most of the work: how much time or money the problem costs them today, what changes for the business once it is fixed, and what they have already tried and spent trying to fix it.
- Time saved: hours per week or month the build removes, multiplied by what an hour of that person's time is worth.
- Revenue unlocked: sales, leads, or capacity the build makes possible that were not possible before.
- Cost avoided: the tool, hire, or agency retainer the client no longer needs because your build replaces it.
- Risk removed: the expensive mistake, missed deadline, or compliance gap the build prevents.
Once you have those numbers, your fee is a fraction of the value, not a multiple of your hours. A build that saves a client thirty thousand a year is not a five-hundred-dollar job because it took you an afternoon - it is worth a meaningful share of that thirty thousand, and a client who understands the math will happily pay it.
What to Say When a Client Asks Your Hourly Rate
The hardest moment in value-based pricing is the one where a client asks, 'So what is your hourly rate?' Answer that question directly and you have already lost - you have agreed to be priced by time. The move is not to dodge it but to redirect it to the outcome before any number gets said out loud.
Charging a flat project fee also removes the client's biggest fear about hourly work: the runaway invoice. A fixed number tied to a defined outcome tells them exactly what they will pay and exactly what they will get. That certainty is often worth more to them than a lower rate would be.
When Hourly Still Makes Sense
Value-based pricing is the right default, but it is not the answer to every engagement. Be honest about the exceptions rather than forcing the model where it does not fit.
A common middle path: price the initial defined build on value, then move ongoing work to a flat monthly retainer once the scope is clear. You keep the upside on the part with a measurable outcome and give the client predictability on the part that does not.
How to Switch to Value-Based Pricing, Step by Step
You do not need to overhaul your whole business overnight. Change how you price the next proposal you send, and let the results convince you.
- Before you quote, ask the three value questions: what the problem costs today, what changes when it is fixed, and what they have already spent trying.
- Translate the answers into a concrete number - time saved, revenue unlocked, or cost avoided.
- Set your fee as a fair slice of that value, then present it as one flat project price, not a rate times hours.
- If asked for an hourly rate, redirect to the outcome before naming any number.
- Move ongoing or open-ended work to a flat retainer instead of falling back to hourly.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
What is value-based pricing?
Value-based pricing sets your fee based on the outcome a build creates for the client - time saved, revenue unlocked, or cost avoided - rather than on the hours you spent making it. You estimate what solving the problem is worth to their business, then charge a fair slice of that as a flat project fee. Because the price is tied to the result and not the time, getting faster raises your effective rate instead of shrinking your invoice.
How do you price a project by value instead of by the hour?
Ask three questions before you quote: what the problem costs the client today, what changes for the business once it is solved, and what they have already spent trying to fix it. Turn those answers into a concrete number, then set your fee as a fraction of that value and present it as one flat price. A build that saves a client thirty thousand a year is priced against that figure, not against the afternoon it took to ship.
What do you say when a client asks your hourly rate?
Do not name an hourly number. Say that you price the project on the result rather than the time, because how long it takes you should not change what it is worth to them. Then go back to understanding the outcome and quote one flat fee. This reframes the negotiation around whether the result is worth it, which is the only question that helps you.
Is value-based pricing always better than hourly?
It is the right default for any defined project with a clear, measurable result, but not for everything. Open-ended, exploratory, or maintenance work with no finish line is genuinely hard to price on outcome, and a flat retainer or day rate can be fairer there. The mistake is defaulting to hourly for defined builds, which is exactly where value-based pricing earns you the most.
Last reviewed July 20, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →
