Most clients who ask how much website creation costs have already made a mental estimate based on what someone told them at a conference, what a competitor spent, or what they saw on a freelancer platform. That number is almost never right — not because agencies inflate prices, but because the scope behind any two websites rarely resembles each other at all.
The five factors that actually determine price: the technology stack, the CMS, the volume of work, whether you're using a template or custom design, and the integrations required. Get those clear and the number becomes predictable.
Technology Stack
The most common mistake in early-stage website budgeting is picking a technology before defining the product. Technology choice drives cost in two ways: development hours and long-term maintenance.
A marketing website built on Next.js with a headless CMS costs more to build than the same site on WordPress — because the development work is more complex and the talent pool is smaller. But it will likely cost less to maintain, load faster, and scale better if the traffic ever grows. That trade-off is not a universal argument for either option. It's a scoping decision.
For most B2B service businesses — agencies, SaaS companies, professional services firms — a modern headless setup (Next.js + Sanity or Contentful) runs $8,000–$20,000 for an initial build. A comparable WordPress site built correctly — not using a cheap theme and 40 plugins, but with a properly structured theme and clean architecture — runs $4,000–$12,000. The gap shrinks when you factor in future development costs. Every WordPress plugin that does something a headless CMS would handle natively adds debt.
Custom-built platforms — no CMS, no framework defaults — exist for good reasons: highly specific workflows, proprietary data models, performance requirements that off-the-shelf tools can't meet. They also start at $30,000 and go up from there. Unless there is a specific technical reason a standard stack won't work, custom platforms are almost never the right call for marketing websites.
Template vs. Individual Design
This is the single clearest cost driver in website creation, and it's the one most clients underestimate.
A template-based site uses a pre-built visual structure — either a purchased theme or a library of pre-designed components — customized with your brand colors, fonts, and content. A custom-designed site builds the visual system from scratch: layouts, components, interactions, responsive behavior at every breakpoint. The difference in hours is significant. A template-based site might take 80–120 hours of design and development. A fully custom-designed site takes 300–600 hours for the same number of pages.
Templates are not a failure mode. For a startup validating a product, a professional services firm that needs a credible online presence without a large investment, or a content-heavy blog, a well-executed template is the right call. The ceiling becomes visible when brand differentiation matters — when the site is a sales tool and the visual experience is part of the pitch. At that point, a template that looks like every other business on the same theme library is an active liability.
In practice: template-based websites run $1,500–$6,000 depending on complexity. Custom-designed websites run $8,000–$35,000 for the design and development combined, with enterprise-level work going higher. The overlap between those ranges is where most of the budget conversations happen.
CMS Choice
The CMS determines who controls the site after launch and at what cost. It's also the factor that clients think about last and end up regretting most.
WordPress powers roughly 43% of the web because it's flexible, has an enormous plugin ecosystem, and most developers know it. That ubiquity is also the source of its problems: WordPress sites accumulate plugins, plugins accumulate conflicts, and sites that were fast and secure at launch degrade over time without active maintenance. For a business that wants to own its content, update pages without a developer, and stay on a familiar interface, WordPress is a reasonable choice — with the caveat that it requires ongoing maintenance budgets of $1,000–$4,000 per year to keep it functional.
Headless CMS options — Sanity, Contentful, Strapi — separate the content management layer from the frontend entirely. Editors work in a structured interface; developers control how content renders. This approach costs more upfront but tends to produce faster sites, cleaner architecture, and fewer maintenance emergencies. It makes the most sense when the content model is complex (multiple content types, localization, programmatic pages) or when the frontend needs to serve multiple channels simultaneously.
Shopify occupies its own category for e-commerce. The platform handles payments, inventory, and hosting in exchange for transaction fees and a monthly subscription. For a business moving $0–$2M per year in online revenue, Shopify is almost always the correct choice over a custom WooCommerce or Magento build. Above that threshold, the transaction fees become large enough that a custom solution starts penciling out.
The CMS decision is not a technology preference. It's a question of who will be editing the site, how often, and how much they're willing to depend on a developer for routine tasks. Answer that honestly before the architecture conversation starts.
Volume of Work
More pages and more features cost more money. That sounds obvious, but scope is where most website projects overrun their budgets — not because agencies quote wrong, but because clients add to scope after the project has started.
A five-page brochure site — homepage, about, services, team, contact — is a fundamentally different project than a site with 30 service pages, a blog, a case study library, a careers section, and a client portal. The difference isn't just page count. It's content architecture, internal linking structure, CMS configuration, and design system complexity. The five-page site takes four to six weeks. The latter takes three to five months.
One pattern I've seen repeatedly: a client scopes a lean website, launches it, sees it working, and immediately wants to add features that weren't in the original plan — a quote calculator, a dynamic filtering system for a service catalog, a multilingual setup. Each of those is a separate project. Starting with a minimal viable scope and expanding is the right strategy. Starting minimal and assuming it's almost free to expand is where the budget surprises come from.
Integrations
Every system a website needs to talk to adds complexity. The cost lives in the edge cases, not the connection itself.
Connecting a CRM — HubSpot, Salesforce, Pipedrive — to a contact form sounds straightforward. The integration work itself might take four to eight hours. The scoping conversation, however, quickly surfaces questions: Which fields map to which CRM properties? What happens to duplicate contacts? Who owns the lead routing logic? Does the form need to segment leads before sending them to the CRM? Those questions add hours. A simple CRM integration typically runs $800–$2,500 when done correctly.
Payment integrations — Stripe, PayPal, local payment providers — add more complexity because they touch money and therefore require testing at a level most content integrations don't. A Stripe integration for a subscription product with multiple pricing tiers, proration logic, and dunning emails is a $5,000–$15,000 project on its own.
Third-party booking systems, ERP connectors, custom API integrations, and data syncs with external databases all follow the same pattern: the connection is cheap, the logic is expensive. Budget for integration work separately, not as a line item buried inside the main website estimate.
Analytics setup is often left off integration lists entirely and then becomes a problem post-launch. GA4 configured properly — with conversion events, channel grouping, and goal tracking — takes 8–16 hours. Skipping this means launching a site with no reliable data about what it's actually doing.
What the Total Actually Looks Like
Combining these factors: a five-page marketing site on WordPress with a purchased theme, basic contact form, and no integrations beyond GA4 runs $2,500–$5,000. A 20-page custom-designed site on a headless stack with CRM integration, blog, and a proper analytics setup runs $18,000–$35,000. A multi-language e-commerce site with custom design, Shopify or custom checkout, payment integrations, and ERP sync starts around $40,000 and scales with scope.
The mistake is comparing those numbers against each other without comparing the scopes. A $3,000 WordPress site and a $30,000 custom build are not two prices for the same product. They're two different products solving different problems.
Before asking how much website creation costs, define what the website is supposed to do in the first 12 months. That answer determines the technology, the design approach, the CMS, the integrations needed, and the realistic scope. The price follows from that — not the other way around.
If you're working through this for a real project and want a sanity check on scope or a second opinion on an existing quote, we're happy to take a look. We build websites and web apps — the conversation is free and we'll tell you if something doesn't add up. See how we approach website projects, or reach out directly.
Get in touch