Latest / Freelance Careers with Fexingo: Independent Work, Consulting, and Self-Employment / How Freelancers Can Build a Client Proposal Template That Wins
Transcript
- Lucas: Luna, I want to talk about something that feels deceptively simple but I think is one of the highest-leverage things a freelancer can do: the proposal template. Luna: I'm already skeptical. Templates feel cookie-cutter. Clients can smell a form letter. Lucas: Right, and that's exactly the myth. A template isn't a form letter. It's a structure. The best freelancers I know have a template they've refined over years — but every proposal reads like it was written just for that client. Luna: Okay, so what's in this structure? Give me a concrete example. Lucas: Let's use a real case. A freelance UX designer I worked with — let's call her Maya — was sending proposals that were essentially feature lists. 'I'll deliver five wireframes, three user flows, a clickable prototype.' She was winning maybe one in four. We restructured her template into three sections: outcome, process, investment. Luna: Outcome first. So you're leading with the result, not the work. Lucas: Exactly. The outcome section is one paragraph that paints a picture of what the client's situation looks like after the project. Not 'we'll improve your conversion rate' — that's vague. She wrote: 'After this project, your onboarding flow will get a first-time user from sign-up to value in under 90 seconds, which we estimate will lift trial to paid conversion by 15 to 20 percent.' Specific, measurable, and it names the client's actual business metric. Luna: That's powerful. And the process section — does she explain every step? Lucas: No — and this is key. The process section is short. Three to five bullet points max. 'Week one: research and audit. Week two: design and test. Week three: refine and deliver.' The point isn't to prove you've thought of everything — it's to show you have a reliable method. Clients buy confidence, not complexity. Luna: So you're leaving out the detail to keep the focus on the outcome. That makes sense. What about the investment section? Price is usually where deals get sticky. Lucas: Right. The investment section in Maya's old proposals was just a number at the bottom — '$12,000.' No context. We changed it to: 'Investment: $12,000. This covers the full three-week engagement, including all research, design, and testing. Payment terms: 50 percent upfront, 50 percent on delivery.' And we added a one-line note: 'This is a fixed price based on the scope outlined above. If the scope changes, we adjust together.' Luna: That last line is interesting. It sets a boundary without being defensive. Lucas: Exactly. And it signals professionalism. The result? Maya's close rate went from 25 percent to almost 60 percent over the next six months. Not just because the template was better — but because the template forced her to think about what the client actually cares about. Luna: I want to push back a little. Doesn't this assume the client already trusts you enough to read the proposal? What if you're cold emailing? Lucas: Great point. In a cold outreach, the email itself is the proposal opener. You can still use the outcome-first frame. 'I saw your site's onboarding flow has a 40 percent drop-off at step two. I have a process that can fix that in three weeks. Want to see a proposal?' That's the same structure, just compressed. Luna: So the template scales from a one-line pitch to a full document. I like that. And I've seen data that backs this up — a 2025 study from the Freelancers Union found that proposals under 1,200 words had a 33 percent higher close rate than longer ones. Lucas: That's exactly the number I was thinking of. My rule of thumb is one page for projects under $10,000, two pages max above that. If you can't state the outcome in a paragraph, you probably don't understand the client's problem well enough yet. Luna: So the template is really a forcing function for clarity. It's not about the document — it's about the thinking. Lucas: Exactly. And here's the thing — developing a good template takes iteration. Maya didn't get it right on the first try. She tested versions, got feedback from clients who said no, and refined. That's the part most freelancers skip. They write one proposal, it doesn't work, and they blame the client or the price. Luna: What kind of feedback did she get from lost deals? Lucas: One client told her the outcome section sounded too good to be true. So she added a line: 'This estimate is based on similar projects I've completed for three other SaaS companies, with results ranging from 12 to 22 percent improvement.' That small credibility anchor made a big difference. Luna: So you're layering in social proof without a separate 'testimonials' section. That's smart — keeps the proposal tight. Lucas: Right. And it also signals that she's not guessing. She's done this before. That's the whole game — you want the client to feel like hiring you is the safe bet, not the risky one. Luna: You know, this reminds me of something I've noticed — the best proposals I've seen don't just sell a service, they sell a decision. The client is making a choice, and the proposal makes that choice feel obvious. Lucas: That's beautifully put. And if we've helped you think about your own proposals or make a smarter career move, I'll mention something quick — a small group of listeners already chips in monthly at buy me a coffee dot com slash fexingo, and that support is what keeps this show ad-free and independent. Luna: Yeah, it really does. And we're grateful — it lets us focus on the content, not the commercials. Lucas: So back to the template: once you have a structure that works, the next step is to build a library of outcome statements. For each type of project you do, write a few versions of the outcome paragraph. Then you can mix and match based on the client's situation. Luna: That's a great tip. I've also heard freelancers say they keep a 'kill fee' clause in their template — just in case scope creeps. Do you recommend that? Lucas: I do, but only for projects over a certain size. For a $5,000 project, a kill fee can feel adversarial. For a $50,000 engagement, it's standard. The key is to frame it as protection for both sides: 'If the project is paused or cancelled, a prorated fee covers work completed to date.' That's usually enough. Luna: And that language is already in the template — you don't have to think about it in the moment. Lucas: Exactly. The template is your baseline professionalism. It lets you focus on the relationship and the problem, not on reinventing the wheel every time. Luna: So if someone is listening right now and wants to build their own template, what's the first step? Lucas: Open a blank document. Write one sentence: what does the client have after this project that they don't have now? That's your outcome paragraph starter. Then list the three biggest steps to get there. Then write the total price. That's the first draft. Then spend the next month testing and refining based on feedback. Luna: One sentence to start. I like that. It lowers the barrier. Lucas: Right. And if you want to go deeper, look at your last three won proposals and your last three lost ones. What patterns do you see? Usually, won proposals have clearer outcomes and shorter process sections. Lost ones over-explain the work. Luna: That's a concrete audit exercise. I'm going to do that myself. Lucas: Good. Let us know how it goes. That's it for this episode — next time we'll talk about how to handle the 'I need to think about it' objection, which is basically a proposal killer if you don't have a follow-up plan. Luna: Looking forward to it. See you next time.