A custom website, designed and built by hand rather than assembled from a template, typically costs in the five figures for a marketing site, and scales from there into custom web application territory as complexity grows. That’s the honest headline. The range is wide because “website” covers everything from a sharp ten-page brand site to a logged-in product with a database behind it, and the price tracks the work, not the page count.
This is a breakdown of what actually drives that number, so you can read a quote and know whether you’re being charged for craft or for padding.
The honest ranges
Set aside the outliers, the hundred-dollar template gigs at one end, the seven-figure enterprise platforms at the other, and most custom work falls into a few bands:
- A crafted marketing site, bespoke design, hand-built, fast, search-engineered, a handful to a couple dozen pages, sits in the five-figure range. This is the category most founders and growing companies are actually shopping for.
- A content-heavy or multi-function site, complex navigation, integrations, a CMS your team will run, custom interactive pieces, sits at the upper end of five figures.
- A custom web application, dashboards, portals, logged-in products, anything with real software behind the interface, is scoped individually and priced by complexity, not by page. There is no honest flat number here, and anyone who gives you one without understanding the build is guessing.
Where a specific project lands inside those bands is a function of a few cost drivers, which is the part worth understanding. The full scope of what I build and how is on the custom web development practice page; the economics below apply whoever you hire.
What drives the cost up, and down
Six things move the number more than anything else:
- Design originality. A visual language built for your brand alone costs more than adapting a system, and looks like it. Templates are rented distinction, your brand wearing someone else’s suit. Bespoke design is most of why custom costs what it does.
- Custom functionality. Every feature that isn’t off-the-shelf, a configurator, a booking flow, a member area, an integration with your other systems, is software, and software is priced like software.
- Content and scale. More pages, more templates, more content to structure. A five-page site and a fifty-page site are different amounts of work even at the same level of polish.
- Performance and search engineering. Done properly, speed and search aren’t a line item added at the end; they’re built into the architecture. That discipline costs more up front and is most of what determines whether the site ever ranks.
- Integrations. Connecting the site to a CRM, a payment system, an email platform, or internal tooling adds real engineering, especially when those systems are particular.
- Stewardship after launch. A site is not a one-time purchase that stays fast and secure on its own. Ongoing care is a cost worth planning for, not discovering.
The same drivers work in reverse. A tighter scope, fewer custom features, and a smaller page count are all legitimate ways to bring a number down, far better than cutting the quality of the build itself.
Why the cheapest quote is usually the most expensive
The lowest bid almost always wins the wrong way. Here’s the mechanism.
A cheap custom site is cheap because something was skipped, the performance budget, the accessibility, the structured data, the conversion thinking, or the engineering quality that lets the site evolve. You don’t see the gap at launch. You see it eighteen months later, when the site is slow, won’t rank, can’t be extended, and has to be rebuilt from scratch. Now you’ve paid twice: once for the cheap build, once for the real one, plus the revenue the first site quietly failed to earn the whole time it was live.
A custom website earns its cost in three places a template never reaches: speed and search performance no page-builder matches, conversion paths designed around your actual customer rather than a generic layout, and the ability to evolve with the business instead of being torn down every two years. When a build is done right, the price is an investment with a return, not an expense to minimize.
What “search engineered in” should mean for the price
If a quote includes SEO, ask what that actually buys, because the word covers both real work and decoration.
Real search engineering is architectural: a fast, crawlable foundation, clean information architecture, structured data, and copy built on actual keyword research rather than guesses. It’s done while the site is built, not sprinkled on after. That’s part of why a properly engineered custom site costs more than a pretty one, and why it’s the version that still earns traffic years later. Ongoing search and demand work after launch is a separate discipline; it usually belongs with the digital marketing practice rather than the build itself, and it’s worth budgeting for distinctly.
Increasingly, builds also wire intelligence directly into the product, a search, a recommendation, an automation, from the AI practice. That’s custom web application work, and it’s priced accordingly.
How to budget for it honestly
Don’t start with a number; start with what the site has to do. A site that simply has to look credible and load fast is a different budget from one that has to rank in a competitive category, and both are different from a site that has to run part of the business. Define the job first, and the band it falls into becomes obvious.
Then insist on two things from whoever you hire: a fixed scope and a price quoted before work begins. Every project I take is scoped and quoted up front precisely so you never discover the cost at the invoice, and so the conversation stays about what the site should achieve, not what it might end up billing.
Your website is your most-visited room. The question worth asking isn’t “what’s the cheapest way to furnish it,” but “what does it need to earn, and what build will actually get it there.” Answer that, and the cost stops being a mystery and starts being a decision.