Day 4: Write Proposals That Win Without Discounting

The Concept

Most freelance proposals are essentially invoices sent before the work begins. They list what will be done, how long it will take, and what it costs. The client reads a column of deliverables and a number at the bottom, compares that number to the next proposal in their inbox, and makes a decision that has almost nothing to do with quality. If your proposal looks like every other proposal, price becomes the only differentiator — and that is a competition you do not want to win, because you will have to win it over and over again.

The shift that changes everything is moving the proposal from a description of your process to a diagnosis of the client's situation. Clients do not actually want a logo, a website, or a content strategy. They want the outcome those things are meant to produce: credibility in a new market, leads from a channel that is currently underperforming, or a communication system that stops their sales team from improvising every pitch. When your proposal demonstrates that you understand what they are really trying to achieve — not just what they asked for — you stop being a vendor and become an advisor. Advisors are not compared on price. They are compared on trust.

The gap between what clients ask for and what they need

A client who sends an enquiry asking for "a new website" is almost never really asking for a website. They are asking for more customers, a more professional impression, or a platform that does not embarrass them when a prospect Googles them. The website is the vehicle. The outcome is what matters — and if your proposal focuses on the vehicle, you sound like every other developer they are speaking to. If your proposal starts by naming the outcome they are actually after, you immediately occupy a different position in their mind.

This is not manipulation. It is listening. The gap between what a client says they need and what they actually need is often just a few questions away. Before you write your next proposal, ask yourself: what does a successful outcome look like for this client six months after the project ends? What would they tell a colleague this project achieved? That answer — not the list of deliverables — is what belongs at the top of your proposal.

Why AI is particularly good at this

Language models are trained on an enormous range of business contexts, which means they are skilled at translating a specific client situation into the broader commercial language that surrounds it. When you give AI the details of a client's situation and ask it to articulate the real problem, it often names things the client themselves has not yet articulated clearly. This is useful in two ways. First, it improves the proposal — clients who read their situation described more clearly than they described it themselves feel understood, and that feeling is the foundation of trust. Second, it surfaces the strategic framing of your work, which helps you price it as a business solution rather than a task to be completed.

The structure that works

The Situation-Complication-Resolution structure used in today's prompt is a simplified version of a consulting framework used by professional advisory firms for decades. It works because it mirrors how the client's own mind is moving: they have a situation, they face a complication if it is not resolved, and they need a resolution. Following that structure means your proposal reads with the client's logic, not yours. The scope and investment come after — anchored to the resolution, not floating independently as line items on a bill.

Presenting the fee without apology

One of the most common mistakes in freelance proposals is the way fees are presented. A line that reads "Total investment: £8,500" with nothing around it forces the client to evaluate the number in isolation. A sentence that reads "The investment for this engagement is £8,500 — reflecting the strategic complexity of the positioning work and the commercial risk of getting the brand wrong at this stage of growth" connects the number to the outcome. The client is not just looking at a cost. They are looking at a cost relative to what it buys them. Your job is to make that relationship explicit.

The test of a good proposal

There is a simple way to evaluate a proposal before you send it. Read the first paragraph and ask: could this opening apply to any other freelancer in my field? If yes, it is not specific enough. A strong proposal opening names something about the client's situation that only someone who paid close attention would know. It might reference the market they are entering, the timing pressure they mentioned, or the risk of getting this decision wrong. Specificity is not flattery — it is evidence that you were actually listening.

By the end of today you will have a proposal draft that starts with the client's real problem, builds to a clear resolution, and presents your fee as a considered response to the situation — not a number you arrived at by multiplying hours. That shift alone will change how clients respond to your proposals.