What a Website Really Costs: Anatomy of a Build Quote
Two quotes for the same-looking site can differ tenfold. Here is what each line item buys, and what often goes missing.
Website build cost is set by effort across six line items, not by page count: discovery and planning, UI design, front-end build, back end and CMS, QA and launch, and ongoing maintenance. Typical ranges run from about $500–$3,000 for a template site, $5,000–$15,000 for a semi-custom build, and $15,000–$75,000 or more for fully custom work. Design and development usually take more than half the budget, and responsive design is now standard rather than an add-on.
Why does the same-looking site cost 10x more?
You line up two proposals and the mockups look nearly identical. One comes in at a few thousand dollars, the other at ten times that. Before deciding that one vendor is padding the bill, it's worth asking whether they're quoting the same thing at all.
Usually they aren't. 'Website' covers very different jobs. Swapping text and photos into an existing template is one job; designing every screen from scratch and building an admin panel your team can actually use is another. They share a name, not a process.
So the first step in comparing quotes isn't the total. It's the line items. Check whether planning, design, front end, back end, QA and maintenance are each accounted for, and who pays for whatever is missing once the project is underway.
What goes into a website quote?
A custom website quote typically breaks into six blocks. Agencies label them differently, but the stages are almost always the same, and each tends to take a fairly stable share of the total.
The biggest cost driver isn't page count; it's the number of unique templates. Thirty product pages that share one layout are one template. A home page, an about page and a contact page that all look different are three separate designs to create and build.
| Line item | What it covers | Typical share of quote | What drives the cost up |
|---|---|---|---|
| Discovery & planning | Requirements, sitemap, wireframes | 10–15% | Number of pages and features, number of stakeholders signing off |
| UI design | Home and inner-page mockups, mobile layouts, a design system in Figma | 20–30% | Unique templates, rounds of revisions |
| Front-end build | HTML/CSS implementation, responsive behavior, interactions | 15–25% | Animation or 3D, range of browsers supported |
| Back end & CMS | Admin panel, content types, forms, third-party integrations | 15–30% | Accounts, payments, multiple languages, number of API integrations |
| QA & launch | Cross-device testing, deployment, search engine setup | 5–10% | Device matrix, performance and accessibility targets |
| Maintenance | Bug fixes, security updates, content changes | Separate contract; typically 10–20% of build cost per year | Response-time SLA, monthly change volume |
How do prices differ by build approach?
Template sites are built on platforms such as Wix, Squarespace or Shopify by adapting an off-the-shelf theme. Expect roughly $500 to $3,000 and two to four weeks. The catch: layout and features stay within whatever the platform allows.
Semi-custom builds put a new design on top of WordPress or Webflow, typically $5,000 to $15,000. Fully custom work, from Figma design through development on a framework like Next.js, starts around $15,000 and spreads widely past $75,000 depending on integrations.
Responsive design is no longer an option you pay extra for. What varies is depth: designing mobile screens separately rather than shrinking the desktop layout typically adds 20–40% to design and front-end effort, so read how the quote describes it.
Which costs tend to be left out?
Some costs rarely show in the headline number: domain and hosting, licensed fonts and stock imagery, and sales tax or VAT. In Korea, for example, quotes conventionally exclude the 10% VAT, and registering with Naver Search Advisor is often an add-on.
Content is another frequent gap. Copywriting, product photography and translation are often quoted separately. So is compliance: someone has to own the privacy policy and the consent wording on contact forms, whether the rules are GDPR or a local equivalent.
Search setup belongs on the checklist too. Whether Google Search Console, Bing Webmaster Tools, a submitted sitemap and GA4 are included or extra can decide how much traffic you see in the first three months after launch.
What should you prepare before asking for quotes?
Comparable quotes start with a comparable brief. List the pages and features you need, two or three reference sites, your target launch date and which parts your team will edit itself. Even that much narrows the spread between vendors noticeably.
When quotes come back, ask for effort in person-days and the day rate per line item, not just a total. A vendor that can't estimate effort hasn't pinned down the scope yet, and the vaguer the scope, the longer the change-order negotiations near launch.
Before you request a quote
- Count unique layouts, separately from total pages
- List what your team must edit in the CMS, plus features like forms or search
- Pick two or three reference sites and note what you like about each
- Ask whether domain, hosting, licenses and taxes are included
- Confirm ownership of code and accounts, and the scope of post-launch support
Frequently Asked Questions
- Does a responsive website cost extra?
- Almost every quote now includes responsive behavior by default. The difference is depth. If the desktop layout simply reflows to fit a phone, the extra effort is minimal. If mobile screens are designed separately with touch-specific interactions, design and front-end effort typically rise 20–40%. Look for a line that mentions dedicated mobile mockups.
- When do projects end up costing more than quoted?
- Scope change is the usual culprit. Restructuring the navigation or adding features after design sign-off means redoing earlier stages. Exceeding the agreed revision rounds and late delivery of copy or photos push cost and schedule too. In what we see in practice, loosely scoped contracts commonly end up 10–30% over the original figure.
- Can we start on a template and move to custom later?
- Yes, but plan on rebuilding the design and code. Builder themes don't travel off their platform. What does carry over is your domain, your content and your URL structure, which underpins search rankings. So even on a template, settle your URL conventions from day one to keep the migration cheaper.
- Do we really need a maintenance contract?
- It isn't mandatory, but you do need to decide who handles what. A static brochure site often needs little beyond hosting and security updates. Once you have user accounts, payments or member content, a contract with a defined response time is the safer choice. If a monthly retainer feels heavy, start pay-per-request and switch once you know your real volume.
- How long does a website build take?
- Template sites typically take 2–4 weeks, semi-custom builds 6–10 weeks and fully custom builds around 10–16 weeks. The biggest source of delay usually isn't development; it's decisions and content on the client side. Naming a single approver and putting copy deadlines on the schedule before kickoff does more for the launch date than anything else.
EnterNext's system integration practice puts planning, design and development in one team. We break every quote down into effort per line item and build a working demo before any contract is signed. If you already have quotes in hand, bring them along and we'll lay them out in one table to see what's missing and what overlaps. Demo first.
Request a Free DemoLast updated:
Keep Reading
n8n vs Zapier vs Make vs RPA: How to Choose an Automation Tool
Feature lists won't settle it. Run volume, where your data lives, and who maintains it will — five options, one table.
Found on Google, Invisible on Naver: How to Get Found in Korea
Search Advisor, a Korean brand name, IndexNow and Smart Place, in the order we applied them to this very site.