How Page Count and Complexity Shape Website Cost

A ten-page website still leaves much unspecified. It might contain a homepage, about and contact pages, plus several service descriptions. Another ten-page project could include booking, checkout, accounts and reporting. The page total matches, but the design, implementation and testing effort differ.

This article presents SoSho’s suggested way to describe project scope. It explains estimation factors; the actual amount is determined through requirements review and a valid tariff or proposal for that project.

Imagine twelve service pages sharing an introduction, benefits, process and FAQ layout. Designing that template is one task; preparing and checking twelve sets of text and images is another. Template reuse does not remove the work of arranging and reviewing each page’s content.

A homepage, product listing, product detail page and customer portal may instead require four distinct layouts. Record both the final page total and the number of unique templates. This makes proposals from different implementation teams easier to compare.

A contact page with static details has a different scope from a form that accepts uploads, validates input, displays errors and sends data to a CRM. Complexity is not simply visual density: it includes rules, data, states and integrations.

For each feature, describe the successful journey and alternative states. Booking needs more than selecting a time: unavailable slots, changed selections, repeated requests and unsuccessful outcomes must also be specified. These decisions affect analysis, implementation and testing.

The first project is an eight-page brochure site: home, about, contact and five service pages sharing a layout. Copy is ready and the contact form is simple. Work centres on shared designs, approved content entry and checking different screen sizes.

The second also has eight pages but includes service selection, booking, payment, login and request tracking. It needs workflow rules and integration checks. These hypothetical examples show why equal page totals are insufficient grounds for equal estimates.

Supplying approved copy and images differs from commissioning writing, photography or illustration. Specify who produces content, how many entries are included and who reviews them. Migrating articles or products from an existing website also needs an explicit scope.

A bilingual site involves translation, RTL and LTR layout, titles and corresponding routes, beyond a language button. Bespoke visuals, animation, 3D models and interactive charts should also enter the estimate with a defined purpose and scope.

Domain registration, hosting or infrastructure, licences and external services may be separate expenses. Backups, updates, defect fixes and future development are different responsibilities. A proposal should state what is included initially and what is recurring or quoted separately.

Define acceptance criteria too: where form submissions go, which journeys must work, who receives administration training and which revision rounds are included. Reviewable details make the price easier to assess.

For an initial SoSho review, list each page and its purpose, then record functionality, content readiness and integrations. If some details remain open, identify the first-release priorities so a deliverable scope can be defined.

A narrower first release can make estimation more manageable. For example, service information and enquiry capture might come first, with a complex portal considered after its workflow is specified. Choose phases around actual business needs.