What we design and build

Four kinds of project, each designed and engineered in the same studio. Each one has its own page with what is included, who it suits and examples.

Web applications and SaaS

Customer-facing products and SaaS platforms, from the sign-in screen to billing and the admin side, on a stack your next engineer will already know.

Product and interface design. User flows, wireframes and a working component library, designed against real content rather than placeholder text.
Front end. React and Next.js with server rendering, so pages load fast, work without a spinner and can be indexed by search engines.
Back end and data. Node.js APIs and PostgreSQL schemas designed around the questions your business asks of its data, with migrations checked into the repository.
Accounts, roles and billing. Sign-in, teams and permissions, subscription billing and the admin screens your staff need to support customers.

One React Native codebase for both app stores, with native work where the platform asks for it: watch apps, Live Activities and the lock screen.

App design. Navigation, key screens and states designed for thumbs and small screens, including empty, offline and error states.
iPhone and Android. One React Native and Expo codebase, with native modules where the platform requires them.
Lock screen and watch. Live Activities, the Dynamic Island, widgets and Apple Watch companions when they serve the product.
Back end and sync. APIs, push notifications, offline storage and sync, built so the app still works on a weak connection.

The spreadsheet that runs the business, turned into software the whole team can use, with exports that match how the books are already kept.

Process mapping. A walk through how the work really happens today, including the exceptions nobody wrote down.
Data model. A database designed around your records, so reports and exports come straight out of it.
Imports and integrations. Reading from the spreadsheets, PDFs and services you already use, with duplicates caught before they are saved.
Screens for each role. Simple views for the people who enter data and fuller views for the people who manage it.

Recent work: MD Motors

Moving an ageing system onto a maintained stack without stopping the business that depends on it, one piece at a time.

System review. A written assessment of the current system: what it does, where the risk is and what to move first.
Migration plan. An order of work that moves the riskiest or most expensive parts first and keeps every step reversible.
Data migration. Moving records to a modern database with checks that every row arrived intact.
Side-by-side running. Old and new versions running together, with traffic moved across one piece at a time.

The same people stay on it from the first conversation to the release after launch.

01
Understand
The business, the people who will use the software, and what has been tried before.
02
Plan
A written scope: what gets built first, what it costs, and what is left out on purpose.
03
Design and build
Design and engineering run together. Working software reaches a preview link every week or two.
04
Launch and look after
Code, accounts and documentation are yours. We stay on to maintain what we built.

A few lines about the project and when it needs to ship is enough to start.