← Back to guides

Freelance Proposal Example: Scope, Price and Acceptance

Editorial review: 17 October 2026 · Published by Freelance Fee Calculator

A proposal should help the client decide whether the defined work fits their need and budget. It cannot guarantee a sale. Use the fictional example below to turn a vague request into deliverables, assumptions, a price and a next action.

On this page
  1. Clarify the missing information
  2. A concise proposal body
  3. Show the price build-up
  4. Make approval testable
  5. A final accuracy pass
  6. Frequently asked questions
  7. Sources and jurisdiction limits
  8. Make assumptions visible before the client approves
  9. Run a contradiction check
  10. Put this into practice

Clarify the missing information

For “redesign my website,” ask which pages, what existing content can be reused, which functions must remain, who approves and what delivery date matters. If a critical unknown changes the cost substantially, propose a defined discovery stage or state a provisional range with its assumptions. Do not present an unsupported fixed quote as certain.

A concise proposal body

“You need a clearer enquiry path across Home, Services and Contact. I propose a three-page redesign using your approved copy and existing brand assets, with two consolidated feedback rounds. Delivery: editable source and agreed web files. Excluded: booking, copywriting and ongoing hosting. I will confirm the final schedule after receiving content and access.” Replace this example with facts from the actual brief.

Show the price build-up

Illustrative estimate: discovery 3 hours, design 8, implementation 10 and checks 3 = 24 hours. At an assumed $50/hour the quote is $1,200 before separately agreed items and tax. A negotiable schedule of $480, $480 and $240 totals $1,200. Explain milestone triggers and due dates. The arithmetic does not establish a market rate or legally required deposit.

Make approval testable

List the checks the client will review: the three named pages, the agreed enquiry behavior, the approved content and the specified browser/device coverage. Distinguish fixing an agreed defect from adding a feature. Ask the client to confirm scope and choose a kickoff time, then put the accepted terms in the agreement. Do not claim that all proposals are non-binding; legal effect depends on wording and law.

A final accuracy pass

Check the client’s name, totals, dates, currency, attachments and whether each promised result is within your control. Remove copied claims such as “I improved checkout conversion” unless you actually did and can explain the evidence. Keep a version number and record revisions so the signed scope matches the accepted proposal.

Frequently asked questions

Must every proposal contain a fixed price?

No. Explain a defined discovery step or a bounded estimate when essential information is missing.

How long should it be?

Long enough to explain the decision and scope, with schedules or appendices for complex details. There is no universal word count.

Can I use this text unchanged?

No. Replace fictional assumptions, confirm legal effect and make every promise match the actual project.

Sources and jurisdiction limits

Sources apply to the named service or jurisdiction. Do not turn one country’s guidance into a worldwide rule; verify the terms relevant to your situation.

Make assumptions visible before the client approves

For a fictional $1,200 proposal based on 24 hours at an assumed $50 planning rate, list the hours as a basis for your estimate, not a promise to bill exactly 24 hours under a fixed-price agreement. A 40% / 40% / 20% payment split is $480, $480 and $240. Use the same total and scope in the proposal, draft contract and milestone invoices.

Suppose the estimate assumes final copy arrives before design starts. If that copy is not ready, offer a clear choice: agree a later start, price copy preparation separately, or narrow the initial delivery. Avoid a deadline that silently depends on unavailable inputs. Separate included revision rounds from correction of work that fails agreed acceptance checks.

Run a contradiction check

Compare the document in pairs: scope versus price; deadline versus dependencies; payment milestone versus acceptance; ownership versus final payment; ongoing support versus the one-time fee. If the summary says “five pages” and the appendix lists six, resolve the difference before asking for approval. Confirm which version the client accepts and which person can approve changes. A signed proposal or approval message may have legal significance depending on its terms and local law, so use a suitable process. The worksheet is a consistency check, not a prediction that the proposal will win. Record the client’s actual reason for accepting or declining so future changes address evidence rather than guesswork.