The hourly rate is the worst way to price freelance work, and it is the way almost everyone starts. It punishes you for getting faster, caps your income at the hours in a day, and turns every conversation into a negotiation about minutes instead of outcomes. Here is how to price for the value you create, not the time you spend.
Why hourly pricing traps you
When you bill by the hour, three things happen. Your income has a hard ceiling — there are only so many billable hours in a week. You get penalised for expertise — the faster you solve a problem, the less you earn. And the client fixates on your rate rather than the result, so a ₹4,000/hour quote sounds outrageous even when the job takes two hours and saves them ₹200,000.
The client does not want your hours. They want the problem gone. Price the problem.
Start with a day rate, not an hourly rate
Before you can price a project, you need to know your floor. Work out what you must earn per billable day to hit your income target, then treat that as the minimum. A rough version:
- Decide your target annual income.
- Assume you bill roughly 130–150 days a year, not 250. The rest is admin, sales, sick days, and gaps between clients.
- Add 25–30% on top for taxes, tools, insurance, and no paid leave.
- Divide the total by your billable days.
If the number shocks you, good — it means you have been underpricing. That day rate is the floor you never quietly drop below.
Then price the project, not the day
Once you know your floor, stop quoting days to the client. Quote a project fee tied to the outcome. "Redesign your checkout to lift conversion" is worth a percentage of the revenue it unlocks, not a count of your working hours. The same work can be worth ₹50,000 to a hobby site and ₹500,000 to a store doing crores in sales. Same effort, different value, different price — correctly.
To land on a number, ask three things: what is this worth to the client if it works, what does the problem cost them today, and what would they pay a bigger agency for the same result. Your fixed price should sit comfortably above your day-rate floor and comfortably below the value delivered.
Anchor high, offer a ladder
Always present three options, not one. A single quote invites a yes-or-no fight. Three options — call them essential, recommended, and complete — shift the conversation to "which one," which is a much better conversation to be having. The highest tier anchors the client's sense of the range and makes the middle tier feel reasonable. Most people pick the middle. Price it as the one you actually want to sell.
Kill scope creep before it starts
Scope creep is where profitable projects go to die. "Can you just also..." is the most expensive sentence in freelancing. Defend against it in writing before the work begins:
- List exactly what is included, and a short line of what is not.
- Define how many rounds of revisions the fee covers.
- State the rate for anything beyond scope — a change-request fee, not a favour.
You are not being difficult. A clear boundary is a gift to both sides; it removes the awkward money conversation from the middle of the work.
Raising rates without losing good clients
Your rate should rise as your skill and demand rise. The fear is that clients will leave. Some will — the ones who were only ever paying for cheap. That is the point. Raise prices on new clients first, immediately. For existing clients, give notice: "From next quarter my rate for new projects will be X." The ones who value the work stay. The churn clears room for better-paying work you did not have time for.
A simple test: if no client has ever pushed back on your price, your price is too low. A healthy rate gets the occasional "that's a lot" from people who then pay it anyway.
The mindset shift
Freelance pricing is not a reflection of your worth as a person; it is a reflection of the value you deliver to a business. Charge for the result. Put the boundaries in writing. Raise your rates on a schedule, not on a whim. Do that consistently and freelancing stops feeling like a treadmill of hours and starts feeling like a business.
Comments
Comments are powered by giscus. Set
PUBLIC_GISCUS_REPO_IDandPUBLIC_GISCUS_CATEGORY_IDin your environment to enable them.