Why every quote you got is different
How much does a website cost? I've been answering versions of that question for twenty years: as an agency developer writing the estimates, on product teams defending the budgets, and now as a freelancer in the Chicago suburbs who scopes projects for a living. The honest answer starts with an uncomfortable fact. I've seen three legitimate quotes for the same project come back at $4,000, $18,000, and $60,000, and nobody in that lineup was trying to rip anyone off.
The industry data has the same shape. WebFX's 2026 pricing guide (opens in a new tab) puts a freelancer build anywhere from $500 to $10,000 and up, and an agency build at $3,000 to $30,000 and up. A range that wide isn't pricing information. It's a symptom: "website" describes a one-page promo and a 200-product storefront equally well, so a number only means something once it's attached to a defined scope.
Every quote also bakes in assumptions the vendor may not say out loud. Who writes the copy. Custom design, or a template with your logo on it. How many revision rounds are included. Who owns hosting and fixes after launch. When two bids differ by 10x, they're almost never pricing the same project. That's the most useful thing I can tell you before you compare a single number.
How much does a website cost, by project type
The chart below is what I actually quote in 2026, as one senior developer working with Chicago companies and remote teams. The ranges assume custom work built properly, not a $30 template with the colors changed. An agency delivering the same scope usually lands at two to three times these numbers, because the invoice also covers a project manager, a designer, and the office they sit in. Neither price is wrong. They're different products, and choosing between a freelancer and an agency is its own field note.
Ranges: my own estimates, July 2026
View this chart as a table
| Project type | Low | High |
|---|---|---|
| Landing page | $1,500 | $5,000 |
| Brochure site | $3,000 | $10,000 |
| Marketing site + CMS | $8,000 | $25,000 |
| Ecommerce storefront | $12,000 | $40,000 |
| Web app UI | $20,000 | $75,000 |
A few notes on the bands, because the labels compress a lot:
- Landing page. One page with one job: a launch, a campaign, an event. The top of the band buys custom design and real copywriting instead of the placeholder text everyone promises to replace later and never does.
- Brochure site. Five to ten static pages that establish who you are. No CMS, so when the content changes, a developer changes it. Cheapest tier to build, and the right call when the content genuinely holds still.
- Marketing site with a CMS. The workhorse for most of the small businesses that call me. Your team edits pages, posts, and case studies without a developer in the loop. Most of the web design cost above the brochure tier goes into CMS wiring and a design system that keeps page twenty looking like page one.
- Ecommerce storefront. Catalog, cart, payments, tax, shipping, receipts. The platform is the cheap part; product data, integrations, and edge cases are where the hours go.
- Web app UI. Dashboards, portals, anything with logins and state. This is software with a design problem attached, and it's priced like software.
What moves the number
Within any band, five things push a project toward the top of its range, roughly in this order:
- Content volume. Migrating fifty pages is real labor even after the templates are done. Content is the most underestimated line in every quote I've reviewed, including my own early ones.
- Integrations. CRM, booking, payments, marketing automation. Each one is a small project with its own documentation, its own sandbox, and its own way of failing the week before launch.
- Ecommerce anything. The moment money moves through the site, testing and security stop being optional and the QA budget roughly doubles.
- Accessibility remediation. Building accessible from day one costs a little extra attention. Retrofitting a finished site after a demand letter costs real money. A vendor who quotes accessibility as an add-on is telling you it isn't in their defaults.
- Decision makers. Every stakeholder with veto power adds a revision round. I've watched approvals alone turn a $6,000 build into a $12,000 one.
Where the money actually goes
On a typical marketing site build my hours split roughly like this: a quarter on design, forty percent on the build, and the rest across content work, QA, and launch. That same build takes 6 to 12 weeks from kickoff to launch, with most of the calendar spent waiting on content. Those are my own averages from twenty years of timesheets, not a law of nature. Their real use is explaining cheap quotes: when one bid comes in at a third of the others, design, QA, or content is usually what got deleted, and you'll buy it back later at a worse rate.
The budget doesn't stop at launch either. GoDaddy's 2026 maintenance guide (opens in a new tab) puts upkeep for a small business site at $50 to $500 a month, which matches what I see in the wild. Hosting, domain renewals, platform updates, security patches, small content changes: that is the subscription cost of owning a website, and skipping it works about as well as skipping oil changes.
That math is most of what website redesign cost comes down to. A neglected site doesn't get cheaper; it sits there depreciating until a rebuild is the only option left. In my estimates, rebuilding a site that skipped years of upkeep runs three to five times what steady maintenance over the same period would have cost, because you're paying for the original build again, plus the archaeology.
How to buy well
Advice from the person who writes the quotes, take it or leave it. Fixed price works when the scope is genuinely fixed: a landing page, a brochure site, a redesign with a defined page list. Hourly fits maintenance and evolving work, where a fixed bid just forces the vendor to price in the uncertainty. I covered the pricing models and the red flags in the guide to hiring a freelance frontend developer in Chicago, and the short version is that the model matters less than getting the scope in writing.
For anything bigger than a landing page, a small paid discovery phase is the cheapest insurance you can buy: a few hundred to a couple thousand dollars for a sitemap, a feature list, and an estimate with real numbers in it. You get a tighter quote, and you learn how the vendor thinks before you're married to them. Then ask every vendor the same three questions. What exactly is included at this price? What happens when scope changes mid-project? Who maintains the site after launch, and at what cost? The answers tell you more than the numbers do.
And if what you actually want is the answer to how much does a website cost for your specific project, with your content and your integrations and your deadline, that takes a conversation, not a chart. My engagement options are public, and a scoping call costs nothing. Worst case, you walk away with a sharper set of questions for whoever you do hire.