You asked three developers for a quote on "a simple website" and got back $2,000, $5,500, and $12,000. It's tempting to assume the cheap one is a bargain or the expensive one is a rip-off. Usually neither is true — they're quoting three different projects that happen to share a name. This guide shows you how to read a web design proposal line by line, put quotes side by side on equal terms, and spot the clauses that cost you later.
Why quotes differ 5x for the "same" site
A website isn't a fixed product like a laptop. Two people can hear "five pages and a contact form" and picture very different amounts of work. Most of the spread between quotes comes from a handful of predictable places:
Custom design vs. an adjusted template
A quote that starts from a purchased theme and swaps in your logo and colors takes a fraction of the time of a design made for your business. Both can be legitimate — but they aren't the same product, and the proposal should say which one you're getting.
Who writes the words and supplies the photos
If one developer assumes you'll hand over finished copy and images while another includes copywriting or a photo shoot, their numbers will be thousands of dollars apart before a single line of code is written.
What's included after launch
Some quotes are build-only. Others fold in hosting, updates, backups, and a block of monthly edits. A lower build price paired with paid-per-incident support can end up costing more within the first year.
Who is doing the work
A solo freelancer, a small studio, and a larger agency have very different overheads, processes, and levels of review. That shows up in the price — and in what happens if your main contact gets sick or leaves.
Padding for uncertainty
When the request is vague, careful developers add a buffer for the unknowns, and less careful ones quote low and bill the surprises later. Both are reactions to an unclear brief, not to the actual project.
That last point is the one you control. Sending every developer the same written brief is the single most effective way to get quotes that can be compared at all — our small business website brief template gives you the ten questions to answer before anyone prices your project. If you're still not sure what a reasonable range looks like for your size of site, check the market ranges in how much a small business website costs first, so you know which quotes are outliers.
Line items every proposal should have
A bottom-line number tells you almost nothing. Before comparing, ask each developer for an itemized proposal that answers the following. If a line is missing, don't assume it's included — ask, and get the answer in writing.
- Scope: the exact list of pages, and what happens (and what it costs) if you need one more.
- Design approach: custom design, a customized template, or a builder theme.
- Content: who writes the copy, who sources photos, and who enters it all into the site.
- Features: contact or quote forms, booking, galleries, a blog or CMS you can edit, integrations.
- SEO setup: page titles and descriptions, sitemap, Google Search Console, basic structured data — named specifically, not just "SEO-friendly."
- Mobile and speed: whether the site is tested on phones and what performance it's expected to hit.
- Revisions: how many rounds of design and content changes are included, and the rate after that.
- Timeline: start date, milestones, launch date, and what happens if your content arrives late.
- Payment schedule: deposit, milestone payments, and final payment, tied to deliverables.
- After launch: hosting, updates, backups, and how small edits are handled and billed.
- Ownership: who registers the domain, whose name the hosting account is in, and who owns the code and design files.
Timelines deserve a second look on their own. A quote that promises a five-page custom site in a few days is either a template or an optimistic guess; our guide to how long it takes to build a website lays out realistic ranges so you can tell which.
A comparison table you can copy
Once the itemized proposals are in, put them into one table. The goal isn't to find the lowest number — it's to make every gap visible. Fill in each cell from the proposal itself, and write "not stated" wherever the document is silent.
| Line item | Quote A | Quote B | Quote C |
|---|---|---|---|
| Build price | — | — | — |
| Pages included / price per extra page | — | — | — |
| Custom design or template | — | — | — |
| Copywriting & photos included? | — | — | — |
| Forms, booking, CMS | — | — | — |
| SEO setup (itemized) | — | — | — |
| Revision rounds | — | — | — |
| Timeline to launch | — | — | — |
| Payment schedule | — | — | — |
| Hosting & care per month | — | — | — |
| Domain & hosting in your name? | — | — | — |
| You own code & design files? | — | — | — |
| 3-year total (build + 36 × monthly) | — | — | — |
The last row is the one that changes minds. Monthly costs compound: a $40 difference in hosting or care fees is $1,440 over three years — enough to erase the gap between two build prices. For context on what's reasonable there, hosting alone typically runs about $10–$30 a month, and care plans commonly range from $20 to $250 a month depending on what's included. Our breakdowns of website hosting costs and what maintenance actually costs explain what you should get at each price point.
Here's how the table tends to reshape a decision. Say Quote A is $2,000 for five pages built on a theme, with you writing all the copy, one round of revisions, and hosting on the developer's own account. Quote B is $5,500 for the same five pages with custom design, copywriting help, and three revision rounds. Quote C is $12,000 and adds a CMS, a booking integration, and a strategy phase. They aren't cheap, fair, and expensive versions of one thing — they're three different projects. The table makes you decide which project you actually need, and only then which price is fair for it.
Red flags inside the proposal
Most problems with web projects were visible in the proposal before anyone signed it. These are the clauses — or the missing clauses — worth slowing down for:
Ownership is vague or stays with the developer
If the developer registers your domain under their name, keeps the hosting account, or retains the code and design files, you can't easily leave. Your domain should be registered to you, and you should receive full access and files once the project is paid.
Hosting lock-in
Watch for sites built on a proprietary system that only runs on the developer's servers, or a "migration fee" if you ever want to move. Bundled hosting is fine; hosting you can't take with you is leverage.
No limit on revisions — or no mention of them
"Unlimited revisions" sounds generous but usually means the project has no clear end, or that changes get quietly billed as "new scope." A stated number of rounds plus an hourly rate after that is more honest for both sides.
Payment that isn't tied to progress
A deposit is normal. Paying 100% before any design is shown removes the developer's incentive to finish well. Look for payments linked to milestones you can actually see.
Buzzwords instead of deliverables
"SEO-optimized," "modern," and "responsive" aren't deliverables. Ask what specifically gets set up, tested, and handed over.
Nothing about after launch
If the proposal ends at go-live, find out who fixes a broken form in month two, and at what rate. Silence here usually means emergency hourly billing later.
Red flags in the proposal often go together with red flags in how the developer sells. Our guide to freelancer vs. agency vs. DIY covers how to vet the person behind the quote — portfolio checks, references, and the warning signs to look for before paying a deposit.
What to ask before signing
Once you've narrowed it to one or two proposals, a short call to clear up the gaps is worth more than another round of quotes. Keep it focused on what the document doesn't say:
- "Which line items in my brief are not covered by this price?"
- "What would push this project over budget, and how would you tell me before it happens?"
- "If my copy or photos are late, what happens to the timeline and the price?"
- "What exactly do I receive at handoff — logins, files, documentation?"
- "If I stop paying for hosting or care with you, how do I move the site, and what does that cost?"
- "Can you show me a live site you built at a similar price and scope?"
Ask for the answers to be added to the proposal or contract, not just said on the call. A developer who's comfortable putting everything in writing is usually one who's planned the project properly. If two quotes still look equal after all this, choose the one whose proposal you understood best — clarity before the project tends to mean clarity during it.
How we write our own quotes
For transparency: Nous Frame publishes its starting prices, so you can compare us before we ever talk. A Landing page starts at $1,500 (custom design, contact form, base SEO setup, about 2 weeks). A Website of up to 5 pages starts at $2,500 (custom design system, lead forms, technical SEO and schema, 3–4 weeks). Larger marketing sites with a CMS start at $5,500. Care plans covering hosting, updates, backups, monitoring, and monthly edits start at $99/month. Every site is hand-coded with no platform lock-in, so the code is yours to keep or hand to another team. If you're still deciding between a hand-built site and a template, our custom vs. template comparison covers that choice in depth.
If you already have quotes from other developers, you're welcome to send them along with your brief. We'll tell you plainly what's included in each, and if one of them is a better fit for what you need, we'll say so.
Frequently asked questions
Why do website quotes for the same project vary so much?
Because they usually aren't quoting the same project. One proposal may include custom design, copywriting, SEO setup, and a care plan, while another covers a lightly edited template and nothing after launch. Differences in who does the work (freelancer, studio, agency) and how much risk they pad for an unclear brief widen the gap further.
What should a website development quote include?
At minimum: the list of pages, design approach (custom or template), what content you supply versus what they write, features like forms or booking, SEO setup, number of revision rounds, timeline, payment schedule, what happens after launch, and who owns the domain, hosting account, and code. Anything not written down should be treated as not included.
Is the cheapest website quote a bad idea?
Not automatically. A low quote can be honest if it covers a smaller scope, like a single page on a template. It becomes a problem when the price is low because key pieces — mobile testing, SEO basics, post-launch fixes, or ownership of your domain — are missing and will be billed later or not done at all.
What are the biggest red flags in a web design proposal?
No itemized scope, 100% payment upfront, no stated number of revisions, the developer registering your domain in their own name, hosting you can't move without a fee, and vague phrases like "SEO-friendly" with no description of what's actually set up.
Want a quote you can actually compare? Send us your brief and get an itemized estimate — scope, timeline, revisions, and ownership in writing.