A guy I know runs a small landscaping company. He got a proposal for a new website: three pages, a contact form, "modern design," $2,800. Sounded fine. Six months later he'd paid $6,100, the site still didn't have a working contact form, and when he asked for the login to make a change himself, he found out the designer owned the domain registration in their own account. He didn't get burned because the designer was a scammer. He got burned because the proposal never said any of the things that would have protected him, and he signed it anyway.
That's the pattern. Most bad web design outcomes don't start with a bad designer. They start with a proposal nobody actually read for what it wasn't saying. This post is about what to look for before you sign, not after you're already six weeks in and the invoices keep growing.
The short answer
The honest answer is that price is the least useful number on a web design proposal. What actually protects you is four things: a scope of work you can picture finished, a clause that says you own the site when it's paid off, a stated revision limit, and control of your own hosting and domain. If a proposal has all four, the price is just a negotiation. If it's missing two or more, the price is a trap regardless of what it says.
Most proposals get graded on tone and design samples. Those matter for taste, not protection. Read the boring parts first — the parts about deliverables, ownership, and what happens when you and the designer disagree about "done."
What actually matters when you're reading a proposal
Strip away the branding and every proposal is answering five questions, whether it says so directly or not: what exactly gets built, who owns it when it's finished, how many rounds of changes you get, how long it actually takes, and who controls the hosting and domain after launch. A glossy PDF with case studies and a nice color palette can dodge all five and still look completely professional.
The AIGA's standard design services agreement — the closest thing the industry has to a shared template — treats scope of work and intellectual property as the two modules every design contract needs, before anything else gets added. If a freelancer or agency skips both, they're either inexperienced or hoping you won't notice.
Red flag #1: a scope of work you can't actually picture
"Modern, responsive website with contact form" is not a scope of work. It's a sentence that sounds like one. A real scope of work names the pages, says what happens on each, states who writes the copy, and says what "responsive" and "modern" mean in practice — usually by pointing to 2–3 reference sites.
Here's the test: read the scope section out loud to someone who's never seen the business. Can they describe, roughly, what the finished site looks like and does? If not, neither can you, and neither can the designer — which means "finished" becomes whatever the designer decides it is, three revisions and two months from now.
"We'll figure out the details as we go" is not flexibility. It's an open door for the project to take twice as long and cost twice as much, because nothing was ever defined enough to be finished.
If you're still deciding whether you even need a from-scratch build versus a custom site versus a template, settle that question first — the scope-of-work problem shows up in both, but it's cheaper to fix on a template.
Flat fee or hourly — which one protects you
Most web design work should be priced flat, not hourly, and the industry mostly agrees: a 2025 survey of 208 working web designers found that 82% price by project instead of by the hour. There's a reason it's lopsided.
Hourly billing makes sense for one situation: ongoing maintenance where nobody knows in advance how many hours a given month needs. For a defined website build, hourly billing shifts almost all the risk onto you. If the designer underestimates the work, or just works slowly, you pay for it — hour by hour, with no ceiling unless one was written in.
A flat fee only protects you if it's tied to the scope of work from the section above. A flat fee with a vague scope gives you cost predictability and nothing else — the designer just controls the outcome instead of the clock.
The clauses everyone skips
Past scope and pricing, three more clauses decide whether a project goes smoothly or turns into a slow-motion argument. All three are easy to add and commonly left out — not because they're hard to write, but because nobody asks.
Who owns the site when it's done
This is the one that surprises the most business owners. Paying for a website does not automatically mean you own it. Under U.S. copyright law, work built by an independent contractor only counts as a "work made for hire" in narrow, specific circumstances — and most freelance website code doesn't qualify unless a signed agreement says so explicitly. Without that clause, the designer holds the copyright even after final payment, and you're licensing the site rather than owning it.
The fix costs nothing: one sentence stating that ownership of the final deliverables transfers to you upon full payment. Nearly every legitimate contract includes it, which is exactly why its absence should worry you.
How many revisions you actually get
"Unlimited revisions" sounds generous. In practice it's a scheduling weapon — either yours (you never approve anything because you can always ask for one more pass) or theirs (they slow-walk every round because there's no cost to you dragging it out). Two to three defined rounds, with a stated rate for anything beyond that, keeps both sides moving toward an actual finish line.
Timelines that sound too good
A five-page business site built well takes roughly 3–5 weeks: content gathering, design, one or two revision rounds, and testing. A proposal promising a full custom build in a week isn't fast, it's skipping something — usually revisions, sometimes testing, occasionally both.
None of this means slow is automatically good. It means a timeline that's dramatically shorter than everyone else's quote is a scope problem wearing a speed costume.
Who holds the hosting and domain keys
Ask directly: whose account is the domain registered under, and whose account is the hosting on? If the answer is "ours" for either one, you don't have a website — you have a website you're renting access to. Switching designers later, or just wanting to make a change yourself, becomes a negotiation with someone who has no reason to make it easy.
This is the same lock-in dynamic that shows up whenever a platform controls the keys instead of you — it's part of why page-builder platforms create their own version of the same trap. Software vendors that control the account have historically used that leverage on price too: half of major SaaS vendors raised prices in 2023 alone, some by double digits, and customers who didn't control their own accounts had no real alternative but to pay.
Already have a proposal sitting in your inbox?
Send it over and we'll tell you, for free, what's missing and what it should actually cost.
Get a free proposal review →What most business owners get wrong
The single biggest mistake is treating the proposal like a menu instead of a contract. Business owners read it for the price and the design samples, decide they like both, and sign — without ever asking who owns the finished work or what "revisions included" actually caps out at. By the time those gaps matter, the relationship has already shifted from "prospective client" to "person who already paid a deposit," and that's a much weaker position to negotiate from.
The second mistake is assuming a lower price is automatically the safer choice. It's often the opposite. A rock-bottom quote with no scope of work, no ownership clause, and a one-week timeline usually costs more once you count the rebuild, the second designer, and the months you lost. Comparing a freelancer's quote against an agency's is worth doing properly — the tradeoffs are real — but compare them on what's actually in writing, not just the number at the bottom.
The third mistake is not knowing what a website is even supposed to return. If you can't estimate what the site needs to bring back to pay for itself, you have no real basis for judging whether $2,800 or $5,500 is the right number for your business specifically. And if you're still unsure whether you need a specialist who's built ten sites in your exact industry or a solid generalist, that's worth settling before you request proposals at all — it's covered in our generalist vs. specialist breakdown.
The bottom line
Don't grade a web design proposal on how it looks. Grade it on four lines: a scope of work specific enough to picture finished, an ownership clause that transfers the site to you on final payment, a stated revision count, and confirmation that the domain and hosting sit in accounts you control. If those four things are in writing, the price is just a number to negotiate. If they're not, ask for them before you sign anything — and if a designer resists adding four standard, unremarkable clauses to their own contract, that tells you more than any portfolio will. If you're earlier in the process and haven't decided whether to hire this out at all, settle that first; everything above only matters once you've decided someone else is building it.
Next step: pull up whatever proposal is currently sitting in your inbox and check it against those four lines right now. Most take less than ten minutes to grade once you know what you're looking for.
Sources
- AIGA — Standard Form of Agreement for Design Services
- U.S. Copyright Office — Circular 30: Works Made for Hire
- FTC Consumer Advice — How to Avoid a Home Improvement Scam (written contracts and deposits)
- Web Designer Academy — State of Web Designer Pricing 2025
- Vendr — Why SaaS Prices Are Still Going Up
Frequently asked questions
What's a fair price for a small business website in 2026?
Most small businesses should expect $1,500–$5,000 for a professionally built, custom site, or $500–$2,000 for a solid freelancer build on a template base. Price alone doesn't tell you much though. A $6,000 proposal with vague scope and no ownership clause is a worse deal than a $2,000 one that spells out every deliverable.
Should I pay a deposit before work starts?
A partial deposit is normal and protects the designer from doing free work for someone who ghosts. A third to half upfront is typical. Anything close to 100% upfront, with the balance due whenever the designer feels like it, removes your only leverage if the project stalls.
What happens if I run out of revisions and still don't like the site?
Depends entirely on what the proposal says, which is why you need it to say something. A clear proposal states a revision count (2–3 rounds is standard) and a per-round hourly or flat rate for anything past that. Without that line, you're negotiating from a weaker position after the work is already half-done.
Do I own my website if I stop paying my web designer?
Usually no, and this catches people off guard. Under U.S. copyright law, work built by an independent contractor doesn't automatically transfer to you just because you paid for it — ownership has to be spelled out in writing. If the proposal is silent on this, assume the designer owns the code until a signed agreement says otherwise.
Can I ask a web designer to change their proposal before I sign?
Yes, and you should. Any designer worth hiring will add a scope-of-work line, an ownership clause, or a revision cap without blinking if you ask. If a request that specific gets brushed off or met with vague reassurance, that's information too.
