Two kinds of web work.
Websites
Public sites for organisations: clear information architecture, fast pages, straightforward editing for your team and good accessibility from the start. We are wary of heavy page builders and will usually suggest a simpler content approach that ages better.
Web applications
Logged-in tools: customer portals, booking and ordering systems, internal dashboards, admin panels for your mobile app. These need careful thinking about roles and permissions, data protection, integrations and what happens when two people edit the same thing.
Our defaults.
- Semantic, standards-based HTML with accessibility checked against WCAG 2.2 AA as a working target.
- Performance budgets agreed early: how heavy a page may be and how quickly it should respond on a mid-range phone.
- Hosting chosen for your needs and budget, documented so that you hold the keys.
- Automated tests around the parts that would hurt most if they broke — payments, sign-in, data export.
- Security basics as standard: updated dependencies, sensible headers, least-privilege access, no secrets in code.
Inheriting an existing site?
Many of our conversations begin with a site somebody else built. We start with a fixed-scope review: what is there, what state it is in, what is risky and what is merely untidy. You receive a written report with priorities, whether or not you then ask us to do the work.