What Should a Beginner Put in a First Freelance Proposal?

Your first proposal can feel like a job interview squeezed into a text box. You want to sound confident without bragging, friendly without being casual, and experienced even if you're just starting. Here's a comforting thought: clients aren't looking for perfect prose. They're looking for signs that you understood their problem and have a sensible plan. That's something any beginner can show.

What is a client really looking for when they read it?

Imagine the client has posted a job and opened a handful of proposals. Most of them start with "Dear Sir/Madam, I am a hard-working professional with excellent skills." After the third one, those words stop meaning anything.

What makes a proposal stand out is evidence that you actually read the job. Clients quietly ask themselves three things:

1. Does this person understand what I need?
2. Do they have a believable way to do it?
3. Will working with them be easy?

If your proposal answers those three questions, you're already ahead of many others, whether or not you have a long history.

Which parts should every proposal include?

Here's a simple structure you can adapt. Think of it as a checklist rather than a rigid template, and always write it fresh for each job.

A first line about them, not you. Repeat the core of their problem in your own words. For example: "You need your online shop's product pages rewritten so they're clearer and easier to scan on phones."

One or two relevant examples. Point to a sample or past project that resembles their job. If you're new, a practice piece is fine, as long as you're honest that it's a sample.

Your plan, broken into milestones. This is where beginners can really shine. Split the work into a few steps, each with a clear deliverable and a date. For instance:

• Milestone 1: rewrite 3 product pages for your review, by Tuesday.
• Milestone 2: rewrite the remaining 12 pages using your feedback, by the following Friday.
• Milestone 3: final tweaks and a short style note for future pages, two days later.

Some platforms are built around this idea; on workli.tech proposals are split into milestones with delivery dates, so the client sees your plan at a glance. Even where that isn't built in, writing it this way makes you look organised and reduces the client's risk.

A price that matches the plan. Give the total, and if it helps, the amount per milestone.

One thoughtful question. Ask something that shows you're already thinking about their project: "Do you have a brand voice guide, or should I suggest one based on your current homepage?"

A short, friendly sign-off. No pressure, no begging. "Happy to adjust the plan if your timing is different."

How long should it be?

Shorter than you think. A focused proposal of a few short paragraphs and a milestone list is usually easier to read than a full page. If you find yourself writing about your entire life story, pause and ask, "Does this help the client decide?" If not, cut it.

A quick tip: read your proposal on your phone before sending. If it feels like a wall of text, break it up.

What common mistakes should I avoid?

Beginners often fall into the same few traps, and they're all easy to fix:

• Copy-pasting the same proposal everywhere. Clients can tell instantly.
• Apologising for being new. You don't need to hide it, but you don't need to lead with it either.
• Promising everything. "I can do anything you need" sounds less believable than a specific plan.
• Pricing far too low. It can signal a lack of confidence and make the work feel risky.
• Ignoring the requirements. If the job asks for a specific skill or answer, address it directly.
• Typos in the client's name or business name. Small, but it stings.

And one more: don't oversell AI help. If you use tools to draft ideas, that's fine, but the proposal should sound like you and reflect your real experience. Some platforms even offer an AI-written note based on your own profile; treat that as a starting point and make it yours.

What happens after I send it?

Then you wait, which is the hardest part. Apply to a few jobs that genuinely fit rather than dozens that don't. If a client replies with questions, answer quickly and clearly, because this is often where the decision is really made. If you hear nothing, don't take it personally; clients get busy, projects get cancelled, and sometimes the timing just isn't right.

Every proposal you write makes the next one easier. Keep the ones that got replies, notice what they had in common, and gently refine your approach. Before long, writing a good proposal will feel less like an exam and more like the start of a friendly conversation.