Start with the kind of website you are buying
A focused brochure or marketing site usually concentrates on positioning, services, proof and enquiries. Its complexity comes from content strategy, bespoke design, responsive development and a content-management setup that is genuinely comfortable to use. A larger editorial or ecommerce site adds content models, search, filtering, products, payments, integrations and migration work.
A web application is a different category again. Accounts, permissions, dashboards, calculations, workflows and live data create product-design and engineering work that cannot be estimated responsibly from a page count. If an agency quotes all three in the same way, the proposal is probably hiding important assumptions.
- Focused marketing site: a clear story, a manageable set of page types and a strong enquiry path
- Content-rich or ecommerce site: structured content, migration, search, products or integrations
- Web application: authenticated users, business logic, workflows and ongoing product development
What changes the cost
The number of pages matters less than the number of distinct decisions. Ten pages built from three well-designed templates can be simpler than four pages where each one behaves differently. Brand work, photography, copywriting, animation, complex forms, CRM connections, multilingual content and unusual browser requirements all add real work because each introduces another design, implementation or testing path.
Content readiness is often the quietest variable. A site cannot be designed around copy that does not exist forever. When messaging, page hierarchy and proof are unresolved, a good studio has to help solve them. That is valuable work, but it belongs in the scope rather than being treated as a free prelude to design.
Budget for the life of the site, not only launch day
Domains, hosting, monitoring, backups, security updates and small improvements continue after launch. Some sites need almost no maintenance beyond platform updates; others depend on APIs, evolving browsers, campaign landing pages or regular content changes. Ask who owns each responsibility and what happens when something breaks on a Friday afternoon.
The cheapest launch can become expensive if the site is slow to edit, difficult to deploy or tied to a supplier that disappears after handover. A clear component system, documented integrations and sensible hosting make future changes cheaper. They also give you the option to change partners without rebuilding everything.
- Hosting, backups and uptime monitoring
- Security and dependency updates
- Analytics, consent and search-console checks
- Content support and incremental improvements
How to get a quote you can compare
Write down the business result, the audiences, the essential journeys, the content you already have, the systems involved and the date that matters. Share a budget range if you have one. It lets a studio shape the right answer instead of spending time guessing whether you want a light refresh or a ground-up platform.
Then compare the assumptions, not just the totals. Does the proposal include content design, mobile states, accessibility, CMS training, redirects, analytics, launch support and post-launch fixes? A precise scope may look longer, but it usually creates fewer surprises. If the project still has unknowns, pay for a short discovery phase before asking anyone to promise a fixed build.