Freelancing and Side Projects

Writing a Simple Project Proposal

The typical parts of a freelance proposal and how to keep it concise, clear and useful, so a client can understand your plan and decide quickly.

On this page
  1. What a proposal is for
  2. Start with a conversation
  3. The typical parts
  4. Keep it concise
  5. Be honest in your claims
  6. Review before sending
  7. Following up

What a proposal is for

A proposal is a short document that shows a prospective client you understand what they need, describes how you would approach it, and states the practical terms. It does two jobs at once. It helps the client decide, and it gives both sides a clear starting point if they say yes.

A proposal is not a sales brochure. Most clients are busy and read quickly, so the best proposals are usually the ones that are easy to scan and answer the obvious questions without much effort.

Start with a conversation

A good proposal depends on understanding the situation. Before writing, if possible, talk with the client or read their brief carefully. Ask about:

  • what they are trying to achieve
  • what has been tried before
  • any deadlines, constraints or preferences
  • who makes the decision
  • the budget range, if they are willing to share it

If you cannot get answers, state your assumptions in the proposal. That way, if an assumption is wrong, the client can correct it before work begins.

The typical parts

Proposals vary by field and project size, but most contain the following sections. For a small job, each can be a few sentences.

1. A short summary of the need

Open with one short paragraph describing the client’s situation and goal in your own words. This shows you listened and lets them correct any misunderstanding. Avoid starting with a long account of your own background.

2. Your proposed approach

Explain what you plan to do, in plain steps. Keep it practical: “I will review the existing pages, draft new text for the five main pages, and revise it after your feedback.” Skip jargon where possible, since the reader may not share your vocabulary.

3. Deliverables

List exactly what the client will receive. Be specific about formats and quantities. This section matters because it defines the scope, and it ties directly to the way you shape client expectations. Where it helps, add what is not included.

4. Timeline

Give the main milestones with approximate dates or durations. Note what you need from the client and when, since delays on their side can move the schedule. Use ranges if you are not sure, and consider your other multiple projects before committing.

5. Price and payment terms

State the price or the way it is calculated, any deposit, when invoices are issued and when payment is due. If the price is an estimate, say what could change it. Present the figures plainly, with no surprises hidden in small print.

6. Relevant experience or examples

A few sentences or a couple of links to similar work are usually enough. Choose examples that relate to this client’s need, and describe them accurately. If you show past work, make sure you have permission, and avoid sharing anything confidential. You can mention testimonials from past clients if they have agreed to be quoted, but select them carefully and keep them honest.

7. Terms and next steps

Mention how long the proposal remains valid, how to accept it and what happens next. For anything beyond a small job, indicate that a fuller agreement will follow. The case for written agreements is stronger the larger the project is, and legal questions are best handled by a qualified professional.

Keep it concise

Length is not a measure of quality. For a small project, one to two pages is often enough, and even a large one benefits from a clear summary at the top. To keep a proposal tight:

  • Lead with what the client cares about. Their goal comes before your credentials.
  • Cut repetition. If a point appears twice, keep the clearer version.
  • Use short paragraphs and simple lists where the content really is a list, such as deliverables or milestones.
  • Choose concrete words. Replace phrases like “high quality” with a description of what you will actually do.
  • Remove what the client does not need to decide. Detailed process notes can go into the later working agreement.

Writing in a concise style takes practice, and reading your draft aloud tends to expose padding quickly. A professional tone, neither stiff nor overly casual, usually works best.

Be honest in your claims

A proposal can describe what you will do and how you work, but it should avoid promises about results you cannot control. “I will redesign the checkout page and test it on common devices” is a commitment you can keep. “This will increase your sales” is a prediction that depends on many factors. Honest wording is more convincing over time and reduces risk for you.

Review before sending

Before you send a proposal, check:

  1. Does it name the client’s goal accurately?
  2. Are the deliverables specific enough that both sides would agree on what is included?
  3. Are the dates realistic, with room for the unexpected?
  4. Are the price and payment terms clear?
  5. Have you proofread names, numbers and dates? Mistakes in these details are noticed more than you might expect.
  6. Is anything unclear that the client would have to ask about?

Check any figure you include, since an arithmetic slip in a total can undermine trust.

Following up

After sending, it is reasonable to follow up politely if you have not heard back. A short message a few days later, asking whether the client has questions, usually comes across as helpful. If the answer is no, a thank-you and an invitation to get in touch in the future leaves the door open. A decline is not always a judgment on your work, and slow periods and rejections happen to most independent workers.

The complete guide to freelancing and side projects

Freelancing Basics Explained
Read the guide

Keep exploring

Guides from other topics

All topics →