What a website actually costs

The price is scope, not pages

The single most common mistake in pricing a website is counting pages. A ten-page site where every page is the same layout with different text is a small job. A three-page site with a login, a database, and payment processing is a large one.

What drives cost is behavior. A page that displays information is cheap. A page that takes input, validates it, stores it, and does something with it later is not. Every place your site touches money, accounts, or another system is where the real work lives.

Where the money actually goes

For most projects the cost breaks down into a handful of buckets, and knowing them lets you compare quotes honestly rather than guessing.

• Design and scoping. Deciding what the thing is before building it. Skipping this is the most expensive shortcut there is, because you pay for it in rebuilds.
• Front end. The part customers see. Templates make this cheap; genuinely custom interfaces do not.
• Back end. APIs, databases, accounts, email, payments. Usually the largest and least visible line item, and the one that determines whether the site holds up under real use.
• Content and migration. Moving existing pages, products, and images across without losing search rankings. Easy to underestimate and painful to get wrong.
• Ongoing care. Hosting, updates, backups, and fixes. Some quotes include this; many do not, and that difference alone can explain a wide spread.

Why the cheap quote is sometimes the honest one

A small business that needs a clean five-page marketing site genuinely does not need a custom application. If someone quotes you four figures for that, and the scope really is that small, the quote is fair.

The danger is not the low number. It is a low number attached to scope that quietly grows. A quote that says "website" without saying what happens when you want to take payments, or add a second location, or change the layout, has not priced your project yet.

Questions worth asking before you sign

These five questions separate a real quote from a placeholder, and any competent shop will answer them without flinching.

• What is explicitly not included? The omissions are where budgets break.
• Who owns the code, the domain, and the hosting accounts when this is done? The answer should be you.
• What happens when I want to change something myself?
• What does ongoing maintenance cost, and what does it cover?
• Can you show me a site you built that does the same kind of thing?

What we do differently

We price per project and show the reasoning, because a number without a reason is not a quote, it is a guess. Every proposal says what is included, what is not, and what a change would cost.

We also tell you when you do not need us. If a template genuinely fits your situation, we will say so, even though it is a smaller job for us. That is cheaper for you than a custom build you did not need, and it is the reason clients come back for the work that does.