Why hourly pricing is a trap
It punishes you for getting better. The first time you build a booking system it takes three days. The tenth time it takes four hours, and it is a better system because you now know which parts break. Under hourly pricing you just cut your own pay by eighty percent for becoming an expert.
It also frames you as labour rather than as someone solving a business problem. A business owner comparing hourly rates is comparing you to every other pair of hands. A business owner considering an outcome is comparing you to the cost of not fixing it.
Finding the value number
This is the part most people skip because it feels like guesswork. It is not, and you can do it in one conversation with three questions.
- 01How many enquiries do you get in a month? Almost every owner knows this roughly.
- 02How many turn into customers? They usually know this too, or can estimate it.
- 03What is a customer worth to you, on average? Every owner knows this precisely.
Now you have a value per enquiry. If a business gets forty enquiries a month, converts a quarter of them, and a customer is worth a meaningful amount, then every enquiry has a calculable expected value. If your system recovers even a few enquiries a month that were previously going cold at 11pm, you can put a number on what you are adding.
That number is what you price against. Not your hours. Not what a course told you to charge. The number the owner gave you, in their own words, using their own figures.
The two-part structure
Never quote one number. Quote two, and make clear what each buys.
| Setup fee | Monthly fee | |
|---|---|---|
| What it covers | Building the system, configuration, testing, onboarding | Hosting the platform, maintenance, fixes, improvements |
| When it is paid | Before the build starts, or split before and on delivery | Every month it stays running |
| What it does for you | Pays for the work so you are not funding the build | This is the actual business |
| Getting it wrong | Too low and you resent the project | Too low and you resent the client every time they message |
The setup fee protects your time. The monthly fee is what turns a series of projects into something that compounds. Charging only setup makes you a freelancer forever, however large the setup fee is.
Where to actually set the numbers
There is no universal figure, and anyone quoting one has not seen your market. What there is, is a method.
- The monthly fee should be a clear, defensible fraction of the value you calculated. Small enough that the arithmetic is obviously in their favour, large enough that supporting them is worth your time.
- The setup fee should be at least a few times the monthly, because the build is front-loaded work and you want the client committed before you start.
- Both should be numbers you can say out loud without your voice changing. If you flinch saying it, you will discount it before they ask.
- Local clients will pay less than international ones. Price accordingly rather than pretending otherwise, and treat early local work as buying proof.
The first client is priced differently, on purpose
Take the first one slightly below what you think is right, and over-deliver past the point of comfort. You are not buying revenue. You are buying a case study, a testimonial, referrals, and the belief that you can do this.
But do not work for free. Free clients do not implement, do not commit, and do not respect the arrangement. A small real payment changes the entire relationship, including how seriously they take their own onboarding.
Raising prices without losing anyone
Raise for new clients only. Leave existing ones where they are and tell them you have done so. It costs you nothing, it reads as loyalty rather than as a discount, and it removes the anxiety that stops most people from ever raising at all.
Raise when any of these are true: you have a result you can point at, you are turning work away, delivery has become fast enough that the price no longer reflects the value, or you are quietly resenting a client. That last one is a pricing signal, not a personality flaw.
What to say when they ask why it costs that
Do not defend the price by describing the work. Nobody cares how many workflows it involves.
Go back to their own numbers. They told you what an enquiry is worth and how many are going cold. Restate that, then state the fee beside it. The comparison does the work, and you have not argued at all.
If the numbers genuinely do not justify the price for that business, say so and walk away. A business with very low enquiry volume does not need this yet, and telling them that is how you get the referral when they grow.
The mistakes that cost the most
- Quoting before understanding the problem. You cannot price value you have not measured.
- Cost-plus pricing on software, which turns you into a reseller earning a markup.
- One number instead of two, which hides the recurring line and trains the client to see this as a project.
- Discounting when someone hesitates. Hesitation usually means the value was not established, and a discount confirms the price was invented.
- Charging the same for a business turning over a little as for one turning over a lot. Same build, different value, different price.