Freelance proposal checklist before sending

Try SpecBot free — send proposals clients accept in one click, with a signed PDF for both sides.

You’ve written the proposal. Now before you hit send, run through this checklist. Most proposal mistakes are caught in a final review — and a 10-minute review before sending is worth far more than the deal it might save.

Executive Summary

• Does the opening reference this specific client’s situation? Not a generic opener, not “I am pleased to present.” The first sentence should reflect what you learned on the discovery call.
• Does it use the client’s own language? When clients hear their words reflected back, they feel understood. If they said “we need to stop losing people at checkout,” your summary should reference losing people at checkout — not “reduce cart abandonment.”
• Is the business problem clearly stated? Not just the project task, but the business problem the project solves. “Your website redesign” vs. “your site isn’t converting qualified traffic to demo requests.”
• Is there a clear statement of what you’re proposing? What will you do, and what will it accomplish?
• Is the tone appropriate? Matches how you communicate? Not overly formal, not casual for an enterprise client?

Scope of Work

• Are all deliverables specific? Number of pages, articles, posts, reports — with quantities, not “etc.”
• Are formats and platforms named? “WordPress” not “CMS,” “Webflow” not “website builder,” “Google Docs” not “digital format.”
• Are revision rounds specified? “2 rounds of revisions” not “revisions until satisfied.”
• Are responsibilities clear? What are you doing vs. what does the client provide?
• Is there a scope exclusions list? What’s explicitly NOT included? This is the most important scope protection you have.
• Does the scope match what was discussed in the discovery call? If you scoped something differently from what was discussed, have you explained why?
• Are any assumptions listed? Conditions that must be true for this scope and timeline to hold (client provides copy by X date, CMS is on a supported version, etc.).

Timeline

• Is the timeline based on actual dates, not just durations? “Starting from sign-off, approximately 6 weeks” is okay. Actual dates (when known) are better.
• Is the project phased clearly? If there are distinct phases, what happens in each?
• Are client feedback windows specified? When does the client need to provide feedback? How many business days?
• Is the final delivery date clear?
• Is the timeline realistic for your current workload? Don’t promise a timeline you can’t deliver. An honest timeline beats a broken one.

Pricing

• Are the numbers your actual prices? (Especially important if using AI generation — AI doesn’t know your real rates.)
• Is pricing structured as line items, not just a total? Line-item pricing is easier to evaluate and easier to negotiate if needed.
• Are payment terms stated? Upfront percentage (50% is standard), when the remainder is due.
• If retainer: is the monthly fee and billing date clear?
• Are any expense pass-throughs named? Stock photography, hosting, tools, third-party services.
• Is there a proposal validity period? (“This proposal is valid for 30 days.”)

Credibility (if included)

• Is the credibility section brief and relevant? 2-4 sentences or a short bullet list — not a full-page biography.
• Is the experience referenced relevant to this project? “I’ve done 12 Webflow projects for SaaS companies” is relevant. A generic background summary is not.
• Are any testimonials or portfolio links current and working?

Next Steps

• Is there exactly one clear next step? Sign the agreement, pay the deposit, book the kickoff call — not “please let me know your thoughts.”
• Is the approval mechanism clear? What does “yes” look like? Do they need to sign something, reply to an email, or click a link?
• If using a payment link or signature tool: is the link working? Test it.

Final Checks

• Client name is correct and spelled correctly throughout. (This sounds obvious. Check it anyway — especially if you used a previous proposal as a template.)
• Company name is correct throughout.
• Dates are consistent. If you mention a start date in the timeline and in the executive summary, they match.
• No placeholder text remaining. No [CLIENT NAME], [INSERT DATE], or [TBD] left in the document.
• Read the proposal out loud. If you stumble over a sentence, the client will stumble over it too. Fix anything that doesn’t flow naturally.
• Proofread for spelling and grammar. Run it through a spellchecker. Read it again. Don’t send a proposal with a typo in the client’s company name.
• Does the proposal look professional? Clean formatting, consistent fonts and headings, no walls of text, easy to skim.

The 60-Second Final Test

Read the proposal one more time from the client’s perspective and ask:

1. Do I know what problem this solves for my business?
2. Do I know exactly what I’ll get?
3. Do I know how much it costs and what’s covered?
4. Do I know when it will happen?
5. Do I know what to do to say yes?

If the answer to any of these is no — fix it before sending.

A proposal that passes this checklist is better than 90% of what most freelancers send. The few minutes it takes to review properly is one of the best investments in your client acquisition process.

Start free on SpecBot — SpecBot turns your offers into proposals clients accept in one click, with a signed PDF for both sides. Free is 3 proposals a month with every feature; Pro is unlimited proposals at €12/month, or €9/month billed yearly. Write them in the web app, by voice, or inside ChatGPT and Claude.