Ask five people to quote the same small business website and you can get $500, $3,000, $8,000 and $15,000 back. That spread makes it look like somebody must be lying. Usually nobody is — the four quotes are for four different things, and nothing in them says so.

What the number is actually made of

Almost all of the cost is time, and the time goes into four buckets that vary enormously between quotes:

Design. A template lightly adjusted, or something drawn for your business. This is the single biggest swing.
Content. Whether you're handing over finished text and photos, or someone has to interview you, write it, and arrange a shoot. Content is the most commonly underestimated line and the most common reason a build stalls for months.
Functionality. Five pages and a contact form is a different project from booking, payments, logins, or inventory. Each of those is not a feature but a system, with its own failure modes.
Number of pages. Straightforward, and the only part most people think to ask about.

The ongoing costs nobody mentions

The build is a one-off. These aren't, and a quote that omits them isn't complete:

Domain — roughly $15–40 a year. Make sure it is registered in your name, not your developer's.
Hosting — anywhere from free to a few hundred a month. A brochure site for a local business genuinely can run on a free tier; an online store cannot.
Email — around $7 per person per month for a proper address on your own domain.
Maintenance — updates, backups, broken links, the things that rot on their own. Can be a retainer or a few hours a year, but it is never zero. See why rankings decay for what skipping it costs.

How to read a quote

The questions that separate a real price from an opening bid:

Is this fixed, or an estimate? The most expensive projects I've seen go wrong were hourly ones where the scope drifted and nobody called it.
How many revision rounds, and what counts as one? Vague revision terms are where budgets die. "Unlimited revisions" usually means the price already assumes a fight.
Who owns what, and what happens if you stop paying? These are two questions, and the second one is the one people forget to ask. See below — it deserves more than a line.
What happens after launch? Who fixes a broken form in March? Is that included, billed, or nobody's job?
Is content included? Ask directly. "Client provides copy" buried on page three is how a $3,000 project becomes a $3,000 project plus eighty hours of your own time.

Buying a site versus subscribing to one

Both models are legitimate and the difference is worth understanding before you sign anything, because it changes what you are actually buying.

Buying means you pay once to have the site built and it is yours — you can move it to another host, hand it to another developer, or leave it alone for three years. You carry the hosting and the upkeep from there, or pay someone to.

Subscribing means a monthly fee covers the build, the hosting, and the changes, and the site is live for as long as you are paying. Lower to start, no large cheque, someone is accountable for it every month — and if you stop, the site comes down. For a lot of small operators that trade is the right one: a few hundred a month against one job is easy arithmetic, and the alternative is often a site that was bought once and then rotted for five years because nobody owned the upkeep.

The problem is not the subscription. The problem is a subscription nobody told you about. Two specific things separate a fair deal from a trap:

Is your domain in your own name? This is the one that matters most. The domain is your address — every card, van, invoice and Google listing points at it. If it is registered to your developer rather than to you, you cannot leave without losing it. Check this whichever model you choose.
Were you told, plainly, before you signed? A builder who says up front "this is monthly, and it comes down if you stop" is selling you a service on honest terms. One who lets you believe you bought something and only mentions it when you try to leave is doing something else entirely.

Ask both questions out loud on the first call. The answers tell you a great deal about how the rest of the relationship will go.

Roughly what buys what

Ranges, not prices — every project differs, and anyone quoting from a webpage without talking to you is guessing:

Under $1,000 — a template with your text dropped in, or a DIY builder plus your own weekends. Fine for proving a business exists. Not usually built to be found in search.
$1,500–$5,000 — where most local service businesses land. A handful of pages, built for your business, structured so it can rank, with someone accountable when it breaks.
$5,000–$15,000 — custom design, real content work, or actual functionality: booking, payments, a store, integrations with software you already run.
Beyond that — you're buying software with a website attached, and it should be scoped like software.

The part worth internalising

A cheap site that nobody can find costs more than an expensive one that brings in work — the money is just spent more quietly. The right question isn't what a website costs. It's what one job is worth to you, and how many the site needs to bring in before it has paid for itself.

For most trades that number is small, often one or two jobs. If a builder can't have that conversation with you plainly, that tells you something useful about how the rest of the project will go.

What a website actually costs