Getting a Website for Your Local Business: What to Expect
Choose the main tasks: read a menu, request a quote, make a booking or buy a product.
- Write a brief based on customer tasks
- Agree the content and technical scope
- Review the prototype with real content and real devices
- Separate launch acceptance from ongoing maintenance
- A useful brief for a small service business
- Questions about this guide
- Further reading
- Related help
- Terms in this area
- Read next
- Tell us about your own situation.
- Services
- Resources
- Company
- Get in touch
Choose the main tasks: read a menu, request a quote, make a booking or buy a product. A useful business website begins with the jobs customers need to complete: understand your offer, check whether it fits and contact or buy without confusion. A beautiful homepage is only one part of that work. Content, domain ownership, mobile behaviour, languages and maintenance all affect whether the finished site remains useful. This guide explains the project decisions a small business should make before commissioning a website, what to review during design and what to receive at handover. It is a planning guide, not a universal price list or a promise about delivery time. The right scope depends on your content, integrations and the people who will maintain it. Write a brief based on customer tasks List your main services or products and the questions people ask before contacting you. Decide what each page should explain and the action it should support. A trades business may need a clear service explanation and an enquiry form; a retailer may need stock, delivery and checkout. These are different systems, not just different colours on the same homepage. Collect existing logos, licensed images, confirmed business details and the names of people who approve changes. Mark missing information instead of asking the designer to invent it. Define the languages customers genuinely need and who reviews each version. For international residents on the Costa Blanca, a multilingual booking or contact task may be more useful than translating a large news archive nobody maintains. Agree the content and technical scope Specify the page list, forms, search, appointment or shop functions, and external services. Distinguish content writing from uploading text you supply. A quote should say whether translations, image licensing, data migration and revisions are included, and what happens when the scope changes. The number of pages alone is a poor measure of complexity. Agree who owns the domain registration, hosting account, email service and administrator access. Keep essential accounts under the business’s control rather than dependent on a contractor’s personal login. Clarify which assets and licences transfer, which require renewal and whether you can export the content. A website that works only while an unspecified third-party subscription remains active creates avoidable uncertainty. Review the prototype with real content and real devices Review actual headings, photos and form
What should I prepare before our first conversation?
A short description of your business, the people you would like to reach and what you want visitors to do is plenty. Your branding, photos and examples of sites you like are helpful, but please get in touch even if some material is still missing.
Do I need bookings or a shop on my website?
Start with what your customers actually need to do. For some businesses a clear way to get in touch is plenty, while others need bookings or purchases. It helps to talk this through early, because it affects the content, the testing and the ongoing work.
Who will update the site after it goes live?
It is best to agree this before launch. Decide who changes prices, opening hours, photos and translated text, and who looks after maintenance. Ask what is included in the proposed arrangement and how any extra work would be agreed, so you know where you stand.
Should I approve only the desktop design?
It is better to look at both. Please check the content and your most important customer task on a real phone too, because a desktop mock-up cannot show mobile menus, typing, form checks or how long translations read. Your approval should cover both layouts and the full journey.