A freelance designer we know sent an $18,000 proposal for a site redesign. Two weeks later the client replied, “We’ve decided to go in a different direction. Thanks for your time.” No reason. No feedback. She never found out why.
When we dug into her proposal, the answer was obvious in the first paragraph — and obvious in the pricing, and the scope, and the closing line. Four separate risk signals, each one invisible to her, each one loud to the client.
Freelancers rarely lose proposals on price. They lose on risk — the small signals inside the document that tell a client, this might not go well. This post is about the five risk signals that kill the most proposals, and the specific rewrite for each one.
You’re not losing on price. You’re losing on risk.
When a client chooses a $3,000 bid over your $8,000 bid, they’re not saying they believe the cheap bidder can deliver what you can. They’re saying your proposal didn’t create enough confidence to justify the premium.
Every proposal answers one unspoken question for the buyer: Is this safe?Safe means the scope is clear, the number is defensible, the payment terms are standard, and the person on the other end has done this before. When that question goes unanswered, the client doesn’t argue — they just go quiet. And the proposal that wins isn’t the cheapest one. It’s the one that felt safest.
Here are the five most common ways a proposal reads as unsafe.
Mistake 1 — Pricing that floats, not anchors
The symptom:“Total investment: $8,000” at the bottom of the proposal, with no line items explaining how you got there.
Why it kills deals:The client has no way to verify the number. So they anchor on their own guess — almost always lower. They compare your undifferentiated $8,000 to a competitor’s itemised $5,500, and yours looks padded even when it isn’t.
The fix: Itemise. Break the number down into the work it pays for.
UX design (3 screens, 2 revision rounds) — $2,400
Front-end development (approx. 40 hours @ $90/hr) — $3,600
Integration + QA (10 hours) — $900
Project management and handoff — $600
Total — $7,500
When the client can see the math, “expensive” becomes “specific.” Specificity signals professionalism. Round numbers with no backup signal a guess.
Mistake 2 — The “unlimited revisions” trap
The symptom:“Includes unlimited revisions until you’re happy.”
Why it kills deals: Sophisticated clients read this and think one of two things. Either the project is going to drag on forever while you try to hit a moving target, or your quote is padded to cover that risk. Neither reads as a good deal.
Less sophisticated clients read it and think, “Great, I can keep asking.” Then they do, and you work unpaid hours for a month.
The fix: Bound revisions like a professional contract.
Includes 2 rounds of revisions. Each round is one consolidated feedback document (not ongoing back-and-forth). Additional rounds billed at $90/hr and quoted before work begins.
This doesn’t make you seem inflexible. It makes you seem like someone who has run projects before and knows where they go wrong.
Mistake 3 — No deposit terms
The symptom:“Invoice on delivery” — or worse, no payment terms listed at all.
Why it kills deals:To a seasoned buyer, this signals one of two things. Either you’re new enough that you’ve never been burned (and they’ll have to manage that risk themselves), or you’re desperate enough to accept any terms. Both read as amateur.
It also leaves you exposed. A client who ghosts at the end costs you the entire project if you have no deposit.
The fix: State standard payment terms up front. The two that work:
- Two-step: 50% deposit to begin, 50% on delivery.
- Milestone-based: 30% on kick-off, 30% on first review, 40% on final delivery. Better for larger projects — gives the client a sense of escape-hatch control, which actually increases their willingness to sign.
Deposit terms aren’t aggressive. They’re the standard. Proposals without them get negotiated down; proposals with them get signed faster.
Mistake 4 — Scope that can be interpreted
The symptom:“Website redesign” or “copywriting assistance” as the scope.
Why it kills deals: Ambiguity on paper becomes arguments on call four. Every word the client can interpret differently from you is a future scope-creep fight. Experienced buyers know this and read vague scope as a warning sign; less experienced buyers sign it, then assume everything is included.
The fix: Write scope like a contract clause — and include a not included section.
In scope: Redesign of 5 pages (Home, About, Services, Blog index, Contact). Desktop and mobile breakpoints. Figma source files with developer handoff specs. 2 rounds of revisions as described above.
Not included: Copywriting, stock imagery, third-party integrations, SEO audit, content migration, ongoing maintenance after handoff.
The “not included” line feels awkward to write. It saves three painful email threads after the project starts. Skipping it is the single most common cause of freelancer burnout.
Mistake 5 — Closing with “let me know what you think”
The symptom:The last line of the proposal is “Looking forward to hearing from you!” or “Let me know if you have any questions.”
Why it kills deals: No next step. No deadline. No urgency. The proposal dies on their desk while they think about it, then forget about it, then sign with whoever followed up first.
The fix: Close with a concrete next step and a soft deadline.
This quote is valid for 14 days. To move forward, reply with approval and we’ll send the deposit invoice within 24 hours and schedule a 30-minute kick-off call for the following week. I’ll check in on [date] if I haven’t heard back.
Four things happen in that paragraph: you set a freshness window on the price, you tell them exactly what signing means, you promise a fast follow-through, and you remove their anxiety about being pursued by a salesperson. That last point matters more than you think.
The read-aloud test
Before you send any proposal, read it out loud. If you hit a line and can’t explain — in plain speech — whyit’s priced that way or whatis specifically included, the client can’t either. Every line that fails the read-aloud test is a risk signal. Rewrite it until it passes.
The best proposals don’t use more words than bad ones — they use fewer. Clarity is subtraction, not addition.
The critique shortcut
Every mistake above is something a proposal writer can miss in their own work. You wrote it; you know what you meant. The client doesn’t.
This is the gap we built ProposalDesk’s critique engine for. Paste any proposal — ours, a template, your last one that lost — and it scores five axes (pricing, scope, trust, structure, closing) against 39detectors. Soft pricing language, missing deposit terms, “unlimited” traps, weak closing CTAs, scope items with no timeline attached. It tells you which specific lines need a rewrite and shows a dollar figure for unpaid scope that’s silently sitting in your quote.
It’s free. No signup required. Run your next proposal through it before you send.