Website proposals are comparable only when they describe the same work. A «five-page website» might mean a template populated with your copy, or a project covering research, writing, bespoke design and integrations. The price difference alone does not tell you which approach fits your business.

Give every supplier the same brief

Describe the business, audience, website goal and primary action. Include the page list, languages, features and systems the site must connect to. Identify the materials you already have and the person responsible for approvals.

A testable requirement might be: «The quote form sends the name, email address and selected service to our team inbox and CRM». «We want an interactive website» does not define what must be built or tested. Share visual references with an explanation of what you like, rather than asking someone to copy them.

Separate the deliverables into clear categories

Ask the proposal to distinguish structure, copy, design, implementation and testing. Record the quantity and boundary of each category. If a blog is included, establish whether that means the template and CMS, or article writing as well.

• Pages: distinct templates and populated pages.

• Content: responsibility for writing, translation and entry.

• Design: an adapted template or a project-specific design.

• Integrations: forms, payments, bookings and external systems.

• SEO: metadata, indexing, redirects and page checks.

• Handover: access, training and documentation.

These distinctions expose costs that might otherwise emerge after work begins. Do not assume every activity associated with a website is automatically included.

Agree on what a revision means

A feedback round should consolidate the team's comments into one set. Adjusting a colour and introducing a booking system are different kinds of change. Ask how new requests are estimated and who approves them.

Set review points for the structure, design, test version and launch. A realistic schedule includes the client's time for supplying materials and making decisions. Delayed approvals can move subsequent stages.

Compare operating costs as well as the launch price

List hosting or platform subscriptions, domain renewal, licences, maintenance and paid integrations separately. Ask who owns the accounts and what happens when the engagement ends. Understand the content export options and remaining dependencies.

A monthly fee can cover valuable work, but the activities and support limits should be explicit. Conversely, a proposal without maintenance does not mean the website will require no administration.

Request acceptance criteria

Before choosing, ask for a checklist covering working forms, mobile usability, correct links, administrative access and completed metadata. An automated score can support diagnosis, but it does not replace testing the customer journey.

A promise of a guaranteed first-place ranking is not a technical handover criterion. Organic results depend on multiple factors and changing search systems. Assess the activities and checks the supplier actually commits to.

Frequently asked questions

Is the cheapest proposal always risky?

No. A tightly scoped template-based project may be entirely sufficient. The problem is unclear boundaries or a scope that does not meet the actual business requirements.

How many website references should I provide?

A few well-explained examples are more useful than a long list. Identify whether you are referring to structure, tone, navigation or how services are presented.

Read our guide to choosing a web design agency for the wider evaluation. To discuss a proposal with Nightstar, share your brief through the contact page.