Create
Website design and development, built to be kept.
Most business websites do not fail because they look wrong. They fail because nobody can update them, nothing is measured, and the pages that would answer a buyer’s actual question were never written. The work below is aimed at that, not at a new coat of paint.
- Capability group
- Create
- What that group is for
- Build what your business needs
- Who it is for
- Businesses whose website is dated, slow to change, or not producing the enquiries the rest of the marketing is paying for.
- Where it stops
- Public-facing websites, revamps, landing pages, UX and web implementation. When the main deliverable is something people log into to do their job, it is a custom software project instead.
Why the rebuild keeps getting postponed
A website degrades gradually. A page gets added outside the design system, a section is edited into a shape it was never built for, a plugin is installed to solve one problem and left running for three years. Eventually the quickest way to change anything is to ask a developer, so nothing changes, and the site slowly stops describing the business.
That is why the first questions here are not visual ones. What does this site have to do — earn trust for a considered purchase, take bookings, support a sales conversation, rank for a specific search? Who has to keep it current, and what will they realistically be able to edit themselves? Those answers decide the structure, and the structure is what decides how long the site stays useful.
Common signals
- Changing a page means booking developer time, so pages stop changing.
- The site is noticeably slow on a phone, where most visitors arrive.
- Enquiries arrive as bare emails with no indication of what the person wants.
- Nobody can say which pages produce contact and which are decoration.
- The pages a buyer would search for do not exist, so paid traffic lands on the homepage.
What we can help with
Few projects need all of this. The scope follows the problem, and we would rather remove a workstream than pad one.
- Website strategy and structure
- What the site is for, what a visitor needs at each stage, and which pages have to exist — settled before layouts. Produces a page inventory and an information architecture, with the question each page is built to answer written down.
- UX and interface design
- Templates and a component set designed as a system rather than page by page, so new pages stay consistent and the site can grow a section at a time instead of needing a full redesign every two years.
- Responsive development
- Implementation that works from a 320-pixel phone upward, with real keyboard support, visible focus, sensible reading order and accessible markup — not a desktop layout squeezed onto a smaller screen.
- Performance
- Images generated at build time in modern formats, minimal JavaScript, and no third-party script added without a reason it has to be there. Speed is decided by build and architecture choices, not recovered afterwards with a plugin.
- Search foundations
- Clean URLs, one canonical per page, honest metadata, a real heading hierarchy and crawlable internal links. This is the groundwork that makes search work possible; the campaign itself is a separate engagement.
- Measurement
- The enquiry path instrumented before launch, so you can see which pages and which campaigns produce contact rather than inferring it from traffic totals months later.
- Ecommerce and landing pages
- Product, category and checkout experiences where the site sells directly, and single-purpose campaign pages built around one offer and one action where it does not.
- Content model and handover
- A structured content system, documentation, and a site your team can edit inside its intended design instead of working around it. The handover is part of the build, not an afterthought.
How a website project usually runs
Five stages. The sequence matters more than the labels: structure is agreed before design, and design is reviewed against real content.
Discovery
What the site has to do, who it is for, what exists today, and what has to survive the rebuild. Ends with an agreed page inventory and structure, not a mood board.
Structure and content model
Templates, sections and fields defined before design, so every piece of content has somewhere to live and the site can be extended later without inventing new page types.
Design
Key templates designed properly, the rest derived from them as a system. Reviewed with your real copy and real constraints, because that is where layouts break.
Build and instrumentation
Implementation, accessibility and performance work, measurement wired in, and automated checks running in the build so quality is verified rather than remembered.
Launch and handover
Redirects, canonicals, analytics and documentation. You get the site, the content model, and a written explanation of how to keep it running.
Where it connects
A site built this way is the foundation the rest of the work stands on. Search and campaigns need a structure worth sending traffic to. Automation needs an enquiry that arrives as structured data rather than a free-text email. Neither is included here — they are separate engagements — but both are considerably cheaper when the site was built expecting them.
If the requirement turns out to be an application people log into rather than a site people read, that is a different project with a different shape, and we would say so before design started.
What to expect from us
- A straight answer on whether a rebuild is the right spend right now, including when it is not.
- Scope, sequence and decision owners written down before design begins.
- Work reviewed against your real content, never against filler standing in for it.
- A site you can maintain, handed over with its content model and documentation.
Related
Work that usually sits alongside this
Thinking about a new site, or a rebuild you keep deferring?
Tell us what the current site is not doing and what you need it to do instead. You will get a realistic view of the scope, the sequence, and what it would take.