A proposal isn't a price list. It's the first taste of what working with you feels like. The client doesn't just read a number — they read whether you understood their problem and whether this will be smooth. So a good proposal sells the outcome, not the hours.
What a proposal should contain
- A short restatement of the brief in your own words — proof you listened.
- What's included and what isn't (scope). This is where disputes are born, so be specific.
- Price broken into line items, not one big number (more on that below).
- A timeline, or at least a rough delivery window.
- How long the proposal is valid (e.g. 14 days) — a gentle nudge to decide.
- What you need from them to start (assets, access, a deposit).
How to present the price so it doesn't shock
One big number always looks expensive. Break it into parts — "Concept & direction", "Build", "Revisions & handover". Now the client doesn't see "$5,000", they see what they're paying for. And if they need to trim the budget, you have something to talk about without discounting your day rate.
Stop juggling browser tabs
UseOneApp creates the invoice, tracks the due date and keeps it next to the client — all in one place. Free forever for one project.
Try it free →Three mistakes that lose the deal
- Sending just a price with no context. A bare number in an email reads like a receipt, not an offer to work together.
- Leaving scope vague. "Build a website" means something different to everyone. Without boundaries, you get endless free revisions.
- Replying slowly. A client's enthusiasm has a short shelf life. A proposal in 24–48 hours beats a perfect one a week later.
After they say yes
Once the client agrees, turn the proposal straight into a project or invoice so nothing is retyped and the scope stays on record. For larger work, send a deposit invoice — it's normal, and it filters out non-payers before you start.