Services
Four shapes of work. Most engagements combine two — a site and the platform it runs on, or a product and the team that keeps it alive.
Websites
A site is an argument about what matters. We build that argument before we build anything else.
We start with architecture and content, because a site whose structure nobody can explain is a site nobody can maintain. By the time anything is designed, the navigation, the page types, and the words are settled and written down.
The build uses a component system your team can pick up. We set a performance budget and hold it in continuous integration, so the site that launches is the site that stays fast after six months of edits.
What is included
- Information architecture and content model
- Copy editing, not copywriting
- Visual design across every breakpoint
- Component library with documented usage
- CMS your editors will not need training for
- Redirect map, analytics, and a launch checklist
What changes the price
- Number of page types, not number of pages
- How much of the content already exists
- Whether we write it or you do
- How many languages you need
- Whether a migration is involved
What we will tell you
If your problem is a content problem, a site is the wrong answer and we will say so in the first call. Roughly one in five briefs we review does not need a rebuild.
Product software
Internal tools and customer portals, built around the slow part of the job nobody wants to do.
The demos are never the hard part. Hard part is the approval that needs two people, the record that has to survive an audit, the exception that happens twice a year and stops everything. We design for those first, because they are what the software is actually for.
You get a working URL in week three and a Friday demo every week after. Nothing is presented finished-and-perfect at the end, because that is the only way to find out you built the wrong thing.
What is included
- Discovery on the real workflow
- Data model and permission design
- Web application, built to be extended
- Audit trail on everything that changes money
- Import and export from day one
- Documentation and a handover walkthrough
How we scope it
Two weeks of discovery, then a fixed scope for the first release. Later releases are quoted separately against a backlog you own, so you decide what is next rather than discovering it at renewal.
Fixed scope for release one. Change after that is a decision you make, not a negotiation.
What we need from you
One person who knows the workflow well enough to say "that is wrong" on a Friday, and four hours a week of their time. Without that, we will guess, and you will pay for the guessing.
Platform
The unglamorous work of getting off whatever is holding you back — done carefully, with a way back.
Most of this starts with a sentence like "we cannot get a report our finance team trusts" or "the site has not been deployable in three years". We map the current system, agree what is worth keeping, and migrate the rest with a rollback available at every step.
You get runbooks for whoever is on call, and a written record of every decision, because the next person should not have to reconstruct your reasoning from a git history.
Common jobs
- CMS replacements and content migration
- Hosting, CI, and monitoring from scratch
- Consolidating APIs across acquisitions
- Data reconciliation between systems
- Performance work on an ageing codebase
How we work
We take over systems we did not build, which means reading other people's decisions before changing them. The first week is spent understanding, not editing.
What you keep
Everything. Source, infrastructure, accounts, and documentation. We work in your cloud tenancy, not a rented black box that only we can open.
Care
A standing team for the year after launch, when the real work finally shows up.
A named group of people who already know your code, with a standing weekly slot rather than a ticket queue. Small changes ship in days, and nothing waits for the next quarterly review to discuss a one-line fix.
Once a quarter you get a written review of what we changed, what it cost, and what we think will break next. If the answer is that you no longer need us, that is in the document.
What is included
- Security patches and dependency updates, applied weekly
- A named team, reachable without a ticket
- Quarterly cost, performance, and risk review
- Monitoring and on-call rotation set up and staffed
- Planned roadmap work, roughly one sprint a month
The catch
Care only applies to work we built or have taken over. We will not inherit an unfamiliar codebase into a retainer — that is what Platform is for, and it comes first.
Which one is yours?
Describe the problem in your own words. We will tell you which shape fits, and roughly what it costs, before you commit to anything.
Start a project