Which one should we start with?

If you're not sure, a Trust Audit. It shows what to fix first, and which service fits after it. If you already know what you need, start there.

Yes. Each one builds on the one before, so you can start with one and add the next when you need it.

Do you work with our engineers?

Yes. Your engineers get designs they can build from, every state included, or production code in your repo that they review.

Do you build the back end?

No. We ship the product layer: the interface and the logic behind it. The back end stays with your engineers, or a partner engineer we bring in.

What happens after the call?

If there's a fit, a written proposal with a fixed scope and price. If not, we'll tell you, and why.

SERVICES

Four ways to work with us.

Each one goes further into your product, from finding where trust breaks to the systems that keep it. Start with the one that fits.

Trust AuditFind where trust breaksA review of your most important flow: every issue ranked by impact, and a fix plan your team can ship.For teams not sure where to start Product DesignDesign that earns trustResearch, interaction and AI interface design, specified so your engineers can build it as designed.For teams with their own engineers Design & BuildCode that ships itWe design it and build it: production front-end code in your repo, reviewed by your team.For teams that need it built SystemsSystems that keep itThe systems your team builds with, from the design system to AI instructions and checks. New work stays consistent without us.For teams that keep building

SOUND FAMILIAR?

Where trust leaks.

Each one points to the service that fixes it.

01People hesitate before they act on your numbers.They double-check in a spreadsheet, or ask support if it's right.Trust Audit
02Your AI feature demos well, but nobody relies on it.Because nobody can see why it said what it said.Product Design
03What ships isn't quite what was designed.The reasoning got lost between design and code.Design & Build
04The product feels less like one product with every release.Each team ships its own version of the same thing.Systems

TRUST AUDIT

Find where trust breaks.

We go through your most important flow the way a careful user would, and find every place it loses their trust.

For teams not sure where to start

01Every issue, ranked.Each one ranked by how much trust it costs and how hard it is to fix, so you know what to do first.
02A fix plan your team can ship.What to change and in what order, written so your designers and engineers can act on it.
03The flow, redesigned.The fixes designed into the flow itself, ready to build.
04A walkthrough with your team.We take you through every finding and answer your questions, so nothing is left to interpretation.

PRODUCT DESIGN

Design that earns trust.

We design the parts of your product people rely on most, with AI and data products as our specialism, and specify them so your engineers build them as designed.

For teams with their own engineers

01Flows people trust.From research to interaction design, built around what people need to see before they act.
02AI people can check.Answers that show where they came from, and that people can approve, edit or undo.
03Every state designed.From empty and loading to errors and missing permissions, so nothing is left to guess.
04A spec your engineers build from.In Figma or in writing, with the reason behind each decision, and a review of the first build.

DESIGN & BUILD

Code that ships it.

We design the product layer and build it ourselves, in your repo, so what was designed is exactly what ships.

For teams that need it built

01Production code in your repo.Front-end and interface logic, written to your standards and reviewed by your team.
02Progress you can see.Small changes, often, each with a preview link and a before and after.
03Tested with real users.The flow that matters most, checked with the people who will rely on it before it's done.
04A decision log.Every design and code decision written down with its reason, so your team can carry it on.

SYSTEMS

Systems that keep it.

The foundations your team and its AI tools build with, so every new feature looks and works like one product, without us.

For teams that keep building

01Foundations in code.Tokens and the components you repeat most, from tables to forms, each with its states and usage rules.
02Ready for your AI tools.Instructions and examples your AI coding tools follow, so what they generate fits the system the first time.
03Checks in code review.Off-system work is flagged before it merges.
04A team that runs it.Docs next to the code, a playbook and a handover session. It's done when your team ships on-system without us.

QUESTIONS

Before you book.

Which one should we start with?
If you're not sure, a Trust Audit. It shows what to fix first, and which service fits after it. If you already know what you need, start there.
Can we combine them?
Yes. Each one builds on the one before, so you can start with one and add the next when you need it.
Do you work with our engineers?
Yes. Your engineers get designs they can build from, every state included, or production code in your repo that they review.
Do you build the back end?
No. We ship the product layer: the interface and the logic behind it. The back end stays with your engineers, or a partner engineer we bring in.
What happens after the call?
If there's a fit, a written proposal with a fixed scope and price. If not, we'll tell you, and why.