自由工作者如何撰寫能獲客戶簽署的服務提案

Disclosure: this post was written with AI assistance and reviewed before publishing.

A proposal is not a CV and not a brochure. It's a short document that answers one question for the client: "If I say yes, what exactly happens, and why is it worth the money?" Freelancers who win consistently tend to use the same structure every time and adapt only the details. Here's a structure that works for most service work, from design and development to writing and consulting.

Before you write: qualify and listen

The proposal is mostly decided before you open a document. On the first call, try to learn:

• The problem in the client's words. Write down their exact phrases; you'll reuse them.
• Why now. What triggered the project? A launch, a deadline, a failed previous attempt?
• What success looks like. A number, a date, a feeling ("we stop losing leads").
• Budget range. Ask directly: "Do you have a range in mind?" Many clients will answer.
• Who decides. If someone else signs off, your proposal must make sense to them without you in the room.

If the fit is poor, it's fine to decline before writing anything. Proposals take time.

The seven sections

1. Summary of the situation. Two or three sentences restating the problem using the client's language. This shows you listened, which is often the main thing clients are judging.
2. Goals. What the project should achieve, ideally measurable.
3. Approach. How you'll do it, in phases. Keep it understandable to a non-expert.
4. Scope and deliverables. A clear list of what is included — and a short list of what is not. The exclusions prevent most later disputes.
5. Timeline. Milestones with dates or week numbers, including what you need from the client and when.
6. Investment. Price and payment terms.
7. Next step. Exactly how to say yes: sign, reply, pay a deposit.

Two pages is enough for most projects. Long proposals are rarely read more carefully; they're just skimmed for the price.

Pricing: offer options

Presenting two or three options often works better than a single number, because the conversation shifts from "yes or no" to "which one". A common pattern:

• Essential — solves the core problem.
• Recommended — the core plus the things that usually make the biggest difference.
• Complete — everything, including ongoing support.

Make sure each option has a clear difference in outcome, not just in hours. Use fixed prices per option where you can estimate reliably; it's easier for clients to approve.

Payment terms and protection

State terms plainly:

• Deposit before work starts (25–50% is common for new clients)
• Remaining payments tied to milestones, not dates
• Number of revision rounds included
• What happens if the client delays feedback
• How long the proposal is valid

A proposal isn't always a contract. For larger projects, use a proper written agreement as well, and get local legal advice if the stakes are high.

Writing style

• Use "you" more than "I". The proposal is about the client's result.
• Replace jargon with plain outcomes: "Pages load in under two seconds" instead of "performance optimisation".
• Include one or two short, relevant examples of past work rather than a full portfolio.
• Keep formatting simple: headings, short paragraphs, a table for options.

A reusable template skeleton

Project: [Name]  |  Prepared for: [Client]  |  Valid until: [Date]

1. Where you are now
2. What we'll achieve
3. How we'll get there (Phase 1 / 2 / 3)
4. Included / Not included
5. Timeline and what I need from you
6. Investment (Option A / B / C) and payment terms
7. Next step: reply "yes" with your chosen option and I'll send the agreement and deposit invoice.

Follow up

Send the proposal, then follow up. A short note two or three working days later ("Any questions about the options?") is normal and expected. If there's no answer after a second follow-up, ask whether the project is still a priority — it gives the client an easy way to say no, which saves you time.

Summary

Listen first, restate the problem in the client's words, use a consistent seven-section structure, offer two or three priced options, be explicit about scope and terms, and make the next step obvious. Consistency is what lets you write good proposals quickly.

If you'd rather start from a ready-made structure, I put together a small, inexpensive, AI-assisted kit on this topic: Client proposal templates. There's a *free sample** (the intro plus one complete template), so you can check whether it's useful before paying anything. Everything above works without it. Other kits: all products.*