Technology
How we build, and what we will not do
A public-safe description of our engineering approach. It deliberately stops short of internal architecture — what matters here is the commitments a client can hold us to.
Engineering approach
- Server-rendered pages so critical content is readable without client-side scripting.
- One codebase, content-driven templates and a central registry rather than bespoke code per page.
- Typed interfaces end to end, with checks running in continuous integration on every change.
- Accessibility and performance treated as acceptance criteria, not as a later clean-up pass.
Governance commitments
A person stays accountable.
Systems we build pause for human approval before an action that affects a customer, a record or money.
Results can be explained.
Where a system makes a suggestion, the reason behind it is available to the people who have to stand behind it.
Data stays where it belongs.
We agree the legal basis, the retention period and the deletion path before a system collects anything.
Claims are backed by evidence.
We do not publish an availability, performance or outcome figure we cannot show you the source for.
What we decline to build
- Systems that take a consequential decision about a person with no route to a human review.
- Interfaces that present an automated response as if it came from a named professional.
- Data collection without an agreed legal basis, retention period and deletion path.
- Public claims about performance or outcomes that we cannot evidence.
Have a project in mind?
Tell us the problem and the outcome you need. We reply with an honest read on scope, sequence and whether we are the right team for it.