Every winning freelance proposal has the same five parts: the client's problem, your plan, the deliverables, the price, and one clear next step. Everything else — long bios, mission statements, ten pages of boilerplate — is filler that slows down a yes. Here is the structure, part by part, ready to copy.

Part 1: The problem (their words, not yours)

Open with a short restatement of what the client told you they need. Two or three sentences, in language close to what they actually said on the call. This does two jobs at once: it proves you listened, and it frames the whole proposal around their goal instead of your services.

  • Bad: "I am a full-stack developer with 8 years of experience."
  • Good: "Your checkout flow is losing mobile customers, and you want it fixed before the spring campaign."

Clients skim proposals looking for evidence that you understood the job. Give them that evidence in the first paragraph.

Part 2: The plan (how you will get there)

Describe your approach in three to five plain-English steps. Not a methodology lecture — a sequence the client can picture. "First I audit the current flow, then I redesign the three checkout screens, then we test with real users, then I hand off to your developer." That is a plan. It builds confidence because it shows the work has a shape and an end.

Include a rough timeline here. "Two weeks from kickoff" beats a Gantt chart every time.

Part 3: The deliverables (what they can point at)

This is the section clients reread before they pay. List concrete, countable things: number of pages, number of concepts, rounds of revisions, file formats, what happens at handoff. Every item should be something the client could check off a list.

Just as important: say what is not included. "Copywriting and stock photography are not included in this scope." One sentence of exclusions now prevents a week of awkward emails later.

Part 4: The price (one number, stated plainly)

One flat price, in bold, with a one-line summary of what it covers. Resist the urge to bury it, apologize for it, or pad the section with justification. If you followed parts one through three, the value case is already made — the price is just the last fact.

If you offer options, cap it at two. A single alternative ("add a second landing page for $600") reads as helpful. Three tiers with feature matrices reads as a decision the client has to schedule a meeting about.

Part 5: The next step (make yes a single action)

End with exactly one instruction: "Approve the proposal and pay the 50% deposit to lock in your start date of March 9." Not "let me know your thoughts." Not "happy to jump on another call." One action, one link, one outcome.

The fewer steps between "I want this" and "it is booked," the more proposals convert. This is where most freelancers leak deals — the client says yes in their head, then the moment passes because acting on it required effort.

Putting it together

Five parts, one page, sent within a day of the call. That is the whole template. If assembling it still feels slow, Tendrly was built for exactly this structure: answer five questions, and it drafts the branded proposal with a one-click Stripe payment link attached — so when the client approves, they have already paid.

FAQ

Do I need a cover letter or about-me section?

No. A one-line credential inside the plan section ("I have rebuilt checkout flows for 12 e-commerce brands") does more than a full bio page. The client already vetted you before asking for a proposal.

Should the price go at the top or the bottom?

Either works, as long as it is easy to find and stated once. What kills deals is hiding it on page six or splitting it across confusing line items.

How long should the whole proposal be?

One page for most projects, two at most for complex ones. If a section does not help the client say yes, cut it.