Compare the scope before comparing the price.
Two website proposals may cover very different work. One might include design and launch only, while another includes content editing, data migration or a content management system. Ask what will be delivered before comparing the total price. A meaningful comparison is difficult without a written breakdown of pages, screen types, languages and features.
Functionality matters as much as page count.
A five-page company website and a five-page membership system do not require the same development effort. Enquiry forms, reservations, permissions and external integrations need their own analysis and testing. Distinguish reusable page templates from entirely different layouts. A price-per-page comparison alone can obscure the actual scope.
Agree who is responsible for content and design.
Responsibility for the logo, copy, product information and photography affects the schedule. Adapting an existing theme and designing a bespoke interface involve different processes. Check how the proposal handles mobile layouts, design approval and revisions. If content is not ready, ask for a separate plan to prepare it.
Include the costs that continue after launch.
Domains, hosting, paid plugins, email and maintenance can all create ongoing costs. Consider first-year fees separately from renewal pricing. Technical updates, content entry and new feature development are different services; ask which are included. Account ownership and access arrangements are also important parts of the proposal.
Use the same brief when requesting proposals.
Create a short brief covering your objective, pages, essential features, existing website and preferred launch window. A service business may prioritise detailed service pages and an enquiry form, while a manufacturer may need a multilingual product catalogue. Sharing the same brief makes it easier to understand which work accounts for differences in price.
Before you decide: a checklist
- Are the pages and features to be delivered documented?
- Are content, imagery and licensing responsibilities clear?
- Is the distinction between revisions and new requests explained?
- Are renewals, maintenance and hosting priced separately?
- Are management access and handover terms defined?