A new website
Start with what the business offers, who the site is for and what visitors need to do. We turn that brief into a page structure, a design direction and a build scope you can review.
Websites for businesses & creators
Website design& development.
Our website development services help businesses and creators explain what they offer and give people a clear way to get in touch or buy. From the first page outline to launch, we work through the content, editing tools and connections your site needs.
- 01Structure & content
- 02Design & build
- 03Tools & integrations
- 04Launch & handoff
Where does your project start?
We can work with what you have.
A website rebuild
If you’re considering a WordPress website redesign or moving from another platform, we start with what already works. That means looking at the pages visitors use, the URLs that bring in traffic and the tools your team needs before deciding what to rebuild.
Focused improvements
You may need to repair a broken WordPress enquiry form, improve a service page or make the website easier for your team to update. We inspect the current setup, agree on the specific work and test the result without assuming the whole site needs rebuilding.
Inside a website project
Follow a website through the build.
A page is one part of a working website. Explore four parts of the build using CMX’s own site as the example, from organizing its pages to agreeing what stays with the business.
CMX01 / Page structure
HOME / 01Introduce the business.
Services, useful work and a clear next step.
SERVICE / 02Website development
Scope, approach and project enquiry.
Explain the work ↗
GUIDE / 03Website ownership
Accounts, access and handoff.
Answer a question ↗
CONTACT / 04Discuss a project
Context for the conversation.
Take the next step ↗
Visitor journey
Find the service → Understand the work → Get in touch
01 / Structure
Give each page a clear job.
The homepage introduces CMX. A service page can then explain the relevant work in more detail, link to useful guidance and give the reader a way to discuss a project.
We plan those relationships before designing the templates. For a rebuild, that also means deciding which existing pages and URLs need to stay.
CMX02 / Reading layout
Website guideOwnership & handoff
AFTER LAUNCHYour website.
Your website.
Your accounts.
Agree who controls the domain, hosting and content before the handoff.
01 / ACCOUNT ACCESSKeep the essentials together.
Record the accounts, renewal responsibilities and access your team will need.
Clear headingUseful contextRelevant next step
02 / Interface
Make the information easy to use.
The title introduces the subject, the paragraph gives useful context and the link leads to the full guide. Type size, reading width and spacing help each part stay distinct.
We design the layouts around real content, then check how the text, navigation and controls behave at different screen sizes. The important next step needs to remain easy to find and use on a phone.
CMX03 / Illustrative enquiry route
VISITORProject enquiry
Contact detailsProject outline
Collect the information needed for a useful reply.
WEBSITECheck & route
Required fieldsSpam controlsDelivery handlingVisitor confirmation
TEAMReceive the context.
Respond to the person.
Respond to the person.
03 / Connections
Plan what happens after the click.
A form needs a destination, confirmation and a way to handle delivery failures. We agree those details alongside any booking tools, payments, email services or CRM connections in the project.
This route illustrates the decisions involved. The exact tools and behaviour depend on the build scope, and the important paths need testing before launch.
CMX04 / Handoff outline
PROJECT DELIVERYYour website handoff
Items and responsibilities to agree.
- 01 Accounts & access
- Domain, hosting, CMS and connected tools
- 02 Website files
- Agreed source files and deployment details
- 03 Editing guide
- Instructions for the people managing content
- 04 Support agreement
- Maintenance scope and renewal responsibilities
Agreed before the buildReady for the people taking over ↗
04 / Handoff
Know what you’re taking over.
Account ownership and the handoff belong in the proposal. Your team needs to know how to edit the site, where its important files are and who will maintain the systems it depends on.
We agree the access, files and documentation included in the project, along with any ongoing support. That gives both teams a clear record of what delivery means.
CMX site example with simplified page and reading layouts. The enquiry route is illustrative and does not submit a form or demonstrate a verified live integration.
Structure · Interface · Connections · Handoff
Agreeing the build
What goes into your website?
The scope depends on your content, the way your team works and the tools the site needs to connect. We agree those details before the build starts.
Pages & templates
Plan the navigation and page structure, then design and build the layouts around your content. Brand and graphic design can be included where the project needs it.
Content editing
Set up an editing workflow for the people who will maintain the content. We work with WordPress, other CMS platforms and custom builds. Hosting, publishing and maintenance are considered alongside the choice of system.
Forms & tools
Connect the agreed enquiry, booking, payment or business tools. E-commerce and custom application work need a defined scope covering their journeys, integrations and ongoing operation.
Search foundations
Useful headings, clear service information and links between related pages are part of the build from the start. When an existing website is being redesigned, we also check which URLs should stay, plan redirects for anything that moves and test indexing and inquiry tracking before launch. For ongoing search and campaign work, see our digital marketing services.
Checks & delivery
Test important pages on mobile and desktop, check navigation and forms, and review accessibility and the routes visitors use to get in touch. Before handoff, agree who owns the domain, accounts, files and documentation, and who will maintain the site.
The editing setup
Choose around the people using it.
We consider who will edit the website, how often the content changes and which tools it relies on. Those details help us choose the platform and plan its ongoing upkeep.
We review the existing setup before recommending a change. The proposal should identify the software, hosting and service costs, along with who manages each account and how the website will be maintained.
From brief to handoff
A build you can review as it develops.
The work moves through agreed review points. Content, feedback and access to existing systems all affect the schedule, so we identify those dependencies at the start.
- 01 / Plan
Define the work.
Review the goals, existing website, content and tools. Agree the pages, important journeys, responsibilities and boundaries of the project.
A brief and scope to review
- 02 / Design
Review real pages.
Develop the page structure and layouts with representative content. Review the direction and key screen sizes before building the remaining templates.
Layouts and content decisions
- 03 / Build
Use the preview.
Build the templates, editing setup and agreed connections. Review the working site and check the journeys visitors and editors will use.
A working website for review
- 04 / Deliver
Prepare the launch.
Resolve the agreed review items, check redirects and indexing, and coordinate the release. Deliver the included access, files and instructions.
Launch and documented handoff
Before we start
Questions about the build.
Can you work with our existing website?
We begin by reviewing the current site and the problem you want to solve. A focused improvement may be enough. If the project needs a rebuild, we identify the content, URLs, accounts and integrations that should carry over before agreeing the replacement.
Can our team edit the website?
We agree what your team needs to update and set up the editing tools around that work. The scope should specify the CMS, access levels and included instructions so you know how day-to-day changes will be handled.
Do you help with content and design?
Page structure and layout are part of planning the website. We agree who will supply, edit and approve the copy and images. Brand and graphic design can also be included where needed. Our design services page explains that work in more detail.
What happens to our existing search traffic?
A rebuild needs a record of the important pages and their URLs. We review what stays, plan redirects where addresses change and check the intended indexing setup before launch. Search results can still change after a rebuild, so the migration and any ongoing SEO work need a clear scope.
Can you include a shop, bookings or other tools?
We discuss the journey and the systems it needs to connect before defining the work. Payments, booking rules, account access and delivery handling all affect the build. Existing services may cover the requirement, while a custom application needs its own agreed scope.
How much will the project cost, and how long will it take?
We need the page scope, content requirements, integrations and current setup to give a useful estimate. Share any budget or deadline early. The proposal should set out the included work, review points, dependencies and ongoing service costs.
Who owns the website after launch?
Account ownership, included files and access should be agreed before the build. We document the handoff and any maintenance arrangement so your team knows what it controls and who handles ongoing work. The website ownership guide covers the questions to ask.
Start a website project
What does your website need to do?
Tell us what you want to build or improve. If you already have a site, send the link and explain what’s getting in the way. Include any timing or budget you have in mind so we can talk through the work.