Product Design & Development
Design and engineering for digital products, run by one team: research and scoping, interface design, build, testing, launch, and the work that follows release. Web and mobile, new products or rebuilds of ones you already have.
What we build
MVPs
A first working version scoped to one core flow, built to go in front of real users rather than to demo.
Full product builds
Web and mobile applications, concept through to production release.
Redesigns
A new interface on a product that already works, along with the component library behind it.
Rebuilds
Replacing a codebase that has become slow, fragile, or too expensive to keep changing.
How the engagement runs
1. Discovery
One to two weeks. Stakeholder interviews, a review of what exists today, user research where there are users to talk to, and a written scope listing what's in and what's out.
2. Design
User flows and wireframes, then interface design in Figma, then a clickable prototype of the main journeys, reviewed stage by stage.
3. Build
Two-week iterations, each ending with a working build on a staging URL. Code lands in the repository from the first commit and the ticket board stays open throughout.
4. Testing
Cross-browser and device testing, accessibility checks, performance profiling, and a fix pass before release.
5. Launch and after
Deployment, analytics and error tracking wired up, then a refinement period driven by what real usage shows.
What you get at the end
Design source
Figma files with components and styles intact, not a flattened export.
Code
Your repositories with full commit history, under your organisation's account.
Infrastructure
Environments, deployment pipeline, and the hosting accounts they run on, in your name.
Documentation
Setup and architecture notes written for the next developer, plus a handover session with your team.
Who this is for
Founders building a first version. Teams whose product has outgrown the design it launched with. Companies with engineers but no design capacity, and companies with neither. Most engagements run four to twelve weeks.
Frequently asked
How long does a typical engagement take?
Four to twelve weeks for most of them. You get a real date at the end of discovery, once the scope is written down and agreed by both sides.
What do you build with?
React and Next.js on the web, React Native for mobile, Node or Python on the back end, Postgres for data. We'll use something else if you already run a stack your team maintains.
We already have designs. Can you just build them?
Yes. We review them first for the states that usually go undrawn: empty lists, errors, loading, long content, small screens. Whatever's missing we design as part of the build.
Do you do design without development, or the other way round?
Both. Design-only engagements end with Figma files, a component library, and specs your engineers can build from. Build-only ones start with a review of the designs you have.
Who will actually be doing the work?
The people on your kickoff call. No substitution of juniors after the pitch, and no subcontractors you haven't met.
How often will we hear from you?
A weekly call, a shared Slack channel, and access to the board and the staging builds whenever you want to look.
Who owns the design files and code?
You do, once invoices are settled. Figma files, repositories, documentation, and accounts. We sign work-for-hire terms that say exactly that.