Enterprise software. Thoughtful delivery.
Software Engineering

A website with a clear job to do.

Build websites and web applications that help visitors find the right information, complete a task and take the next step.

What this covers.

Public sites and customer-facing applications: the content model, the editing experience, performance, accessibility and search visibility. The people who will keep the site current are treated as users of it, because a site nobody can update goes stale within a year.

How it runs.

Structure and content model first, then design, then build. Accessibility and performance are constraints during the build rather than a test at the end. The content management side is built so an editor can change wording, imagery and structure without a developer.

Where it fits.

When the site has a job beyond presence: capturing enquiries, publishing to more than one language, or supporting a sales conversation with something a reader will actually use.

What you get, and what it depends on.

A site your team can keep current without a developer, that performs on a phone and works with a keyboard and a screen reader. It depends on somebody owning the content, because a site nobody updates goes stale within a year.

Engagement

How we can work together

The model is chosen to suit the work, not to suit us. We will tell you when a fixed price is the wrong instrument.

01

Site build

Structure, design and build, with the editing experience treated as a feature.

02

Redesign

An existing site restructured and rebuilt, with the content carried across.

03

Continuous improvement

Ongoing changes against a prioritised list rather than a project.

What does this work look like on your side?

Describe the piece of work you are weighing up. We will come back with scope, sequence and who needs to be in the room.