What we build,and how we run it

Eight disciplines, one team. Each of these is work we do on our own products first — which is why the pages below talk about what happens after launch, not just what gets delivered.

These are the studio’s services. How the studio works explains the team and the method behind them, and our own products are where we prove it.

Custom software built by the people who will keep it running.
Most software fails after the handover, not during the build. We write the code, deploy it, watch it under real traffic and stay on support — so the decisions we make during the build are the ones we will have to live with.
Software Development in detail
- Discovery and technical scoping before any estimate is given
- Full-stack build: interface, API, database, integrations
- Automated tests around the parts that would hurt most if they broke
- Deployment, monitoring and an on-call route to a person
Multi-tenant products with billing, roles and onboarding that actually work.
We run four SaaS products of our own, so we have already paid for the mistakes: tenant isolation that leaks, plan gates bolted on late, billing that cannot handle a downgrade. A SaaS build with us starts from the parts that are painful to retrofit.
SaaS Development in detail
- Multi-tenant data model with isolation enforced at the database, not the UI
- Plans, entitlements and feature gates designed before the first screen
- Subscription billing, invoices and the awkward cases — downgrades, refunds, failed payments
- Onboarding that gets a new customer to value without a call
Fast, accessible sites that stay fast after you add content to them.
A website is not finished when it launches; it is finished when someone can update it without breaking it and without making it slower. We build sites that hold their performance and their carbon budget after a year of edits.
Web Application Development in detail
- Design and build, or build from the design you already have
- A CMS your team can use, with content models that prevent broken pages
- Performance and carbon budgets set at the start and checked per release
- Accessibility to WCAG AA, tested rather than assumed
Apps for people working on their feet, on the phones they already own.
Most business mobile work is not a consumer app — it is a counter, a delivery round or a stock take, done one-handed on a mid-range Android with bad signal. That is the device and the situation we design for.
Mobile App Development in detail
- Interface designed for one hand, gloves, glare and interruption
- Offline-first behaviour where the work does not stop when the signal does
- Device features that earn their place: camera, QR scanning, printing, location
- Store submission, or installable web apps where a store adds nothing
Research, interface design and a system the build can be held to.
This is where the studio started, and we still do it — with one change. We do not hand over files. Design here is written down as a system the engineering can be checked against, and we are the ones who build it.
UI/UX Design in detail
- User research: interviews, observation, and testing with people who do the job
- Information architecture and flows before any visual design
- High-fidelity interface design and interactive prototypes
- A design system — tokens, components, states — not a folder of screens
One team owning discovery, design, build and what happens after launch.
The expensive failures are not technical. They are a product built exactly to a specification that was wrong. Product engineering is the whole arc under one team — deciding what to build, building it, and staying accountable for whether it worked.
Product Engineering in detail
- Discovery: the problem, the people, and whether software is even the answer
- Roadmap tied to outcomes you can check, not a feature list
- Design and engineering in one team, on one cadence
- Instrumentation, so we can tell whether the thing worked
AI where it removes work — not a chatbot bolted to the corner of the screen.
We build AI into products when it takes a job off someone. Reading a document so a person does not have to type it. Spotting the invoice that does not match. Adapting an interface to how one person actually works. If it cannot be evaluated, we will not ship it.
AI Development in detail
- A hard look at whether AI is the right tool for the task at all
- Document understanding, extraction and classification in real workflows
- Assistants scoped to one job, with the boundaries written down
- Personalisation that adapts to a role or a habit, not a marketing gimmick
Infrastructure you can afford, understand and recover from.
Cloud bills and cloud outages come from the same place: nobody owning the infrastructure. We set up deployment, monitoring and backups so that a bad day is boring, and so you can see what you are paying for.
Cloud & DevOps in detail
- Deployment pipelines — every release the same way, every time
- Environments that match: development, preview, production
- Monitoring and alerting that reaches a person who can act
- Backups, and a restore that has actually been tested

Available for new projects

Let’s build aproduct thatlasts.

Whether it’s a first product or an established platform, we bring the research, the design and the engineering.

Start a project Book a discovery call