Websites and web apps built to be changed, not just shipped
Most agency websites are built once, handed over, and then nobody can safely touch them. We build on mainstream stacks your own developers can pick up, with the CMS, the tests and the documentation that make a codebase survive its first year. The point is not the launch — it is every release after it.
Engagement
A marketing site is typically a 4–8 week fixed-scope engagement. Web apps are scoped in two-week sprints once we have agreed what the first release must do.
What you get
Deliverables, not adjectives
This is what lands in your hands at the end. If something is missing from this list, it was not in scope — and we will say so before we start rather than after.
Responsive front end built with Next.js, React and TypeScript — real components, not a page builder export
A CMS your marketing team can actually operate, with roles and an approval workflow
Technical SEO baked in: metadata, structured data, sitemap, canonicals, Core Web Vitals budget
Accessibility to WCAG 2.2 AA, tested with a keyboard and a screen reader, not just a scanner
Automated tests over the critical paths, and a CI pipeline that runs them on every push
A written handover pack: architecture, environment setup, deploy runbook, and a recorded walkthrough
30 days of post-launch fixes included as standard
When to call us
The situations where this is the right conversation
If you recognise one of these, that is probably enough to justify a 30-minute call.
01
Your site is slow and you have no idea why
We profile it properly first — Core Web Vitals, real-user timing, the actual network waterfall — then fix what the data points at. Usually render-blocking third parties and unoptimised images, occasionally the hosting.
02
Nobody can safely change the site
That is a build problem, not a people problem. We restructure the code, remove the mystery, and leave documentation your next developer can use on day one.
03
It looks fine on a laptop and falls apart on a phone
Roughly 70% of traffic is mobile. We design and test at real device widths with real touch targets, not a desktop layout squeezed into a narrow viewport.
04
You need an internal tool, not a public website
Dashboards, admin panels, approval queues, data entry. Same engineering discipline, shipped to the handful of people who use it every day.
How we build it
The tools we would reach for
Not a shopping list. These are what we would actually pick for this kind of work, and we will tell you if a different tool fits your constraints better.
- Next.js
- React
- TypeScript
- Laravel
- Node.js
- PostgreSQL
- Tailwind CSS
- Sanity
- Storybook
- Playwright
Examples
The shape of work this usually turns into
Illustrative scenarios, kept anonymous. Specific case studies with client names and evidenced metrics appear on our work page as clients approve them.
B2B lead generation site
A 40-page marketing site with a custom CMS, gated whitepapers feeding a CRM, and a quote calculator. Rebuilt on Next.js with incremental static regeneration so editors can publish without a deploy.
- Next.js
- Headless CMS
- CRM integration
Internal operations dashboard
Replaced a spreadsheet-and-email workflow with a role-based dashboard for 30 staff: live job status, document upload, approval routing, and an audit trail that finance could actually sign off.
- React
- Laravel
- PostgreSQL
- RBAC
Public sector procurement portal
A supplier portal built to meet WCAG 2.2 AA and full keyboard operation, with digital-signature submission and an audit export. Passed accessibility review first time.
- Accessibility
- WCAG 2.2 AA
- Audit trail
Questions
Web development: what buyers ask
Straight answers, including where the answer is that you probably do not need this.
Yes — that is a requirement, not a bonus. You get a CMS with roles and an approval workflow, plus a recorded handover walkthrough. If your team cannot publish a page without an engineer, we have not finished.
Either. We can build to your existing brand guidelines, work from Figma, or design from scratch. If a design is not buildable as drawn — usually for accessibility or small screens — we tell you before we start, not after.
It is yours. Repository, cloud accounts, domains and third-party services are all in your name from the first commit. There is no licence to buy back later.
We build the technical foundation properly — semantics, metadata, structured data, sitemaps, Core Web Vitals. Ongoing content and link-building is a different job and we will say so rather than sell you one.
Related
Often needed alongside this
Got a web development project in mind?
Send us the problem and the constraint. You will get a written responsewithin one uk business day, uk hours, 9:00-18:00, monday to friday, and an honest view on whether we are the right fit.