Elliot Web Designs
A useful website quote explains the work, responsibilities and ongoing costs. Compare what each proposal delivers against the same brief before comparing the total.
Begin with the job the website has to do
A five-page website could be a straightforward introduction to a local business. It could also include a carefully researched service structure, original copy, a new visual identity and a booking integration. The page count is the same; the work is very different.
Start by describing the commercial problem. Perhaps the existing site attracts enquiries for services you no longer offer. Perhaps customers struggle to understand a specialist product. A useful proposal connects the work to that problem, so you can see why each part is included.
Separate design from content preparation
Design relies on the material it presents. Finished service descriptions, organised photographs and approved brand assets let a project move differently from a brief that starts with a blank page. Copywriting, image selection and restructuring an old site all take time.
Ask who will interview the business, write the first draft and check technical accuracy. If you are supplying the copy, agree the format and deadline. A lower quotation may reasonably assume you are doing more of this work yourself. The important thing is knowing that before you commit.
Ask which templates and journeys are included
A homepage, a service page and a product page solve different design problems. Multiple pages sharing an agreed pattern may take less work than a smaller collection of very different layouts. Ask the designer to distinguish the number of pages from the number of unique page types.
Then look at the journeys: booking, purchasing, requesting a quote or applying for a service. An integration can include account setup, data mapping, error messages and testing as well as its visible button. Agree representative examples so that both sides understand what a completed feature means.
Include the move from your existing website
A redesign has a starting point. Existing URLs, downloadable documents, enquiry routes and useful content need an explicit decision: keep, improve, move or retire. A launch plan should explain how the old and new websites connect.
Ask whether the scope includes an inventory of current pages, a redirect plan, hosting setup and checks after the switch. If you run email on the same domain, make that arrangement known. These details may be less visible than the homepage, but they belong in the project discussion.
Understand the costs after launch
List the services that need renewing: the domain, hosting, software licences and any external platforms. Establish whose account holds each subscription and who is responsible for keeping it current. A managed monthly service should explain what is included and how additional work is requested.
There is also the cost of keeping content useful. Decide who will update projects, check service descriptions and publish articles. A website that your team can manage comfortably may be a better fit than a technically impressive setup that nobody has time to maintain.
Compare proposals using one shared brief
Give each supplier the same core information and compare their responses against it. Check content responsibilities, review stages, ownership, integrations, launch work and support. Ask about exclusions rather than assuming they are included.
If a proposal exceeds your budget, discuss phasing. A strong initial set of service pages and a clear enquiry journey may be more valuable than launching every possible feature at once. Preserve the work that makes the site useful; schedule secondary ideas for a later stage when there is a clear reason to add them.
