Six Ways Consultants Charge You, and What Each One Quietly Rewards
Nobody sets out to pick a pricing model. How consultants charge is usually something you get handed, and by the time you're paying attention you're arguing about the number instead of the structure — which is a shame, because the structure is the part that decides how the work actually goes.
Every consultant pricing model rewards something. Not because anyone's cynical, but because incentives work on all of us whether we notice or not. Here's what each one rewards, where it's the honest choice, and where it quietly bends the work out of shape.
How consultants charge, at a glance
| Model | What it rewards | Best fit | Watch for |
|---|---|---|---|
| Hourly | Hours spent | Open-ended advisory | No incentive to find the fast answer |
| Day rate | Days booked | Intensive on-site work | Three-hour problems eating full days |
| Fixed project fee | Accurate scoping, finishing | Anything with a definable outcome | Vague scope, then change orders |
| Monthly retainer | The relationship continuing | Genuine ongoing work | Month eleven looking like month three |
| Outcome / revenue share | Results, and arguments about attribution | Cleanly isolated outcomes | Who decides what counts |
| Equity | The long game, hardest | Company-defining work, no cash | Permanently changes the relationship |
Now the detail.
Hourly
Rewards: hours.
Not padding, necessarily. Something subtler: there's no reason to find the fast answer, and a small permanent reason not to. The engagement expands to fill the problem.
Honest when: the work genuinely is open-ended. You want someone on call, the questions keep changing, and neither of you can define done.
Dangerous when: the job has a shape. If you can describe the outcome, paying by the hour means you carry all the risk of it taking longer and the person doing it carries none.
Ask: what's your estimate, and what happens if you exceed it?
Day rate
Rewards: days. Same as hourly, in bigger blocks.
The blocks are the interesting part. A day rate means a full day gets consumed by a three-hour problem and nobody mentions it. On the other hand it stops the meter-watching that makes hourly relationships tense — you're not calculating the cost of a phone call.
Honest when: the work really is full-day. Workshops, on-site reviews, intensive sprints.
Dangerous when: it's being used to make an hourly rate sound tidier.
Fixed project price
Rewards: accurate scoping and finishing.
This is the structure that puts risk where it belongs. If I quote you a number and it takes longer than I thought, that's my problem — I priced it wrong. You make one decision, once, with the whole number in front of you.
Honest when: the scope can actually be defined. Most work can be, with enough effort up front.
Dangerous when: the scope was written vaguely on purpose. Then the change orders arrive and you find out the fixed price was fixed to something other than what you needed. The defence is a written scope specific enough to argue with.
Ask: what is explicitly not included?
Monthly retainer
Rewards: the relationship continuing.
Fine when it should continue, quietly corrosive when it shouldn't. The failure mode isn't fraud, it's drift — month eleven looks like month three, nobody wants an awkward conversation, and the invoice keeps clearing.
Honest when: there's genuine ongoing work. Someone has to watch the numbers monthly, maintain the thing, or be reachable.
Dangerous when: it's a discrete job wearing a subscription costume.
Ask: what specifically happens each month, and what would make you tell me to stop paying?
Outcome or revenue share
Rewards: results — and arguments about attribution.
The alignment is real. So is the problem nobody warns you about: you both have to agree what counts. Revenue went up nine percent. How much was the pricing change, and how much was your best salesperson having a good quarter, a competitor stumbling, or the season? Reasonable people land in genuinely different places, which is how a well-intentioned arrangement becomes a negotiation about counterfactuals.
Honest when: the outcome is cleanly measurable and isolated. Cost removed from a specific line. A process that either runs or doesn't.
Dangerous when: the outcome is entangled with everything else in the business, which is most outcomes.
Ask: exactly how do we measure this, and who decides?
Equity
Rewards: the long game, hard.
The strongest alignment available and the most expensive thing you can hand over. It also permanently changes the relationship — an adviser with equity is a part-owner with opinions.
Honest when: the work is genuinely company-defining and cash genuinely isn't available.
Dangerous when: it's making a small engagement feel bigger than it is.
What I do about it
I'll work under most of these. Which one fits depends on the shape of the work, not on which one I prefer — and if capital is the real constraint, I'll structure something that shares the upside rather than asking for cash you'd rather keep.
The part I don't flex on: you see the whole number in writing before anything starts. What I think can be improved, how I'd do it, how long it takes, what it costs. You read it on your own time, with nobody sitting across the table watching your face, and you decide.
Not because it's generous. Because nobody makes a good decision about money while being looked at.
The test that works on anyone
Whoever you're considering — me, an agency, a developer, a finance person — ask three things.
What does it cost, and do I get a number or a feeling? What happens if it takes longer than you thought? What do I own at the end?
Anyone good has clean answers ready, because they've been asked before. Anyone who needs three more calls before they'll say a price has already told you something.
Then ask the fourth one, which matters more than all of these: after you hand me this, who actually does it? And if what you're buying is a website specifically, there's a longer version of this test here.