Page count is only one part of the work
Ten pages built from a consistent pattern can be simpler than three pages with specialised interactive behaviour. Look at the number of distinct page types, the depth of content and the design requirements. A service business may need a homepage, individual service pages, project examples and a quote form. A retailer also needs catalogue, cart and checkout decisions.
Content has its own scope
Copywriting, editing, original photography, image selection and product entry all take work. Check whether a proposal assumes that you supply finished content or includes help producing it. Clarify how many review rounds are included and who approves factual claims. A clear content plan prevents design work from stalling while important details are still being decided.
Connections change complexity
A simple enquiry form differs from a connection to inventory, appointment scheduling or a customer portal. The scope should identify the provider, the information exchanged, error handling and testing. Ask what happens when a third-party service is unavailable and who maintains the connection. A named integration is not enough detail to compare proposals.
Migration needs a deliberate plan
Moving an existing website may involve useful URLs, media, product data, account access or forms. Even when the visual design starts fresh, decide which existing content still serves customers. Redirect mapping, search checks and measurement setup should be visible items rather than assumptions. The size and condition of the old system affect the work.
Separate the build from running costs
Hosting, domain renewal, payment fees, licensed software, ongoing content work and maintenance may be billed separately. Ask which accounts your business owns, what happens if you change providers and what files or content are included in handover. A cheaper initial build may carry different operating requirements; a larger build should still explain its ongoing costs.
Compare proposals using the same brief
Ask each provider to state deliverables, exclusions, review process, dependencies, launch checks and support expectations. Share the same essential requirements with each so you can compare like with like. We provide a project-specific scope after reviewing your goals and current website; we do not publish an invented universal price that ignores the work.