The most common pricing mistake in freelance developer proposals, and the one that costs freelancers the most money, is this:
A single number, buried at the bottom.
The typical proposal reads like a resume with a price tag stapled on. Three paragraphs about skills, a list of technologies, and then, at the very end: "My rate is $45/hr" or "Total: $2,000." One number. Take it or leave it.
Here's why that loses you money:
- A single number invites a single response: "can you do it cheaper?" There's nothing to negotiate toward, only down.
- Burying the price signals you're uncomfortable with it. Clients read that discomfort and price you accordingly.
- One number gives the client no way to say yes to more. You never find out they would have paid double for a faster timeline or extra scope.
The fix I kept recommending is the 3-tier proposal. You present three options instead of one:
- Essential: the minimum viable version of the work.
- Standard: the version most clients actually need. This is the one you want them to pick.
- Complete: the everything version, with extras like priority support or a maintenance window.
This changes the client's internal question from "is this worth it?" to "which one do I pick?" That's a completely different conversation, and it's the one where you stop getting haggled down.
Here's a skeleton you can steal. Fill in your own scope lines:
SUBJECT: Proposal: [Project Name] - 3 options
Hi [Name],
Based on what we discussed, here are three ways we can work together.
OPTION A - ESSENTIAL ............ $[X]
[2-3 sentence scope summary]
Delivered in [N] weeks.
OPTION B - STANDARD .............. $[Y]
Everything in Essential, plus:
[scope addition 1]
[scope addition 2]
OPTION C - COMPLETE ............... $[Z]
Everything in Standard, plus:
[scope addition 3]
[priority support / maintenance window]
Payment: 50% to start, 50% on delivery. Valid for 14 days.
Setting X, Y, and Z is its own skill. A rule of thumb: Standard should be the price you'd quote as a single number today, Essential about 70% of that with real scope cut, and Complete about 140% with genuine additions. Never invent a tier by just changing the price. Each tier needs real scope differences or clients see through it.
The bigger problem underneath all of this is that most freelancers don't actually know their numbers. They pick a rate that "sounds right" and hope. If you want to fix that part, I put the math into a free calculator here: https://rateup-nw.netlify.app/#calculator.
And if you want the whole system, 15 proposal templates, 5 contract starting points, 8 rate-raise scripts for existing clients, and the pricing psychology guide, it's $49 as a one-time purchase: https://rateup-nw.netlify.app. No subscription.
What's the worst pricing mistake you've seen, either yours or someone else's? Curious how common the single-number quote really is.
Top comments (1)
tr.ee/dev-to
Some comments have been hidden by the post's author - find out more