Freelance Proposal Mistakes That Lose Clients

Plenty of lost proposals don't fail on price. They fail because the client couldn't tell exactly what they'd get, or wasn't sure what to do next. Here are twelve common mistakes, with before-and-after fixes.

Updated September 30, 2026

1. Opening with yourself

The first paragraph is where the client decides whether you understood them. Leading with your experience makes them do the work of connecting it to their problem. Lead with the problem instead, and bring your experience in where it's relevant.

Before: "I'm a full-stack developer with 9 years of experience in React, Node and AWS, and I've worked with clients across many industries."

After: "Your booking form loses customers on mobile because the date picker doesn't open on older iPhones. Here's how I'd fix that first, then speed up the rest of the checkout."

2. A scope you can't check

If neither of you could point at a line and agree it's done, it will cause an argument later.

Before: "Website redesign with modern, responsive design and SEO."

After: "Designs and build for 6 page templates (Home, Services, Service detail, About, Blog, Contact), responsive on mobile, tablet and desktop, with page titles, meta descriptions and redirects from your 14 current URLs."

3. No "not included" section

Clients assume anything not excluded is included. Name the adjacent work they're likely to expect (copywriting, hosting, photography, ongoing support) and offer to quote it separately.

4. Unlimited revisions

"Unlimited" feels generous and ends up unprofitable. Set a number of rounds and define a round as one consolidated set of feedback.

5. A single price with no options

One number gives the client one decision: yes or no. Two or three options with different scope turn it into "which one?", and let a client with a smaller budget still say yes.

6. Price before value

If the price appears before the client understands what they get, it's judged on its own. Put it after the scope and approach, so it reads as the cost of something specific.

7. A timeline that ignores the client

Dates only hold if feedback and materials arrive on time. List what you need and when, and say that later dates move if inputs are late.

8. No payment terms

Deposit, milestones, due dates. Leaving them out doesn't make the proposal friendlier; it just moves the awkward conversation to after you've started work.

9. No expiry date

Without a valid-until date, a client can accept months later at a price you'd no longer offer. The date also gives you a natural reason to follow up.

10. Ending without a next step

Before: "Let me know if you have any questions!"

After: "If this looks right, accept it from the link and I'll send the deposit invoice. I can start on 3 March if we confirm by 24 February."

11. Waiting too long to send it

A proposal sent a week after the call arrives when the client's enthusiasm has cooled and they may have heard from someone else. Aim for a day or two, while the conversation is fresh for both of you.

12. Sending it and hoping

A proposal isn't finished when it's sent. Put a follow-up in your calendar before you send it, and follow up with a question or a new option rather than "just checking in".