Website Design
Websites planned, built and maintained as business infrastructure rather than as a one-off design exercise.
A website is judged on whether it works.
Not on how it looked in a presentation. It is judged on whether it loads on a phone in a lift, whether someone can complete its forms from a keyboard, and whether the organisation can still change its own content two years later.
Work is scoped against written acceptance criteria agreed before design starts, so “finished” is a checklist rather than an opinion.
Book a consultation.
A consultation is a scoped conversation, not a sales call. Bring the problem rather than a specification; the specification is what the engagement produces.
What we build, and what each is for.
Professional website
A defined set of pages presenting what an organisation does, for organisations that need to be findable and credible.
Multilingual site
The same site in more than one language, with a structure that keeps the language versions genuinely equivalent as content changes.
Membership platform
Public pages plus gated areas for signed-in members, with tiers and the access rules that go with them.
Client portal
An authenticated workspace where clients follow their own projects, approve work and collect files.
E-commerce
Product catalogue, checkout and the operational work behind it: fulfilment, tax, refunds and reconciliation.
Website care
The ongoing work that keeps any of the above correct, patched, backed up and monitored after launch.
What you can hold us to.
These are checked before launch, by both sides, against the agreed criteria. They are commitments about the build rather than claims about results.
Responsive behaviour
Every page is checked at phone, tablet and desktop widths before launch, not only at the width it was designed on.
Keyboard access
Every interactive element is reachable and operable from the keyboard alone, with a visible focus indicator.
Readable contrast
Text and interface boundaries are measured against WCAG AA rather than judged by eye.
Tested forms
Every form is submitted and received end to end on the live site before it is handed over.
Clear content ownership
A written record of which account, service and asset belongs to whom, so nothing is trapped with an agency.
Analytics and backup
Analytics verified as recording, and a backup taken and restored once before launch rather than assumed to work.
Seven stages, each ending in something you can read.
Discovery and scope
What the organisation needs the website to do, who it must serve, and what is explicitly out of scope. Ends with a written scope both sides accept.
Information architecture
The pages, how they relate, and what each one is for. Sitemap and content inventory agreed before any visual design begins.
Design direction
Typographic and colour direction, applied to real page structures rather than to decorative mock-ups, and reviewed on narrow screens first.
Build and integration
Front-end build, content management, forms, analytics and any third-party integration, on a staging environment you can see at any time.
Content, accessibility and QA
Content loaded and proofed, keyboard and contrast checks run, forms tested end to end, and the site checked on real devices.
Launch and handover
Domain and DNS, redirects, analytics verification, a rehearsed backup, and written handover of every account and asset involved.
Care and measurement
Ongoing updates, monitoring and reporting against the measures agreed at the start. Optional, and priced separately.
Six ways to buy website work.
Each package is scoped individually and quoted in writing. No prices are published here, because a figure that has not been scoped against your requirements is not a price.
Website Diagnostic
For an existing site that is underperforming
A structured review of an existing website covering structure, content, performance, accessibility and analytics. Delivered as a written report with a prioritised list of what to fix and what to leave alone.
Discuss this package →Professional Website
For a small organisation that needs a credible presence
A focused site of a defined page count: structure, design, build, content loading and launch. The right starting point for most organisations.
Discuss this package →Business Website Plus
For an organisation with content to manage and integrate
A larger site with a content management system, multiple content types, form handling, analytics and integration with existing business systems.
Discuss this package →Membership Website
For an organisation whose audience logs in
Everything in Business Website Plus, with member accounts, gated content, subscription or tier logic, and the privacy controls that membership implies.
Discuss this package →Client Portal
For an organisation that runs projects for clients
An authenticated workspace for clients: projects, approvals, files, sessions and billing, with role-based permissions and an audit trail.
Discuss this package →Website Care
For any site that has already launched
An ongoing arrangement covering updates, security patching, backups, monitoring and a monthly allowance of content changes.
Discuss this package →What you get handed over.
This practice does not publish client names, project references or performance figures — not because the work is confidential, but because naming an employer, a director or a client without separate authorisation is not something this practice does.
What stands in place of a portfolio is the handover pack. Every engagement ends with the same set of artefacts, and they are yours:
- The agreed sitemap and page-by-page content inventory
- Written acceptance criteria, with the results of each check
- The accessibility and contrast report the build was tested against
- A record of every account, service and asset, and who owns it
- A backup taken and restored once, with the restore recorded
- A short handover document for whoever maintains the site next
Is this the right practice for the work?
This practice is a good fit where the website is business infrastructure: it has to keep working, be maintained, and be owned by the organisation rather than the supplier.
It is a poor fit for work that is primarily a visual campaign, for projects that need a launch in a few days, or where the decision-maker and the person who has to maintain the site are not in the same conversation. Saying so early is cheaper for both sides.
Tell us about the work.
If it is not a fit, you will be told so, and where possible pointed at someone better suited to it.
Start with a conversation.
A consultation is a scoped conversation about what you need, not a sales call. You will leave it knowing whether this is the right practice for the work.