01
Custom software
End-to-end product engineering for teams who need software that earns its place in their operation. We build, ship, and stay.
- ·TypeScript
- ·Go · Python · Rust
- ·Postgres · Redis
- ·Cloud-native
We build custom software, AI applications, internal platforms, lead engines, and mobile products for ambitious teams. Senior engineers and designers, no agencies in the middle, code we sign our names to.
A deliberately small, deliberately senior practice. Every engagement is staffed by people who've shipped more than they've slidedeck'd.
End-to-end product engineering for teams who need software that earns its place in their operation. We build, ship, and stay.
Retrieval pipelines, agentic workflows, and AI-native interfaces that go past the demo. We build evaluation into the codebase.
Internal platforms that the people running the business actually want to open in the morning. Built around real workflows, not vendor dashboards.
From capture to attribution to follow-up — an instrumented pipeline that turns interest into closed business, with the data trail to prove it.
Interfaces with point of view. Performance budgets that survive contact with reality. Design systems engineered to scale across teams.
Native iOS and Android, and the cross-platform builds where it makes sense. Offline-first, built to be reviewed and shipped.
A short selection — not a portfolio. Click through; everything below is live and the work continues.
An AI-native consumer platform built for play. Full-stack engineering and an interface that leans into motion as a primary material.
An intelligent search interface paired with a tuned retrieval layer. Quiet on the surface, instrumented underneath.
A travel companion for trekkers — routes, gear, community, planning — across mobile and web, designed to feel handed-down rather than installed.
A creative AI tool exploring colour, composition, and generative palettes. Built around the working session of a designer, not the demo reel.
Two to four engineers and a designer at most. No layered escalation. The people on Slack are the people writing the code.
The first week is usually a paid discovery. We agree on what we're actually trying to make and what done looks like — before any retainer.
Code is read more than written. We treat it like editorial prose: clear, considered, easy to revisit a year later when we're long gone.
When we ship AI features, we ship the evals, the guardrails, and the boring parts that make them work in production. No demos.
No throw-it-over-the-wall. Design and engineering work in the same file, the same Linear issue, the same review.
We don't disappear at handover. Every engagement includes a stewardship window: deploys watched, on-call respected, knowledge transferred properly.
No middlemen, no farmed-out contractors. The names below are the same names on every commit, every call, every release.
Tell us what you're trying to make, where you are with it, and the shape of the team. We respond in person, usually within a working day.