Freelance Business

Writing Case Studies That Explain Your Design Thinking

Writing Proposals That Win Design Projects

Put the client's goals at the top

Clients don't buy design; they buy a solution to a problem. Your proposal should open by showing you understand that problem, not by listing every service you offer. Spend a few minutes echoing the client's own language from your discovery call or emails. If they said they're "losing sales because the website feels dated", use that phrase. It signals you were listening.

Then translate their goal into a clear outcome. Instead of "I offer brand identity design", write: "You need a brand identity that helps you stand out at trade shows and feels consistent across packaging, social media and your website." That single sentence tells the client you're thinking about their world, not your portfolio.

  • Restate the brief: one short paragraph summarising what they asked for and why it matters.
  • Name the outcome: what will be different for their business once the project is finished?
  • Connect to their audience: show you understand who they're trying to reach and what those people need to feel or do.

Define the scope so nothing is vague

Scope creep is the enemy of freelance profit, and vagueness is its best friend. Be specific about what you will deliver, how many rounds of revisions are included, and what happens if the project grows. Use plain English and avoid design jargon that might confuse a non-designer.

For example, instead of "logo design package", write: "Three initial concepts, two rounds of revisions on your chosen concept, final files in SVG, PNG, EPS and PDF formats, plus a one-page usage guide." That level of detail reassures the client and protects your time.

  • Included: list every deliverable, file type, and revision round.
  • Not included: gently note what would need a separate quote, such as additional concepts, copywriting, printing or photography.
  • Client responsibilities: state what you need from them, such as feedback within five working days or access to brand assets.

If you're a sole trader or limited company, a short scope section also makes it easier to raise a change request later without awkwardness. You're not being difficult; you're being professional.

Show a timeline with clear milestones

A timeline isn't just a schedule; it's a promise. Break the project into stages so the client can see what happens, when, and what you need from them at each point. Use dates rather than "week one" and "week two" where possible, because dates feel more real and help everyone plan.

Be realistic. If you're waiting on feedback, build in a buffer. A timeline that slips in the first week erodes trust, whilst a slightly longer timeline that you beat makes you look organised and reliable.

  • Kick-off: date, what you'll do, and what you need from the client to start.
  • Concept stage: when they'll see initial ideas and when feedback is due.
  • Design development: revision rounds and review points.
  • Final delivery: handover date, file formats and any support after launch.

Mention your working hours and preferred communication channel. UK freelancers often juggle school runs, client calls and deep work, so setting expectations early prevents frustration on both sides.

Present your fee as a simple decision

Money makes people nervous, so make it easy. Give a single, clear fee for the scope you've defined, or break it into staged payments. State whether the fee includes VAT if you're VAT registered, and be explicit about what happens if the project takes longer than planned because of delayed feedback.

Offer a payment schedule that protects your cash flow. A common UK approach is 50% upfront and 50% on completion, or three equal payments across larger projects. If you prefer a deposit, say so clearly and explain why it secures their slot in your calendar.

  • Total fee: one number, in pounds, with VAT status confirmed.
  • Payment terms: deposit, milestones, final invoice, and accepted payment methods.
  • Late payment: a polite note that you may charge interest or pause work on overdue invoices.
  • What's included: repeat the scope summary so the fee feels justified, not arbitrary.

Don't apologise for your price. Present it as the investment required to achieve the outcome you described at the top. If the client hesitates, you can discuss reducing scope, not reducing your rate.

Make the next step obvious and follow up

End your proposal with a single, frictionless action. Tell the client exactly how to say yes: "Reply to this email with 'approved' and I'll send the deposit invoice and kick-off questionnaire." Remove any ambiguity about what happens next. If you need a signed contract, attach it or mention that you'll send it once they confirm.

Keep the whole document skimmable. Use short paragraphs, bold key details, and bullet points for anything the client needs to check. Most decision-makers will read it on a phone between meetings, so clarity beats cleverness every time.

Finally, follow up. A gentle nudge three or four working days later is not pushy; it's helpful. Ask if they have any questions, and offer to jump on a quick call. Many projects are won not by the best designer, but by the one who made the decision easiest. Structure your proposal around their goals, scope, timeline and fee, and you'll give yourself the best possible chance of hearing "yes".

« Previous postOtto von Bismarck Next post »http://www..com/