NabblyGuides

How to start a freelance proposal

Build the opening of your freelance proposal around the brief, relevant work you can show and the questions that affect delivery. Your reply should make it easy to see that you read the brief and understand the next decision. You do not need to fit your entire work history into the opening message.

Answer the actual request

Name the feature, file, audience or deadline that matters to this project. Then connect it to something you have genuinely done. A portfolio link is more useful when you explain which part of the sample you made and why it relates to the request.

If your experience is adjacent, say so. You can explain how a skill transfers without claiming to have completed the same project before. Never invent a client, credential or result to make the fit look closer.

Ask about the missing dependency

Read the post again before adding questions. Ask about something that changes the scope, estimate or delivery: whether the copy is final, whether the files are available, or who approves the work. Don't ask the client to repeat a detail they already supplied.

If you cannot support a fixed estimate yet, explain what you need to check. A bounded paid discovery stage can be appropriate when the request depends on a system or dataset you haven't inspected. Describe its output rather than offer an undefined investigation.

Keep the opening easy to read

Around 90 to 150 words is a useful starting point for an opening reply, rather than a requirement for every brief. Use short paragraphs and familiar words, as if you were typing directly to the person who posted it. Aim for no more than two questions in that opening message; choose the ones that affect the next decision. A complex scope can need a longer conversation later.

Three edited examples

The briefs and replies below are fictional teaching examples, not live listings or testimonials. The stronger replies assume relevant experience; change those sentences to match work you can honestly show.

Design: a brochure with supplied content

Brief: "Need a promotional brochure. We supply copy and photos. Please deliver a print PDF and editable layout."

Weak reply: "I'm a creative designer who delivers high-quality work. Please see my portfolio. I would love to help."

Stronger reply:

Your brochure needs to work in print and as an editable layout. I can share a brochure sample and explain how I organized the supplied copy and images. Is the content final, and do you have the printer's file specifications? With those confirmed, I can outline the layout, review stages and handover files in a proposal.

Why it fits: It addresses the outputs, connects the evidence to layout work and asks about inputs that affect production. It doesn't offer a full concept before the scope is clear.

Writing: a case study from an interview

Brief: "Need a customer case study from an interview transcript. Our sales team will use it. Customer approval required before publication."

Weak reply: "I'm a versatile writer who can create compelling content for any industry and audience."

Stronger reply:

You need a case study that turns the interview into a useful sales story and still passes customer approval. I can share a relevant sample and explain my role in structuring it. I'd separate the problem, the approach and the results, with claims checked against the supplied material. Do you have a preferred length, and who handles customer sign-off? I can then propose a draft and review schedule around that approval step.

Why it fits: The reply notices the audience and approval dependency. It describes handling evidence without inventing impressive customer results.

Development: an export that matches filters

Brief: "Add a CSV export to our dashboard. It should match the selected date and status filters. Include tests."

Weak reply: "I'm an expert developer with a broad technology stack. I can build this quickly and efficiently."

Stronger reply:

The export needs to match the filtered dashboard results, with tests covering that behavior. I can explain a reporting feature I've worked on and the part I implemented. Is there already an endpoint for filtered records, and how large can an export be? Those details would help me confirm whether this is a small interface change or needs additional backend work before estimating it.

Why it fits: It identifies the behavior that matters and checks a dependency that could change the implementation. Familiarity with a framework alone wouldn't answer either question.

Leave the client a clear next step

Keep the message focused enough to scan. Finish by asking for the missing information or offering a scoped proposal once it is available. Avoid promising a delivery date or result before you can support it.

Nabbly sorts listings into fields but does not verify the employers behind them. Review the original posting and research the employer before applying. Be cautious about requests for payment or unpaid test work.

Browse gigs

Related proposal guides

Browse by field