The hourly rate you calculated when you started is now the ceiling on your business. Here is where a price comes from, and how to build one that survives being said out loud.
A value-based price comes from what the outcome is worth to the client and what your life needs to cost, and the number of hours you spend is unrelated to both. Pricing by time caps your income and punishes you for getting better at your work.
Almost every consultant starts with the same calculation, and it's the reason so many of them stall at the same income. Decide what you want to earn. Divide by the working hours in a year. That is your hourly rate. Then scope a project by adding up hours and multiplying.
I call it the bad math of entrepreneurship, and the problem isn't that the sum is wrong. The problem is what it makes you.
It ties you to a straight exchange: I give you my time, you give me your money. That is a job with extra admin. You have all the risk of owning a business and the earnings structure of employment.
And it has a hard ceiling built into it, which is the part nobody mentions when they teach it. There are only so many hours. Once they're full, the only way up is to raise the rate, and raising a rate on an existing client is a conversation most consultants avoid for years.
What that arithmetic quietly decides for you:
So the ceiling isn't a market fact about what consultants can earn. It is arithmetic you chose in your first month, before you knew anything, and never revisited.
Hourly pricing pays you less as you get better, which is the strangest feature of the model and the one that should end the argument.
Work it through. A problem that took you four weeks in your second year takes you nine days now, because you've seen it before and you know where it goes wrong. Under an hourly model, your reward for a decade of expertise is a smaller invoice.
The client got a better outcome, faster, with less disruption. You got paid less for it.
| What the client experiences | What hourly pricing does |
|---|---|
| The problem solved faster | Reduces your fee |
| Fewer meetings, less of their time consumed | Reduces your fee |
| Judgment that avoids an expensive mistake | Not billable at all |
| A decade of pattern recognition applied in an hour | Bills as one hour |
There is a second cost that's harder to see. Hourly work invites the client to manage your time, so you end up justifying a timesheet to somebody who doesn't care how long it took and only wants the thing fixed.
It also puts you in the wrong position in the relationship. Someone whose time is being audited is being treated as an executional resource, and that positioning is set in the sale rather than after the contract.
We're talking about pricing your work to support your life, and then getting the clients who can pay that.
Leah Neaderthal, Smart Gets Paid
The first pricing principle I teach is that price isn't about money, it's about your life. That sounds like a soft opening and it's the most practical thing in this guide.
Here is what it means concretely. Setting your price is a decision about how you want your life to be, and about making enough that your business can fund it. Not filling your schedule. Not matching what other consultants charge. Not what you think somebody will tolerate.
So the sequence runs the opposite way to the one most people use:
Step four is where most people flinch, and it's the whole game. If your number requires clients who can pay it and your current clients cannot, the answer isn't a smaller number. It is different clients.
This is also why pricing work so often turns into identity work. You are deciding what your life is allowed to cost, which is a bigger question than what to put on a proposal, and it's why the arithmetic alone rarely fixes it.
A price you quote before you understand the problem is a guess, and you'll spend the rest of the engagement defending it.
Value-based pricing has an order to it, and the order is the method. You understand the situation. You establish what solving it's worth to them. You define the engagement that gets them there. Then the price follows from the first two.
That means the pricing conversation begins long before anybody says a number. It begins with questions like these:
Notice that all of those are ordinary business questions a colleague would ask. None of them is a pricing tactic, and together they produce a number that has a reason behind it.
The practical payoff is that you can say the price and explain where it came from in one sentence, in their terms. "You told me the delay is costing about eighteen thousand a month. The engagement is X, and it's designed to end that inside a quarter."
That sentence is hard to argue with, and it's impossible to write if you priced before you asked.
Not everything valuable is expensive to produce, and the gap between those two things is where a lot of margin lives.
The idea has a name in my curriculum, Race Track Items: elements of an engagement that are high value to the client and low lift for you. Every consultant has some, and almost nobody has catalogued them.
They tend to be things you've already built or already know. A diagnostic you've run forty times. A template that took you a year to get right and now takes an hour to adapt. An introduction you can make in one email. A way of framing a problem that lands with a board.
Two reasons this matters for pricing:
Do the inventory once. List everything you can deliver that a client would value highly and that costs you comparatively little. That list is an asset, and most consultants are giving several of its items away without noticing.
What it's not is padding. Adding low-value items to justify a number is the opposite move and clients can see it.
The inventory is also useful in the room. When a client asks what is included, the answer that lands names two or three of these by outcome, because they are the parts that sound like relief.
Nobody wants to hire a consultant. They want the outcome in their business, and every hour you spend is a cost from their point of view rather than a benefit.
This is worth sitting with, because it inverts how most proposals are written. A document that details your process, your phases and your deliverables is describing your effort. The client is trying to work out what will be different afterwards.
So the same engagement can be described two ways:
| Effort language | Outcome language |
|---|---|
| Six workshops over twelve weeks | Your leadership team aligned on one plan before the fiscal year |
| A full audit of your current programs | A clear answer on which three things to stop doing |
| Weekly advisory calls | A named owner and a decision path for every stalled initiative |
The right-hand column is what gets approved, because it's what your champion repeats to the person holding the budget. The left-hand column is what she has to translate on your behalf, and translation is where value gets lost.
None of this is spin. You do run the workshops. The question is which fact you lead with, and the one that matters to them is the one about their business.
State your price plainly, then stop. Do not justify it, don't soften it, and don't offer a reduction nobody asked for.
The silence after a number feels much longer than it is, and the urge to fill it's close to universal. What comes out in that gap is where the money goes: an unprompted discount, a nervous explanation of your rates, a sudden extra deliverable.
What that teaches the client is that the first number was negotiable, which means every number after it's too.
A few things make the moment easier:
The deeper version of this is that a price you've not decided on can't be said calmly. Most of the wobble in that moment traces back to a number you weren't sure about before the call started, which makes this a preparation problem more than a nerve problem.
When the work grows after you've priced it, that's a commercial event and it needs a conversation, not a quiet absorption into your evenings.
Every consultant knows this and most of them absorb it anyway. The request arrives mid-project, framed small, from a client you like, at a moment when raising money feels like it would spoil a good relationship.
Then it happens twice more, and the engagement you priced properly is now delivering at half the rate you set.
The reason it's worth naming every time isn't the money on this project. It is what silence teaches. A client who learns that scope grows for free will keep growing it, and they're not being difficult. They are responding to what you showed them.
The conversation is shorter than the dread suggests:
Some things aren't worth invoicing, and pretending otherwise makes you tiresome to work with. A half-hour call, a quick review, an introduction. Those are relationship, and they're cheap.
The test is whether it changes the shape of the engagement. An extra workstream, a new stakeholder group, a second round of something scoped once: those are the ones that need the conversation, and the value delivered and the value received move together.
A monthly arrangement isn't an exception to any of this, and it's where hourly thinking most often survives. The temptation is to work out how many hours a month you'll spend and multiply, which reproduces the ceiling in a new format.
Price a retainer on what continued access and continued outcomes are worth, and define what the client gets.
Run the numbers backwards once, this week, before you price anything else.
If step three produces a number that your current clients couldn't pay, you've not found a pricing problem. You have found a positioning problem, and that's the more useful thing to know.
Pricing looks like arithmetic and behaves like therapy, and pretending otherwise wastes everyone's time.
I can give you the sequence, and I have. Value, engagement, price. Discovery first. Say it and stop. Most consultants can repeat that back to me within an hour, and then still quote low the following Tuesday.
What moves is the decision underneath, about what you're worth and what your life is allowed to cost. That isn't a spreadsheet question and it doesn't resolve because somebody showed you a better formula.
What I have watched work is doing it once, out loud, with the number written down before the conversation starts, and then surviving the pause. It is uncomfortable exactly one time. After that you've evidence, and evidence is the only thing that beats the story.
And the clients who can pay aren't a rumor. They exist, they're buying, and they're largely indifferent to your hours. They want the problem gone.
The pattern I would watch for in yourself is the quiet one. Not the dramatic undercharging, which people notice, but the slow drift where an engagement grows a little at a time and nobody says anything. Six months later the effective rate has halved and it's nobody's fault, because no single moment was worth raising. Those moments are worth raising. Each one is small and awkward, and the alternative is a business that pays you less every year for better work.
Change the model at a natural boundary: a renewal, a new phase, or a new piece of work. Present it as a scoped engagement with a defined outcome and a single price, which is usually easier for a client to approve than an hourly increase. Trying to convert an in-flight project mostly produces an argument about the old arrangement.
Answer the question underneath it, which is almost always about the total. Say that you price by engagement, give the range for work of this shape, and offer to scope it properly once you understand the problem. Most people asking for a rate are trying to work out whether you're in their universe.
Price it on the value of the outcome, which you can establish even when your own effort is uncertain, and build in room for the unknown. If you can't estimate the work, propose a short paid diagnostic first, scoped and priced on its own. That gives you the information to price the main engagement properly.
Value-based pricing anchors the number to something real and measurable in the client's business. The discipline is in the discovery: you've to establish what the problem costs and what solving it's worth before you can quote. Charging what you can get away with requires no discovery at all.
Plenty of valuable outcomes aren't directly financial, and they still have weight you can name: risk avoided, time recovered for senior people, a decision unblocked, a team that stops losing its best staff. Ask what it makes possible and what it prevents. Clients can usually put a size on it once you ask.
Publishing prices makes sense for a standardized product and works poorly for consulting, where the right number depends on the situation you've not yet learned about. A range can help filter enquiries if you're getting a lot of poor fits. Otherwise let the price come out of the conversation, where it can be explained.
Find out what "too high" means, because it's usually one of three different things: more than their budget, more than they expected, or more than they believe the outcome is worth. The first is a scope conversation, the second is a framing problem, and the third means the discovery didn't do its job. Reducing the number without knowing which one you're dealing with solves none of them.
Explaining where a number came from is different from defending it, and the first one is fine. Point at what they told you the problem costs and what the engagement is designed to change, in one or two sentences. What damages you is the longer version, which reads as anticipating an objection nobody made and invites a negotiation about whether your reasoning is good enough.
You already know your prices are too low, and knowing has never fixed it. Here is what is holding the number down, and what to do next time.
A consulting sale takes months, several people and someone to lead it. Here is the process underneath it, and where most consultants lose the work.
How do I price my consulting services?
How do you raise your consulting rates with the clients you already have?
How do you grow a consulting business without working more hours?