10 checks before you invest in a website.
A guide for business owners who want a clear, usable website connected to what their customers need. No technical background or signup required.
Work through the questions below. Use them for your current website or your conversation with a future supplier.
Choose the job your website must do.
Write one sentence: who it helps, what you offer and what the visitor should do next.
Try it: Ask someone outside your business to read the first screen. Can they explain all three without your help?
Make the next step obvious.
Choose a primary action such as an enquiry, a booking or a purchase. Name it clearly.
Try it: Follow that action from the homepage on your phone. Make sure the destination works and explains what happens next.
Show evidence, not just adjectives.
Use genuine project examples, clear service descriptions and reviews you have permission to publish.
Try it: Remove unsupported results and generic claims. A real example with an honest explanation is more useful than a promise.
Keep the mobile journey usable.
Check readable text, comfortable controls and a layout that does not require sideways scrolling.
Try it: Use a real phone to read a service page, open the menu and complete the main journey. Check that fixed controls do not cover it.
Ask for only the details you need.
Keep the enquiry form short. Explain why any less obvious information is needed.
Try it: Test required fields, validation, errors and the success message. Confirm a real authorised test request reaches the responsible person.
Connect the enquiry to an owner.
Decide who replies, where enquiries are stored and how an unanswered request is noticed.
Try it: Trace a test enquiry from the form to the inbox or CRM. A button click is not proof that the enquiry arrived.
Agree the scope before the build.
List pages, languages, content, integrations, revisions and acceptance criteria in the proposal.
Try it: Ask what is included and excluded. If you want a proof of concept, agree its purpose and scope before anyone builds it.
Know what happens after launch.
Clarify domain ownership, hosting, access, maintenance, backups and ongoing costs.
Try it: Ask who can restore the website and how you receive your accounts and files. Put responsibilities in writing.
Make the content easy to find and understand.
Give important services their own clear pages, useful titles and readable content. Keep contact and business details accurate.
Try it: Check page titles, links and search visibility basics. Technical foundations help discovery, but do not guarantee rankings or sales.
Measure the outcome that matters.
Choose a business outcome such as a real enquiry or a paid project. Keep clicks, bookings and revenue distinct.
Try it: Agree which evidence will show progress and what you will review after launch. Respect visitor privacy and recording preferences.
Keep going with four practical emails.
The checklist is available without signing up. If you wish, receive four emails about the checklist, a practical improvement, a real project and how collaboration works. The series starts only after you confirm.
How would a project start?
Tell us what you want to improve. We discuss the need and, if we agree, define a focused proof of concept. The proposal sets out pages, content, revisions, payment, launch and maintenance. We do not build an unsolicited website or assume your approval.