If you've Googled "how much does a website cost," you've seen the same useless answer: "It depends." It's technically true — and it's also a sign the person answering doesn't want to be useful. Here's what the answer actually depends on, and the questions that will get you a meaningful number from anyone you talk to.
Why "it depends" is a real answer
A website isn't a product. It's a custom build shaped by your goals, your content, your audience, your stack, and how much ownership you want at the end. Two teams asking for what looks like the same thing on a brief can end up with projects of completely different scale — because the assumptions behind the surface request are different.
So the useful question isn't "what does a website cost?" It's "what does my website need to do, and who is the right team to do it?" Once that's clear, the number usually follows — and it's a number you can defend internally.
Scope tiers, not price tiers
Websites cluster into rough tiers based on what's being built, not what's being charged. Knowing which tier you're in tells you which conversations matter and which features to insist on.
Single page — one message, one audience
A focused landing page or coming-soon site. One clear action. Your existing brand applied. Usually built on a modern framework or a visual builder. Timeline: days, not months. Useful for: validating an offer, capturing leads for a single campaign, supporting a launch.
Small business site — a handful of pages, edited by you
Home, about, services, contact, plus a blog or portfolio. A content management system so your team can update it without touching code. Mobile-optimized, with the basics of search engine setup. Timeline: a few weeks. This is where the majority of small businesses land, and the quality of the strategy and writing matters more than the platform.
Custom marketing site — designed from scratch, built to convert
A site built around your funnel rather than your org chart. Custom components, motion, integrations with your CRM and analytics, content workflows for your marketing team, and a system that holds up as you add pages over time. Timeline: a couple of months. Useful for: companies treating the site as a primary growth channel, not a brochure.
E-commerce — selling products online
Catalog, cart, checkout, payments, shipping, taxes, inventory, order management, and the email flows that recover abandoned carts. The conversation here is less about design and more about operational complexity: how many SKUs, how many variants, what integrations with your warehouse or ERP. Timeline: a few months for a focused store; longer for a large catalog or multi-region setup.
Custom web app — software, not a site
Authentication, a database, dashboards, third-party integrations, ongoing iteration. The conversation here stops being about pages and starts being about product: who the users are, what the core jobs-to-be-done are, what the data model looks like, how it gets maintained after launch. Timeline: many months. Useful for: SaaS, internal tools, marketplaces, anything where the website is the business.
The 5 decisions that shape the scope
Most of the variation between quotes comes down to the same handful of decisions. Get these right and the rest of the conversation is straightforward.
- Who is writing the copy? A site with real, considered writing almost always outperforms a more expensive site with placeholder text nobody replaces. Decide this before you sign.
- Do you have a brand? Without a logo, color system, and typography that the team can build against, expect brand work to be part of the scope — and the most leveraged part of it.
- How many integrations, and which ones? Every CRM, payment processor, email tool, or analytics platform you connect adds real setup time and ongoing maintenance. Make a list before getting quotes — it'll save you a round of revisions.
- Who is maintaining it after launch? A website is not a one-time deliverable. Decide in advance whether your team handles updates, the agency does, or there's a shared plan — and what that plan costs in time, not just money.
- What's the timeline, and why? Aggressive timelines force parallelization that adds cost. A clear, honest timeline lets a agency price accurately instead of building in a rush premium.
How to read any quote you receive
A good quote tells you what you're getting and what you're not. Before signing anything, get clear answers to these:
- What deliverables are explicitly included? (Pages, components, integrations, copywriting, photography, brand work.)
- What is excluded, and what would it cost to add?
- How many rounds of design and revision are included?
- What does the team look like — senior people doing the work, or a senior-led pitch handed to juniors?
- Who owns the code, the design files, and the content at the end?
- What happens if scope changes mid-project?
- What does support after launch look like, and at what cost?
Red flags worth walking away from
- A fixed quote with no discovery conversation. If they can price it without asking what you need, they're quoting a template.
- A pitch deck full of logos and case studies, but no specifics on who will actually work on your project day-to-day.
- Vague language about "phases" and "ongoing support" with no structure or cost attached.
- Pressure to pay most of the project up front, before any work has started.
- No clear answer on what happens after launch — who fixes a bug at month three, who updates a dependency, who answers when something breaks.
Green flags worth paying more for
- They push back on the brief. Agencies that just say yes to everything are agencies that don't think.
- They ask about your business, not just your site. The team that understands your goals makes better product decisions than the team that only understands your wireframes.
- They show work that looks like yours in shape, not just in aesthetic. The portfolio is matched to the problem, not the other way around.
- They write down what happens after launch, in detail, before you ask.
How to think about payment structure
Whatever the final number is, the way it's collected tells you almost as much as the number itself. A healthy engagement splits the investment across clear milestones — typically a deposit on signing, a payment on design approval, and a final payment on launch. You should never be asked to hand over everything before any work exists, and you should never be asked to hand over the final payment before you have something to evaluate.
If a agency's payment terms feel uncomfortable, the project will too. That's a useful early signal.
"The cheapest proposal is almost always the most expensive project. Build cost is a one-time number; the cost of doing it twice is forever."