Why most freelance proposals lose the job (and what to write instead)

Most proposals lose before the client reads the price.

They lose because they lead with the wrong thing. A portfolio of past work. A list of services. An “about us” section nobody asked for. The client sent a brief describing a problem they need solved, and the proposal responds by talking about the freelancer.

The client isn’t buying a freelancer. They’re buying a solved problem.

The structure that doesn’t work

The typical freelance proposal looks like this: introduction, credentials, past work, scope of work, timeline, price.

The problem with that order is that everything the client cares about most — “do you understand my problem?” — comes last. By the time you get to scope and price, you’ve already lost or kept the client based on the first two sections. And those sections were about you.

The structure that does

Flip it. Lead with the problem.

Restate the brief in your own words. Not to show you read it — to show you understood it. “Based on our conversation, the core challenge is that your current onboarding process drops 35% of users before the first action. The goal is to cut that to below 15% within 90 days.”

That sentence does more work than three paragraphs of credentials. It tells the client that you paid attention, that you understood what matters, and that you’ve already started thinking about their problem specifically.

Describe the solution, not the deliverables. Deliverables are what you’ll make. The solution is what it will do. “I’ll redesign the onboarding flow to reduce friction at the two points where you’re losing users” is a solution. “I’ll deliver 8 screens in Figma” is a deliverable list. Clients buy solutions.

Timeline and scope. Brief. Specific. Not padded.

Price. After you’ve established the value.

One clear next step. “If this looks right to you, I can start the week of March 10. A 30-minute call this week would let us confirm the scope before I send the contract.” One ask, not three options.

The question that most proposals don’t answer

“Why you, specifically?”

If the client sent the same brief to four freelancers and all four proposals look similar, they’ll decide on price. Your proposal needs to answer — without being asked — why your background, your approach, or your experience makes you the obvious choice for this particular problem.

One concrete sentence is enough. “I’ve redesigned onboarding for three SaaS products in the €5-15M ARR range, and the average drop-off reduction was 40%.” That’s specific. It maps directly to their problem. It doesn’t need amplification.

Length

Short enough to read in three minutes.

A long proposal signals one of two things: the freelancer doesn’t know what matters, or they’re padding to justify a price. Neither inspires confidence. The best proposals I’ve seen are one to two pages. They’re dense with relevant information and contain nothing that doesn’t need to be there.

If a proposal needs to be longer — complex technical scope, multi-phase engagement — use a summary at the top. The client reads the summary. The detail is there for the questions they have afterward.

When to write a proposal at all

Prospects who ask for a proposal before any conversation are often collecting quotes to compare on price. A proposal in that context is a losing game — you’re writing a document to justify a number they’ve already decided is their benchmark.

Before writing anything, get a call. Understand the problem. Understand the budget. Those two pieces of information tell you whether the engagement is worth pursuing and how to position your proposal if it is. A scope that’s still undefined at proposal stage is a red flag worth addressing before you invest two hours writing. On the other side of the price question, the framing in stop being undercut on price applies directly to the moment a client says they got a cheaper quote.

Timescanner tracks your time by project type, so you can calculate exactly what past projects like this one actually cost you — and price the proposal accurately. Works with any iCal-compatible calendar.