OutDept

How Much Does a Website Really Cost in 2026? (Real Numbers, Not Guesses)

October 8, 2026·9 min read

"How much for a website?" is impossible to answer honestly in one number. Here's what actually drives the price up or down, and the real ranges for the kinds of sites most businesses actually need.

"How much does a website cost" is one of the most searched questions in web development, and one of the least honestly answered — because the true answer is "it depends on what you actually mean by website," and most articles skip straight past that to a made-up number. A five-page brochure site and a booking platform with live inventory are both "a website" in casual conversation and roughly ten times apart in real cost.

This breaks down what actually drives the price, and gives realistic ranges for the categories most businesses fall into — so a quote can be sanity-checked instead of taken on faith.

The four things that actually set the price

  • Number and complexity of unique page templates. Ten pages that are all the same layout with different text cost far less than five pages that are all structurally different.
  • Whether there's a back-end. A static site with no logins, no database, and no dynamic content is a different category of project entirely from one that stores data, processes payments, or has user accounts — this single factor swings cost more than any other.
  • Content and design originality. A site built on a proven template with the client's own text and images is cheaper than a fully custom visual design built from scratch — neither is wrong, they're different products at different price points.
  • Integrations. Every third-party system a site needs to talk to — a CRM, a payment processor, a booking calendar, an inventory system — adds real engineering time, because the other system's quirks aren't optional to work around.

Realistic ranges by category

These are the categories most quotes actually fall into, from simplest to most involved:

  • Brochure / landing site (a handful of static pages, no back-end, template-based): the least expensive category, and often the right call for a business that just needs a professional presence.
  • Standard business website (multiple pages, a contact form, light CMS for the client to edit content, moderate custom design): the range most small and mid-size businesses actually land in.
  • E-commerce or booking site (product catalogue, cart, payment processing, inventory or availability logic): meaningfully more, because a working payment flow and inventory sync are real engineering, not template configuration.
  • Custom web application (user accounts, a real back-end, business-specific logic — a portal, a marketplace, an internal tool): the widest range, because "custom" by definition means the price is set by what's actually being built, not a category average.

Why two quotes for "the same website" can differ by 3x

The most common reason isn't that one vendor is overcharging — it's that the two quotes are scoped against different assumptions about what "the website" needs to do, and neither side wrote those assumptions down. A quote that seems to include everything cheaply is often quietly excluding the back-end work, the content migration, or post-launch support — and that gap surfaces later as a change order, not upfront.

The ongoing cost nobody asks about upfront

The build price is not the full cost of owning a website. Hosting, a domain, an SSL certificate, security patches, and periodic content updates are recurring costs that continue for as long as the site exists — usually a small fraction of the build cost per year, but worth asking about before signing, since a suspiciously cheap build quote sometimes recoups the difference through an expensive, mandatory maintenance contract later.

How to get an honest quote

Write down, before asking for pricing, what the site actually needs to do — not what it should look like. Does it need to take payments? Store user accounts? Talk to an existing CRM or booking system? A vendor that asks these questions before quoting is scoping the real project; a vendor that quotes a number off a one-line description is quoting a guess.

OutDept scopes a website against what it actually needs to do before naming a number — so the quote reflects the real project, not a guess that turns into change orders later.

Have a project behind this question?

Tell us the problem, not the service name — we'll scope it properly before quoting anything.

Talk to us

Web Development

All articles