Most website projects fail commercially rather than technically. The site is delivered, it looks acceptable, and then nobody in the business can change a price without going back to the agency. Two years later it is abandoned because updating it costs more than replacing it. We treat editability and hand-over as requirements of the build rather than as an afterthought, and the content model is agreed before any interface is designed.
Technology is chosen to fit the problem and the people who will maintain it. A site that changes weekly and is edited by a non-technical team is usually best served by WordPress with a properly constrained editing experience. An application with authenticated users, complex state and integration requirements is built in Next.js and TypeScript. We will tell you which category your project falls into and why, including when the answer means a smaller engagement than you expected.
Performance and accessibility are measured, not asserted. Core Web Vitals are tested against the production build on a throttled connection, and the site is checked against WCAG 2.2 Level AA. Both results are reported to you whether or not they are flattering.
What is included
Discovery and content model
Who the site is for, what it must achieve commercially, and the structure of the content before any visual design begins.
Design and build
Responsive interface design and front-end implementation, reviewed by you in increments rather than revealed at the end.
Content management
An editing experience constrained to what should actually be editable, so the site cannot be broken by ordinary use.
Performance and accessibility testing
Core Web Vitals measured against the production build, and WCAG 2.2 AA conformance checked and reported.
Search foundations
Semantic markup, metadata, structured data, XML sitemap, and redirects mapped from any existing site so rankings survive the move.
Analytics and deployment
Hosting configured in your own accounts, TLS, analytics with a privacy-compliant configuration, and a documented deployment process.
How it is delivered
- Scope is fixed in writing before work begins, including what is out of scope. Change requests are quoted rather than absorbed and invoiced later.
- Work is delivered in reviewable increments against a shared staging environment, so you see progress while there is still time to redirect it.
- Every dependency, credential and account is created in your name. Nothing is held in ours, and nothing stops working if you engage someone else.
What you receive
- Production website deployed to hosting you own
- Source code in a repository under your organisation
- Content editing guide written for the people who will use it
- Performance and accessibility test results
- Redirect map from any previous site
- Thirty days of defect correction after go-live at no charge
What is not included
Stated plainly, because unstated exclusions are where disputes begin.
- Copywriting and photography, unless separately scoped
- Ongoing content updates after hand-over, which are covered by a support agreement if wanted
- Paid advertising management, which sits under digital marketing
- Third-party licence and subscription costs, which are billed to you directly by the vendor
Common questions
Who owns the site when it is finished?
You do. Intellectual property in everything we create transfers to you on final payment, and it is written into the agreement. Accounts and repositories are created in your name from the beginning, so there is no transfer to negotiate.
Can we edit it ourselves afterwards?
Yes, and this is treated as a build requirement rather than a nice-to-have. You receive an editing guide written for the people who will actually use it, and a walkthrough at hand-over.
How long does a website take?
A small marketing site is typically four to six weeks from agreed scope, and a web application is longer and depends entirely on integration requirements. We give a date range in the statement of work and tell you promptly if anything threatens it.
Related solutions
Application development
Mobile and line-of-business applications delivered through a documented lifecycle, with testing that runs before release rather than after.
Artificial intelligence
Assistants and automation grounded in your own material, built so that answers can be checked rather than merely believed.