Web development
Websites and web applications that perform on the devices and connections your users actually have.
The challenge
Sites built for a fast connection and a new laptop, tested on a fast connection and a new laptop.
On a mid-range Android phone over a slow network — which is most of the audience here — they are unusable.
How we approach it
Agree a performance budget
A number, in the contract, checked in the build.
Accessible from the first commit
Not an audit at the end.
Content model before layout
Structure the content, then design to it.
Test on real devices
Mid-range hardware, throttled connection.
The same four phases, whatever we are building.
- 012–3 weeks
Discovery
We map your current process, users and constraints, then define scope in writing.
- 022–4 weeks
Design
Interface and data design, reviewed with the people who will use the system daily.
- 036 weeks+
Build
Delivery in two-week increments, each one testable, with progress visible throughout.
- 04Ongoing
Launch & support
Deployment, training and documentation, then optional support at a level you choose.
What you get
- Tokens and components, documented.
- The site or application, in your repository.
- Typed structure your team can edit against.
- A measured report against the agreed budget.
- A statement listing what conforms and what does not.
What changes
Usable on real devices
Tested where your audience actually is.
Accessible by construction
Not retrofitted after a complaint.
Budget enforced
Performance is checked, not hoped for.
Often looked at together.
Mobile development
Native and cross-platform apps built for shared, low-end devices and patchy signal.
Software development
Custom web and backend systems, built to be maintained by someone else.
Digital transformation
Process mapping, sequencing and adoption support, measured on use rather than delivery.
About this work specifically.
General questions about scope, ownership and timelines are answered on the resources page.
Yes. Where editing is frequent we connect a content system; where it is occasional we keep content in the codebase, which is cheaper and safer. We will recommend based on who edits and how often, not on what is fashionable.
Tell us what you need built.
We reply within two working days with honest scope and next steps — including when we are not the right fit.