A business website should be useful before it is impressive
Good web design connects business goals, customer tasks, content and technology. The result should help a visitor understand the offer, find reliable information and take the next appropriate step without fighting the interface.
What the service covers
Web design can include information structure, page layouts, content presentation, accessibility and maintainability.
Plan around user tasks
The brief should identify who will use the site, what they need to do, which content is required and how success will be evaluated.
Accessibility is a requirement
The approved project standard is WCAG 2.2 AA, including keyboard access, visible focus and content that works without colour or motion alone.
Plan before layouts
Define the website’s purpose and users
The design should follow the decisions visitors need to make. That begins with the business goal, priority audiences, required pages, customer questions and the action each important journey should support.
- Clarify the website’s primary purpose
- Map important users, questions and tasks
- Plan the page hierarchy and navigation
- Agree content responsibilities before the build
Content and structure
Give every important subject a clear home
A website is easier to use and understand when services, supporting information and business facts have a logical structure. Clear page ownership also gives SEO, advertising and social activity somewhere relevant to lead.
- One clear purpose for each main page
- Service hubs connected to useful supporting content
- Consistent business, contact and location information
- Internal links that reflect real reader pathways
Quality requirements
Accessibility, performance and maintenance belong in the brief
Responsive layouts, keyboard access, readable content, visible focus and efficient assets are part of the website—not optional finishing touches. Ownership, hosting, updates and handover should also be agreed before work begins.
- Responsive behaviour across practical screen sizes
- WCAG 2.2 AA accessibility requirements
- Performance budgets for code, fonts and images
- Clear responsibilities for hosting, access and future updates
Design and development
Choose technology around the website requirement
The project may use a content management system such as WordPress or a static build when that better suits the content, maintenance and performance needs. Domain registration, web hosting, licences, analytics, forms, booking tools, e-commerce functions and other integrations are discussed explicitly; they are not assumed to be included in every web design package.
- Front-end behaviour and content-management needs
- Forms, analytics, booking or social-media integrations
- Hosting, domain and third-party service responsibilities
- Security, maintenance and update arrangements
User experience
Design clear journeys without hiding the detail
User-interface and user-experience decisions should support real tasks: comparing services, checking credibility, reading guidance, finding contact details or making an enquiry. Responsive design, readable type, useful headings, visible focus, descriptive links and restrained interaction improve access for people using different devices and input methods.
- Logical navigation and page hierarchy
- Content-led layouts and clear calls to action
- Keyboard, focus, contrast and reduced-motion considerations
- Testing across representative screen sizes and browsers
Handover and control
Know what you own and how the site is maintained
Concern about being locked out of a website is reasonable. The proposal should identify who owns the domain, hosting account, content and commissioned assets; which software licences continue; who can update the site; and what happens at handover. If website maintenance is required after launch, its scope and response arrangements are agreed separately.
Before commissioning a website
Clear scope and ownership decisions reduce expensive surprises later.
What should be agreed before web design starts?
Agree the website goal, audiences, required pages, content responsibilities, functionality, accessibility requirements, approvals, hosting and the measures used to assess the finished work.
Who supplies the website content?
That depends on the project. The responsibility for research, writing, images, approvals and later updates should be stated clearly in the scope.
Will the website work on mobile devices?
Responsive behaviour should be part of the design and testing requirements. Important content and actions need to remain usable across supported screen sizes.
Who owns the website when it is complete?
Ownership of the domain, hosting account, content, design work, code licences and third-party services should be confirmed in writing before the project begins.
How much does a small-business website cost?
Cost depends on the page structure, content, design system, integrations, e-commerce or custom functionality, migration needs and handover. A proposal follows discovery rather than applying one figure to every website.
Can you work with Wix, Squarespace or WordPress?
The platform should follow the requirement and existing constraints. WordPress and other content management systems may suit some projects, while a static website may suit others. The recommended approach is explained before the build.
How long does it take to design and build a website?
Timing depends on the number of templates and pages, content readiness, integrations, approvals and migration work. The schedule is agreed after those dependencies are known.
Can I update the website myself?
That depends on the chosen technology and agreed editing model. Handover should explain what can be changed safely, who maintains the underlying system and what support is available.
Experience and accountability
Guidance from Pete Hogg
Pete Hogg is the author of the Red Kite SEO guides and an SEO consultant based in Sheffield. He explains the work in plain language, keeps the scope visible and links each service to its supporting guidance.
Read Pete Hogg’s author profile →A practical starting point