The number of pages is only part of the picture
Counting pages gives a sense of the size of a website, but it does not describe all the work. A simple contact page and a service page with original content, visual resources and several sections require different amounts of preparation. It also matters whether pages share a structure or each needs its own approach. The content and the purpose of each page influence the work as much as the count.
When asking for a proposal, describing what each page needs to explain is more useful than choosing a number without context. Start with a list of services and questions you want to answer. We can then consider what needs its own page and what can sit within a section. The aim is to meet the visitor’s needs through a structure that is easy to understand.
Who prepares the text and materials?
Content is a substantial part of a website project. Working with reviewed text and available photographs is different from organising scattered information, writing pages or preparing new resources. Revisions are part of that work too, particularly when several people are involved or details of a service still need confirming. Those responsibilities affect what can be included in a meaningful proposal.
Before comparing quotes, check what counts as content and who is responsible for it. Identify the materials you already have and what is missing. If images, typefaces or other third-party resources are needed, their licences and terms should be considered. This inventory makes the proposal clearer and avoids treating unfinished preparation as something that has already been taken care of.
Features change the scope
Presenting a service with a way to get in touch is different from handling bookings, payments or user accounts. Every feature introduces decisions, usage scenarios and checks. A connection to an external tool may also depend on how that tool works, the permissions available and the options its provider offers. The visible button is often only a small part of what needs to be built and reviewed.
Explain what visitors should be able to do and what you need to manage yourself. That lets us consider a suitable solution without assuming a particular tool is necessary. It also helps to separate the initial development from any subscriptions or usage costs. A proposal should make those dependencies visible so you can assess the practical implications before deciding.
Each language needs its own review
Adding a language means preparing and reviewing another version of the content. Menus, buttons, descriptions and any messages users see need attention as well as the main text. Translations can take up different amounts of space, so readability and presentation should be checked within the website. A language switcher alone does not account for that work.
To define the scope, explain which languages you need from the first day and who will supply or review each translation. It also matters whether every page will be available in every language. The versions need to remain consistent when your business information changes. This decision therefore affects both the initial build and the work involved in future updates, especially if different people manage the translations.
Building, publishing and upkeep are different tasks
Building the website is one part of the whole picture. The domain, hosting, external tools and ongoing administration may have their own terms. Depending on the technology chosen, updates or other tasks may also need planning. It helps to know which of these matters the proposal covers and which remain with the owner or other providers. They should be identifiable even when several services appear in one proposal.
Ask who will own the accounts, how access will be handed over and how you will request or make changes. Clarify what counts as a review before delivery and what is considered additional work later. Having those responsibilities in writing makes options easier to compare on equal terms and helps you understand what you will need once the website is live.
How to compare two proposals fairly
Two proposals can both describe a professional website while including very different work. Review the pages, content, languages, features and planned checks. Look at how revisions, external services and handover are defined too. If something is not explained, it is worth clarifying before comparing only the totals. A useful comparison depends on knowing whether you are looking at similar responsibilities and deliverables.
To prepare your enquiry, describe the business, the main objective and the materials available. Add the essential features and any constraints you already know about. If you are unsure about the number of pages or the technology, say so. That information helps us define what the project actually needs and prepare a proposal you can assess without having to guess what is missing.