Last updated: September 17, 2026
Key Takeaways
- It is the total cost to launch and keep the site usable for 12 months.
- They approve a $4,000 build and forget that the site still needs hosting, plugin renewal, and occasional developer time after launch.
- This is why “How much does a website cost?” is the wrong question by itself.
- It often shows up as weak content structure, poor mobile behavior, and limited control over SEO.
A website can cost a few hundred dollars, a few thousand, or well into five figures — and that spread is normal. If you are asking how much does it cost build website, the answer is usually a range, not a single price: a few hundred dollars for the simplest DIY setup, a few thousand dollars for a small business site, and well into five figures for custom builds or e-commerce. The real cost of how much does it cost build website also includes hosting, domain registration, content, maintenance, and any integrations you need after launch. In practical terms, the question is less about a one-time quote and more about what the site must do in its first 12 months.
I write about web strategy and production cost because the number that matters is not the build quote by itself. It is the total cost to launch and keep the site usable for 12 months. Plain and simple.
How much does a website cost, really?
Budget for setup plus ownership. That is the short version. A domain name is usually an annual fee; hosting is usually monthly or annual; design and development are the one-time build costs; content, photos, and maintenance keep the site alive.
A useful planning range looks like this:
- DIY website builder site: often the lowest upfront cost, but you still pay for the platform plan, domain, and sometimes paid templates or apps.
- Freelance-built small-business site: commonly used for 5–15 pages, a contact form, and basic SEO setup.
- Agency-built custom site: typically chosen when brand, content structure, or integrations matter more than speed.
- E-commerce or membership site: costs rise because payment flow, product data, tax setup, and security add real work.
The mistake most people make is pricing only the visible front end. A 10-page marketing site with a polished homepage may still need copywriting, stock imagery, analytics setup, form spam protection, mobile QA, and accessibility fixes. Those pieces are not optional if the site has to perform. Otherwise, the budget turns into a mirage.
A second mistake is confusing build cost with marketplace cost. A builder template can look inexpensive until you add email marketing, booking, multilingual support, or abandoned cart tools. Those extras stack up fast.
For a neutral outside reference on the kinds of costs and responsibilities that come with a public site, the U.S. government’s plain-language guidance on website accessibility and digital services is a useful starting point: U.S. Web Design System and the ADA’s public guidance from the U.S. Department of Justice on accessible digital content. For cost planning and maintenance practices, see Google Search Central and the W3C WCAG 2.2 standards.
What drives the price up?
Scope. Not page count. A 5-page site with plain content can cost less than a 3-page site with custom animations, a booking engine, and a content migration from an old CMS.
The biggest cost drivers are:
- Design uniqueness.
A theme-based site is faster to assemble than a design system built from scratch. If you want a distinctive brand look, expect more strategy, more revision rounds, and more front-end work. - Custom functionality.
Contact forms are cheap. Filters, calculators, gated content, member accounts, quote builders, and CRM sync are not. Anything that behaves like software gets priced like software. - Content volume.
If the site needs 20 service pages, 50 product pages, or a blog migration with redirects, the content work can rival the design work. - Integrations.
Connecting the site to Stripe, HubSpot, Salesforce, Mailchimp, QuickBooks, shipping tools, or inventory systems adds setup and testing time. - Compliance and quality control.
Accessibility review, privacy/cookie consent, security hardening, and performance fixes can add cost without adding visual drama. They still matter. - Who is writing the content.
If you hand over final copy and images, the build is cheaper. If the vendor is also interviewing, writing, editing, and sourcing, the quote rises for a reason.
This is why how much does it cost build website is the wrong question by itself. A better one is: What must the site do on day one, and what can wait? That single decision can change the budget more than the platform choice does. And yes, that’s where the real headache usually lives.
Should you use a website builder or hire a designer/developer?
Use a website builder if speed, control, and lower upfront spend matter most. Hire a designer/developer if the site must convert well, support unusual workflows, or reflect a brand that cannot look template-driven.
Here is the clean comparison.
| Criteria | Website builder | Designer/developer | Winner for [condition] |
|---|---|---|---|
| Upfront setup | Fastest path for a basic site | Slower because design and development are built to spec | Builder for launch in days |
| Visual originality | Limited by templates and theme structure | Can be built around your brand system | Developer for brand-specific design |
| Custom features | Often plugin- or app-dependent | Can be coded to match the workflow | Developer for nonstandard needs |
| Ongoing maintenance | Usually simpler, but app sprawl can add friction | Needs a maintenance plan or retainer | Builder for low-complexity ownership |
| SEO control | Good enough for many small sites | Stronger control over architecture and performance | Developer for competitive search markets |
| Accessibility work | Depends heavily on theme quality and user setup | Can be addressed more deliberately | Developer for regulated or public-facing sites |
| Editing simplicity | Usually easier for nontechnical staff | Can still be easy if the CMS is set up well | Builder for solo operators |
| Total long-term flexibility | Good within the platform’s limits | Better if the business model may change | Developer for evolving requirements |
The builder wins for the solo owner with a brochure site, a contact form, and a hard budget. It loses when the site becomes a process hub. A builder can also become expensive in a different way: app fees, premium themes, and workaround after workaround can trap you inside someone else’s product choices. Sand in the gears, basically.
The designer/developer route wins when the site must do more than present information. A service business with multiple locations, structured content, booking rules, and SEO competition usually needs more than a theme. The drawback is predictable: more cost, more time, and more dependence on the person who built it if the handoff is weak.
If your site’s primary job is to exist and answer basic questions, use the builder. If its job is to support revenue, automation, or a distinct customer journey, hire the specialist.
How much does it cost to build a website with an agency?
An agency is the right choice when the site needs strategy, project management, content structure, design, development, and QA under one roof. It is not the right choice for a page-count-only project.
An agency quote often includes several roles that a solo freelancer may bundle less formally: discovery, UX planning, wireframes, copy support, design review, development, testing, launch, and post-launch fixes. That coordination costs money, but it also reduces the odds that the site launches with gaps between design and implementation.
The strength of an agency is not just polish. It is process. A real agency build is better for:
- businesses with multiple stakeholders;
- rebrands;
- migrations from an old CMS;
- e-commerce with custom rules;
- sites that need accessibility review and QA;
- teams that need documentation and handoff.
The downside is equally real. Agencies can be overkill for a local accountant, a single consultant, or a 6-page brochure site. You may pay for meetings, account management, and process layers you do not need. If the site does not justify cross-functional work, the agency model becomes expensive overhead.
A solid middle ground is an agency for strategy and design, then a smaller in-house or contractor setup for maintenance. That split can keep the launch quality high without tying every minor edit to a large retainer.
If you want a standard to cite when comparing vendors on accessibility and structure, the W3C’s WCAG 2.2 is the main benchmark most serious web teams work against.
What hidden costs do people miss?
The hidden costs are usually the reason a website budget breaks. A site that appears affordable on paper can grow by 20% to 50% once the real work is counted, not because vendors are hiding things, but because early estimates often omit necessary pieces.
The usual misses are:
- Copywriting. Someone has to write the pages, not just design them.
- Photography and illustration. Stock licensing, shoot days, or custom graphics can matter.
- Redirects and migration. Old URLs need to map to new ones or traffic leaks.
- Forms and spam protection. Forms without protection fill up fast.
- Analytics and tag setup. Without this, you do not know what the site does.
- Security and backups. These are boring until they fail.
- Accessibility remediation. Fixing contrast, keyboard navigation, alt text, and form labels after launch is more expensive than planning for them.
- Legal pages. Privacy policy, cookie notice, terms, and consent tools may be needed depending on your business and region.
One more hidden cost is decision time. If three people must approve every button color and headline, the project slows down. That delay turns into billable hours or missed launch windows.
The practical move is to ask every vendor for an itemized estimate with these lines separated: design, development, content, migration, integrations, testing, and post-launch support. If a quote lumps everything into one line, you cannot tell what you are buying.
What should you budget for in year one?
Budget more than the launch invoice. A realistic first-year website budget includes the build plus recurring operating costs.
For planning, think in these buckets:
- domain registration;
- hosting or platform subscription;
- premium plugins, apps, or extensions;
- email service;
- security, backups, and maintenance;
- content updates;
- occasional design or development fixes.
A simple site may only need light maintenance, but “light” still means updates, backups, and troubleshooting when something changes. The more integrations and custom features you add, the more maintenance matters.
This is where many buyers underbudget. They approve a $4,000 build and forget that the site still needs hosting, plugin renewal, and occasional developer time after launch. A site that is never maintained becomes slower, less secure, and more fragile, so if that risk matters to your business, consult a qualified professional about the right maintenance plan. For ongoing maintenance and security guidance, see the U.S. Cybersecurity and Infrastructure Security Agency and Google’s Search Essentials documentation.
If your business depends on leads or sales, that risk is not theoretical. A broken form or outdated plugin can cost more than the maintenance plan you skipped. If you are making financial or legal dependence decisions, consult a qualified professional before finalizing compliance-related choices.
When does a cheap website make sense — and when is it a bad idea?
A cheap website makes sense when the site is simple, low-risk, and replaceable. It is a bad idea when the site is part of how you earn money or handle customer data.
Cheap is fine for:
- a temporary event site;
- a portfolio with a handful of pages;
- a local business that mainly needs hours, address, services, and contact details;
- a proof-of-concept before funding or demand is clear.
Cheap is a bad fit for:
- e-commerce;
- booking-heavy businesses;
- companies in regulated sectors;
- any site that must integrate with internal systems;
- brands that cannot afford a generic look.
The downside of the cheapest route is not only visual. It often shows up as weak content structure, poor mobile behavior, and limited control over SEO, though the size of that impact depends on the builder, the template, and how much customization you can actually make. Fixing those later can cost more than doing them properly the first time.
If you need the site to support revenue, treat it as a business asset, not a line-item purchase, and talk with a qualified professional if you are unsure how much risk your budget can tolerate.
What should you actually choose?
Choose a website builder if you need a straightforward site live quickly, can live with templates, and want to keep upfront spend down. Choose a designer/developer or agency if the site must convert traffic, support custom workflows, or represent a serious brand. Neither if the real problem is not “build a website” but “decide what the business needs online first.”
That is the clean call.
A builder wins for a solo founder, local service provider, or small team that needs a usable site now and can accept platform limits. A specialist wins when the site must be tailored, integrated, or future-proofed. If you do not yet know the structure, content, or business goal, hiring a builder or agency too early is wasteful.
Exception scenarios where the answer flips
The verdict flips in a few specific cases. Here are the ones that matter.
- You already have a strong brand system and content plan.
In that case, a builder can be enough even for a professional site, because the hardest part is already done. - You need custom logic, not just pages.
If the site must calculate quotes, route leads by region, or handle member tiers, a specialist is the safer choice even if the budget is tight. - You expect rapid iteration.
Startups that will change offers monthly may do better with a flexible CMS and a developer who can adapt quickly.
