Website design scope
Price not set
Website Design & Development
Website design and development built around how customers choose.
Bring distinctive design, clear service content and reliable functionality together in a business website designed for discovery, confidence and enquiry.
Pricing
Pricing
Scope
Pages, content, functionality and handover are specified in the brief. Domains, ecommerce, custom applications and ongoing care are itemised where needed.
Still to confirm: setup fee, tax, contract length, quantity. These are not treated as zero or free.
Deliverables
Useful work, clearly defined.
- Site structure and customer-journey plan.
- Page and content specification for the agreed build.
- Responsive visual design and reusable components.
- Development of the selected forms and integrations.
- Launch checks and editing handover.
Structure and content
Map the pages needed to explain the business and its services. Give each page a distinct purpose and identify the source facts, examples and approvals that its writing requires.
Design and responsive layout
Build a consistent visual system around readable content and usable navigation. Review important journeys at desktop and mobile sizes rather than approve the site from a single homepage screenshot.
Enquiry and application scope
Define the contact actions, forms and integrations the project actually includes. A visible button is not proof that its destination works, and an accepted form is not a confirmed appointment.
Launch and handover planning
Check existing routes, media rights, business identity and the intended editing workflow. Document the launch checks and responsibilities for ongoing care instead of leaving them as assumptions.
How the service helps
Design the page system as well as the pages
Your website needs to explain the business, answer the questions that matter and make the next step easy to complete. We connect positioning, page structure, copy and development around those tasks. That gives the visual design a clear purpose and the build a specification that extends beyond the homepage. Existing routes, editing needs and integrations are considered early, while testing follows the customer journey through to the receiving process. The result is a site built to be useful to visitors and manageable for the business.
A service catalogue benefits from reusable layouts, but each page still needs distinct information. Define the shared components and the facts they display, then create page-specific explanations and relevant links. A structured approach makes updates more consistent while allowing each service to answer its own buying questions.
Your website needs to explain the business, answer the questions that matter and make the next step easy to complete.
A fictional scenario showing how the work could be approached.
Website Design & Development: an example in practice
Observation
A fictional local business has a striking homepage but no clear description of its main service.
Proposed correction
Reorganise the page around the service, suitability, practical questions and an understandable enquiry route.
Verification
Test the journey from first visit to accepted enquiry on desktop and mobile, with unsupported features kept out.
Process
From the first review to the next priority.
Define the website’s job
Review your offer, audience, existing site and the actions customers need to complete.
Plan content and design
Map the pages, develop the message and establish a coherent visual direction.
Build the working site
Develop the agreed layouts and functions with representative content.
Test and prepare launch
Check navigation, mobile use, enquiry handling and existing URL continuity before release.
Your timeline
A website you understand before it goes live.
See the structure, review the design and use a working preview before launch.
An example journey for a separately scoped website project. Dates, pages, functions and review rounds are agreed in the proposal. The Maps package has its own one-page allowance.
Direction
Define the brief
Agree the audience, purpose and useful customer actions.
- What you receive
- A written brief and scope.
- What you provide
- Business facts, existing assets and the problem to solve.
- Checkpoint
- Scope, responsibilities and commercial terms agreed.
Structure & design
Shape the experience
Plan the pages and make the visual direction tangible.
- What you receive
- A proposed structure and design direction.
- What you provide
- Review priorities and consolidate feedback.
- Checkpoint
- Agree the direction before the build.
Development
Build the working site
Turn the agreed direction into a usable preview.
- What you receive
- Working pages and the functions in the agreed scope.
- What you provide
- Approved copy, images and access where required.
- Checkpoint
- Check the main customer journey in the preview.
Review
Review the details
Check content, mobile layouts and enquiry routes.
- What you receive
- Agreed revisions and a record of launch checks.
- What you provide
- Consolidated feedback within the agreed review allowance.
- Checkpoint
- Approval to launch and any outstanding items recorded.
Release
Launch & hand over
Publish the approved work and explain how it is looked after.
- What you receive
- The live site, agreed access and handover information.
- What you provide
- Confirm the receiving contacts and ongoing responsibilities.
- Checkpoint
- Care and future changes follow their agreed scope.
Suitability
Who this work is for.
Who it suits
A useful starting point
A business ready to supply factual content and agree what its website must actually do.
Prepare the brief
What to bring
Business objectives, existing routes, approved service facts, brand assets and the required contact or integration workflows.
Project scope
Make the responsibilities clear
Pages, content, functionality and handover are specified in the brief. Domains, ecommerce, custom applications and ongoing care are itemised where needed.
FAQ
Questions, answered plainly.
Should we choose a template or a bespoke design?
A template can suit a defined brochure site with familiar customer tasks. Bespoke design is useful when the proposition, content or functionality needs a different structure. Choose the approach after defining the website’s job.
Can you redesign a website without losing its existing URLs?
Existing routes should be inventoried before a redesign. Where a change is necessary, the migration plan should identify the new destination and redirect behaviour.
Will we be able to update the website?
The editing workflow and handover are part of the project brief. We identify which content you need to manage and how changes should be made without disrupting shared layouts.
Your next step
Build a website that gives customers a clearer reason to choose you.
Review your offer, audience, existing site and the actions customers need to complete. We will help define the relevant work, responsibilities and next decision.