Software, built
by the people
you talk to.

The public site, built to be edited by your team afterwards. Structure, copy, design and the build itself.

Tools your staff or customers log into. Accounts, permissions, data and the screens that hold it together.

Interface design carried through to real code, including the responsive and accessibility work that usually gets dropped.

A review of what you already run, a practical architecture, and a plan for getting from one to the other.

Reading, extracting and cross-checking documents, with every answer linked back to the page it came from.

Retrieval over your files and systems, scoped by who is allowed to see what.

A test set that catches regressions, and a clear point where a person decides instead of the model.

Private deployment options, cost per task, monitoring, and what happens when the model is wrong.

Where it runs, what it costs, how it scales, and how it comes back after a failure.

Connecting the systems you already pay for, so the same data stops being typed in twice.

Moving off something that no longer fits, without losing history or a week of trading.

Updates, backups, monitoring and a named person to call.

Who it is for, what it has to do, and what it deliberately will not do.

The screens, and the reusable pieces behind them so the tenth screen is as good as the first.

Something clickable in front of real users early, while changing your mind is still free.

Type, colour and tone applied consistently across the product and the site.