What to Include in a Freelance Proposal (Checklist)

A freelance proposal is not a branding deck. It is a decision document — the client should know what they are buying, what it costs, and what happens next.

Use this checklist before you send. If a section is missing, you are either inviting negotiation chaos or scope creep on day one.

The one-page executive summary

Put this at the top. Busy buyers may read nothing else.

Include:

• Client goal — one sentence in their words
• Your recommendation — what you propose doing first
• Investment — total or phase-one price
• Timeline — start window and key milestone
• Next step — "Approve phase one by [date] to hold the slot"

If the summary does not stand alone, the proposal is too buried in detail.

Problem statement and context

Show you listened:

• Current pain (broken flow, missed deadline, internal bottleneck)
• Constraints they mentioned (budget band, stack, compliance)
• Success criteria — what "fixed" looks like

This section should feel specific enough that a generic template would be obvious. For marketplace applications, compress this into two lines — see how to write an Upwork proposal.

Proposed approach and phases

Break work into phases clients can approve independently:

| Phase | Purpose | Output | | --- | --- | --- | | 1 | Discovery / audit | Written findings + recommended fix order | | 2 | Implementation | Working feature or deliverable in staging | | 3 | Launch / handoff | Production deploy, docs, training |

Phasing de-risks large numbers. It also mirrors how hourly vs project pricing should be packaged.

Deliverables list (specific nouns)

Check each deliverable is observable:

• [ ] Named pages, features, integrations, or documents
• [ ] Format (Figma file, repo branch, PDF report)
• [ ] Revision rounds included
• [ ] What happens if they request out-of-scope changes

Pair with how to write a freelance scope clients cannot misread for boundary language.

Timeline and dependencies

Include:

• Estimated duration per phase (ranges are fine)
• Client responsibilities — feedback within X business days, provide access by Y
• Blackout dates or capacity notes if honest

Pricing and payment terms

Checklist:

• [ ] Fixed fee, hourly cap, or retainer — labeled clearly
• [ ] What triggers each payment (deposit, milestone, completion)
• [ ] Expenses — who pays tools, licenses, stock assets
• [ ] Currency and tax note if relevant

Run numbers through the project quote calculator or rate calculator before you paste a figure.

Assumptions and exclusions

Explicitly list:

• What is not included (SEO, copywriting, ongoing support)
• Environment access you need
• Third-party approvals (legal, brand) on their side

Exclusions are not negativity — they prevent scope creep later.

Signed proposals still need a daily plan.

Once scope is agreed, delivery wins repeat work. WorkFocus gives freelance developers one place for today's tasks, client projects, and bugs.

Try WorkFocus free

Proof and credibility (keep it short)

One page maximum:

• One relevant case outcome (metric or before/after)
• Two to three client logos or names if allowed
• Links to portfolio pieces that match this job type

Skip the full CV. Deep background belongs on your site or profile, not in every send.

Terms (scale with project size)

For smaller engagements, basic terms in the proposal may cover:

• Intellectual property transfer on full payment
• Kill fee or deposit policy if they cancel
• Warranty window for bug fixes

Larger deals need a separate contract. The proposal should still reference what document governs.

How you will communicate

Clients fear silence as much as price. State:

• Update cadence (e.g. weekly written summary)
• Primary channel (email, platform chat)
• Response time you commit to during the project

A client update generator helps keep this consistent without rewriting the same email weekly.

Acceptance and valid-until date

End with:

• How to accept (signature, deposit, platform offer button)
• Proposal expiration — "Pricing held until [date]"
• Your availability window

Urgency should be real, not manufactured.

Pre-send checklist (quick scan)

Before you hit send, confirm:

1. Executive summary readable in 60 seconds
2. Deliverables are countable
3. Price appears in the main body
4. Exclusions are stated
5. Next step is one action
6. Filename is professional (ClientName-Phase1-Proposal.pdf)

For the narrative flow behind these sections, read how to write a freelance proposal that wins clients.

The bottom line

What to include in a freelance proposal:

• Summary — goal, recommendation, price, timeline, next step
• Scope — phases, deliverables, exclusions
• Commercials — payment terms and assumptions
• Trust — one proof point, not a memoir
• Process — how you will communicate and close

Checklist complete. Deliver like you wrote — try WorkFocus free.