The Mistakes Everyone Makes on Their First Client Proposal

A proposal is not a document that explains what you'll do. It's a document that answers the question the client is already asking: will this person solve my problem? If the proposal doesn't answer that clearly and early, you've lost the job before the client finishes page one.

Here are the mistakes that show up in almost every first proposal.

**Proposing too many options.** The intention is to seem flexible and give the client control. The effect is confusion and delay. When someone is already unsure whether to hire you, presenting three packages at three price points makes them more unsure. It shifts the conversation from "should we work together?" to "which thing should we pick?". Send one recommendation. You can offer to adjust, but lead with your best judgment about what they need.

**Not confirming budget before writing.** A proposal takes real time to write. Writing one without knowing the budget range is like cooking a three-course meal for someone who hasn't told you if they're vegetarian or what they're celebrating. Ask before you write: "To make sure my proposal is in the right range — what budget are you working with?" If they won't answer, write a short scoping document first, not a full proposal.

**Leading with process instead of outcome.** "Here's how I work: step one, discovery call; step two, research phase; step three, revisions..." Nobody hired you to follow a process. They hired you to achieve a result. Reorder the proposal: start with the outcome, then explain the approach. "This engagement will give you a complete onboarding email sequence designed to convert trial users into paying customers within their first 30 days. Here's how we'll build it."

**Missing a clear call-to-action.** The proposal ends. Then what? Many proposals just... stop. No clear next step. The client reads it, thinks about it, and the momentum dies. End every proposal with an explicit CTA: "If this looks right, reply to this email and I'll send over the contract" or "I'll follow up on Thursday — let me know if you have questions before then." Make the next move obvious.

**Writing for the wrong person.** In many businesses, the person who asked for the proposal isn't the person who approves it. You're writing for the gatekeeper, but the decision-maker — who may have different priorities, different objections, and different language — will read it too. Ask: "Will others be involved in the decision?" If yes, write for both. Lead with business outcomes (the decision-maker cares). Include enough detail that the gatekeeper can explain it internally.

The proposal that works is shorter than you think it needs to be, clearer on the outcome than you'll be comfortable with, and ends with a specific next step. Most first proposals are the opposite of all three.