How to write a freelance proposal that wins without cutting your price

When a client says “we went with someone cheaper,” they’re usually telling you the truth. But the real information is buried in it: the two proposals looked similar enough that price became the tiebreaker.

That’s a proposal problem, not a pricing problem.

Why proposals end up in a price comparison

A proposal that could have been written for any client about any project will be evaluated like any other option — by price.

Most freelance proposals follow the same structure: credentials, portfolio, scope, timeline, price. The problem with that order is that credentials and portfolio say nothing about this client’s specific problem. By the time you get to price, the client has no strong reason to prefer you over anyone else.

When the proposals look equivalent, the cheaper one wins. Every time.

What separates a proposal from a quote

A quote says: here is what I’ll do and what it costs.

A proposal says: here is what I understood about your problem, here is why this approach is right for your situation, and here is what it will cost.

The first can be compared directly with any other quote. The second is harder to compare, because it’s specific to them.

The way to get there is to do the work before you write anything. Qualify the lead properly — understand the actual problem, not just the brief. Ask why this is a priority now, what failure looks like for them, what they’ve tried before. That information is what you lead with.

“Based on our call: your current onboarding process drops 35% of users before the first action. The previous agency built flows that assumed users would read instructions. They don’t. My approach is to remove the instructions entirely and redesign around the one action you actually need them to complete.”

That paragraph can’t be written from a template. It came from listening. And it answers the client’s real question — “do you understand this?” — before they’ve even seen the price.

Specificity on track record

Credentials listed as a resume don’t move anyone. Credentials applied to the client’s specific situation do.

The difference between “I’ve redesigned onboarding flows for SaaS products” and “I’ve worked on three SaaS onboarding flows with similar drop-off rates — in two of them, the issue was at the same point you’re seeing it, and here’s what changed.”

The second version gives the client something to evaluate: not your years of experience, but your direct relevance to their problem. Value-based pricing depends on exactly this framing — the client needs to believe the outcome is real before the price for achieving it makes sense.

The structure that doesn’t set up a price comparison

Lead with the problem you understood. Then the approach. Then scope. Then price.

In that sequence, price arrives after you’ve established context. The client has already formed an opinion about the proposal before they see the number — and that opinion is based on fit, not just cost.

The typical proposal structure does this backwards. The good news is that flipping it is not complicated: the same information, different order.

When a client still asks for a discount

If you’ve done everything above and they push back on price, you’re in one of two situations.

First: the budget genuinely doesn’t work. That’s a mismatch, not a negotiation. Turning down a project that can’t work financially is better than accepting one that will cost you more than it pays.

Second: they’re testing. They got a cheaper quote and want to see if you’ll match. The answer is no — but you can explain what’s different. What’s the other proposal actually covering? If the scope is the same, either the other freelancer is pricing below cost, or they’re offering less than you are and the client hasn’t compared carefully.

What you don’t do is drop your price to close the deal. That discount has a real cost that extends well beyond this project. A client who chose you because you matched the lowest quote will expect that rate to continue.

The full playbook for when a client tries to undercut you is worth reading before that conversation happens.

The underlying problem

The freelancers who compete on price are usually the ones who haven’t done the work to justify a higher one. Not in capability — in specificity. A generic proposal creates a direct comparison. A specific one makes the comparison much harder to run.

Timescanner reads your calendar to show you how much time went into past projects by client and type. When a similar project comes up, you have real cost data to price the proposal — not a guess. Works with any iCal-compatible calendar. 30-day free trial, no credit card required.