A website proposal that's really just a price on a page tells you almost nothing. A proposal worth judging a designer by has six parts, and each one protects you from a different kind of surprise later.
Why the proposal matters more than the price
A 2026 survey of 292 US homeowners who had hired a roofer, run by Roofr, found that 66% ranked a professional proposal among their top three trust factors, and 45% cited it as a top consideration in their final hiring decision. That's a different trade, but the instinct carries over directly: a clear, specific proposal is itself evidence that the person will do clear, specific work.
1. A project overview
One paragraph stating what the site is for and what problem it solves. If this section could describe any business, it hasn't been written for yours yet.
2. Scope of work, and what's out of scope
This is the part most proposals get wrong by leaving it half-written. List exactly what's included: how many pages, whether content is written for you, whether photos are sourced or you provide them, whether search setup is included and what that means specifically. Then list what's not included: copywriting, photography, ongoing updates, extra pages, third-party integrations, whatever applies. A proposal with no "out of scope" section leaves everyone assuming something different, and that gap becomes an argument later.
3. A realistic timeline
A timeline with actual phases and dates, not just a single end date. See how long does it take to build a small business website for what a realistic breakdown looks like and what actually slows a project down. Be wary of a timeline that seems short for the scope; ask what's being cut to hit it.
4. Price and payment schedule
The total, broken into what you're actually paying for, with a payment schedule tied to milestones rather than a single lump sum up front. Optional add-ons should be priced separately from the core scope, not buried inside it. See how much should a small business website cost for how to compare quotes that look similar but aren't.
5. Who owns what, once you've paid
This is the section most proposals skip entirely, and it's the one that matters most later. A fair proposal states plainly that you own the finished design, code and content once payment is complete, and that the domain is registered in your name. See do I own my website? for what to check if this section is missing or vague.
6. What happens after launch
A stated support period, and what it covers: bug fixes, content changes, or both. If there's an ongoing monthly cost after launch, the proposal should say so up front, not introduce it as a surprise once the site is live. See monthly website plans vs a one-time price for the trade-offs between the two.
What a thin proposal looks like
A single price, a vague page count, and no mention of ownership, timeline detail or what happens after launch. That's not automatically a bad designer, but it is a proposal you can't yet compare fairly against anyone else's, and it's worth asking for the missing pieces in writing before you decide.
Questions
Should a proposal include a written contract, or is the proposal itself enough?
They're often the same document, or the proposal becomes the basis for a short contract. Either way, get the six sections above in writing somewhere you both sign.
What if a designer says pricing everything up front is impossible?
Some scope genuinely can't be fixed in advance, like ongoing marketing work. But the website build itself, the part with a defined page list, usually can be. Ask for a fixed price on the build and a separate, clearly labeled estimate for anything that's harder to predict.
Is it reasonable to ask for changes to a proposal before signing?
Yes. A designer confident in their process will walk through changes with you. Reluctance to adjust or clarify a proposal before you've even signed is worth noticing.