Key Takeaways
- Compare website quotes against the same customer journey, not page counts alone.
- Ask who supplies service copy, proof, photography and the information needed to qualify an enquiry.
- Include form delivery, error handling and staff follow-up in the scope.
- Separate launch readiness from ongoing marketing. A working website still needs a plan for attracting suitable visitors.
- Agree what will be measured without accepting promises of a fixed number of leads.
A useful web design quote explains how the finished website will help the right customer make a suitable enquiry. It should also explain what your team must provide and what happens after the customer presses send.
If you are comparing web design in Reading, you may receive one proposal built around pages, another around design concepts and a third around a platform. Those details matter, but they are easier to judge once the commercial job is clear.
You are buying a website that somebody must find, understand and use. Work backwards from that person's task and the gaps in a quote become much easier to spot.
Write Down the Enquiry You Want
Start with a plain description of a suitable customer. Include the service they need, the area you can cover and any practical conditions that affect whether you can help.
For an illustrative Reading installation business, a useful enquiry might include the type of property, approximate location, work required and intended timing. That is a planning example, not a statement about a real client. Your business may need much less information at first contact.
The GTS Reading WordPress build is a documented example of web design in Reading organised around service and industry information, fleet details and a quote journey. The project page describes the delivery, without claiming measured gains in enquiries.
Then list the enquiries you cannot use. Recruitment approaches, requests outside your service area and jobs below your minimum workable scope may require a different route. The aim is to help people find the right answer without making a suitable prospect complete an application form.
Give this brief to every supplier. If one company is quoting for a simple online brochure and another is designing a qualified-enquiry journey, their fees will not be directly comparable.
Map the Journey Before Counting Pages
Sketch the decisions a visitor must make: does this company offer the right service, can it handle my situation, can I trust it and what should I do next?
Map each decision to the content or function that helps. A service page explains the offer. A relevant project example supports the claim. A clear enquiry route helps the person act. Several decisions may sit on one page; one decision may need more than one page.
Our custom website design service starts with that relationship between the business and the user. The layout should support the journey you have agreed.
Ask the supplier to walk through a realistic visit on a phone. Avoid a demonstration that begins on the homepage if customers will usually land on an individual service page. The starting point changes what context the page must provide.
Compare the Responsibilities Hidden Inside the Quote
“Content included” is too vague to price or accept confidently. Does it mean copying your existing text, editing it, interviewing the team or writing new service explanations from scratch?
Check who verifies factual claims, secures customer permissions and supplies photographs. A designer cannot safely invent a case study because the project needs an extra page.
| Part of the journey | Ask the supplier | Ask your team |
|---|---|---|
| Find the service | Which search and navigation needs are covered? | Which services matter commercially? |
| Understand the offer | Who writes and approves the scope? | What do prospects misunderstand? |
| Check credibility | What proof will the page use? | Which examples can we publish? |
| Make an enquiry | What information and actions are included? | Who receives and answers it? |
| Review performance | What events and reports will be checked? | Who confirms lead quality? |
Use the same table for each quote. Mark an item as included, optional, supplied by you or unanswered. A blank box is a question to resolve before accepting the proposal.
The website redesign proposal checklist helps check those responsibilities against the rest of the proposed work.
Ask What “SEO Included” Means at Launch
Search preparation can include crawlable pages, sensible titles, clear internal links, a sitemap and redirects where old URLs change. Ongoing research, content development and reputation-building are different pieces of work.
Google's SEO Starter Guide is a useful reference for baseline site organisation and search accessibility. It does not turn a newly launched website into a guaranteed source of enquiries.
Ask for the launch checks by name. If the proposal includes migration, request a list of important existing URLs and their intended destinations. If it includes new copy, agree the services and audience each page will cover.
Keep the ongoing marketing plan visible too. A business that expects enquiries from paid campaigns needs a suitable destination and a budget decision beyond the design fee. Our guide to Google Ads landing pages and service pages helps decide whether a separate campaign page is justified.
Follow the Form Submission All the Way Through
A form is not finished because it has a button and a success message. The quote should cover what happens to valid submissions, invalid submissions and delivery failures.
Agree the destination inbox or CRM, required fields, confirmation wording and who owns the connection. Use controlled test details and a clear test reference so nobody mistakes a test for a customer enquiry.
Check the experience when a visitor makes a mistake. W3C's form-validation guidance explains that errors should be communicated accessibly and that browser-side checks do not replace server-side validation. Ask the supplier to demonstrate the agreed behaviour, including keyboard use and a small mobile screen.
You also need an operational fallback. If an integration fails, where is the submission retained, how is the responsible person alerted and what can the business recover? Those answers depend on the implementation, so have them written down rather than assuming every form stores a copy.
Include the Human Follow-Up
The website can ask sensible questions and route an enquiry, but somebody must respond. Agree the owner, the intended response window and what happens when that person is away.
Avoid promising a response time on the page that the team cannot consistently meet. An automated acknowledgement should explain what happens next without pretending a person has already reviewed the request.
Consider what staff need to see in the notification. The service requested, contact details and the customer's own description may be enough. A CRM integration may help with assignment or follow-up, but it should solve a real operational problem rather than appear as an impressive extra.
If an existing enquiry process works well, preserve it until the replacement has been tested. The supplier should explain how the handover avoids losing messages during launch.
Define Measurement Without Inventing a Forecast
Ask the agency how you will distinguish page visits, enquiry attempts, received enquiries and suitable opportunities. Each measure answers a different question.
A click on a phone link does not prove that a conversation happened. A booking-button click does not prove that an appointment was accepted. A recorded form event may need checking against the actual submission system.
A scope for analytics and reporting should identify the events, relevant consent handling, test process and known gaps. It should also say whether CRM matching is included or left to your team.
Do not judge a quote by a supplier's unsupported promise of a particular conversion rate. Ask what starting evidence exists and which assumptions a forecast uses. Where the site has little traffic, initial measurement may be about learning which enquiries arrive rather than running a meaningful experiment.
Check the Cost of Running the Journey
List the recurring items required to keep the agreed website working: hosting, domain renewal, maintenance, paid extensions, booking tools, CRM features or email delivery where applicable.
For each item, confirm who owns the account, who pays and what happens if the agreement ends. Ask which features depend on a particular subscription and whether a simpler option would meet the same requirement.
Our guide to how much a website costs in the UK gives broader cost context; use the supplier's written scope to identify what your quote covers.
Include staff time. If publishing a project requires a developer every time, your team needs to know. If the CMS is intended for self-editing, request a demonstration of the actual task, using the content fields you will receive.
This is a total-responsibility comparison rather than a search for the cheapest platform. A lower initial quote may fit perfectly when your team already has the skills and assets to supply the remaining work. It may be unsuitable when those responsibilities have been overlooked.
Agree Acceptance Before the Final Design Review
Write a short set of acceptance tasks into the project: a customer finds the right service, checks the relevant proof, submits an enquiry and receives the agreed confirmation. Your staff receive the correct information and can update the important content.
Also agree how defects are handled and which issues would prevent launch. A broken form is different from a small spacing preference. Both can be recorded without treating them as equal risks.
Our website acceptance-testing checklist covers the later sign-off in more detail. At quotation stage, make sure the supplier has allowed time for that work.
Ask how post-launch issues are reported, what the support period covers and when additional charges begin. Keep the wording specific enough for both sides to recognise whether a request belongs to the original project.
Use a Short Comparison Meeting
Send your preferred supplier the unanswered items from the table. Ask them to explain what is included, what is optional and what depends on your team.
If you still need to assess who will deliver the work, use these questions to ask before hiring a website designer alongside the quote comparison.
Discuss one realistic customer journey rather than every possible future feature. If the first release needs to be smaller, preserve the complete enquiry path and defer lower-priority additions deliberately.
You can share your website brief with us if you want help defining that first release. Bring the service you want to sell, the questions customers ask and the practical details of how your team handles an enquiry. Those are useful starting materials even if you have not chosen a platform or design style yet.
Frequently Asked Questions
How should I compare web design quotes in Reading?
Give suppliers the same business brief and compare the complete customer journey. Check content, design, development, enquiry handling, measurement, training and support responsibilities. A shared page count alone does not mean the proposals include the same work.
Should a web designer promise a number of leads?
Be cautious about a promise without a reliable baseline and clear assumptions. Enquiry volume also depends on demand, traffic quality, the offer and follow-up. Agree the website tasks and measurement first, then review the evidence after launch.
What should an enquiry form quote include?
It should specify fields, validation, accessible messages, delivery destination, storage or recovery arrangements where applicable, and controlled testing. Confirm who maintains any connected email or CRM service and how failures will be noticed.
Does SEO included mean ongoing SEO is covered?
Not necessarily. It may refer only to launch fundamentals such as titles, internal links and redirects. Ask for the exact deliverables and separate any ongoing research, content, technical support or reporting work.
Can I start with a smaller website and expand later?
Yes, provided the first version still supports the important customer journey. Agree what is deferred, what the team can edit and which later additions may require extra development or subscriptions. Avoid launching an incomplete enquiry process merely to keep the page count down.
