Skip to content

Design that ships products, not just pixels

Beautiful is easy. Beautiful and usable and buildable is the job.

We design the whole experience: research, flows, UI, and brand, on a system that keeps everything consistent and a spec developers can build exactly.

Design that ships products, not just pixels.
  • Researchled
  • Systemone
  • Handoffdev-ready
the batten · one curve, fair throughoutbuildable
01

Beautiful

A distinct brand and visual identity

02

Usable

Research-led flows and validated prototypes

03

Buildable

Developer-ready specs, tokens, and measurements

One batten, 3 points. Miss any one of them and the curve is not fair — and the third is the one everybody forgets.

Research-led

Every flow

One system

Web + mobile

Dev-ready

Handoff

AA

Accessibility

Usable and buildable

Product Design & UX

Every decision is grounded in how people actually use the product and tested before build, so we solve the right problem while it's still cheap to change.

Research-led, not decoration

We shape flows around how people actually use the product, then test them before build.

Systems, not one-off screens

Design systems, tokens, and specs keep the product consistent as it grows.

Built to be built

Developer-ready handoff means what you approve is what ships.

What you get at handoff

Good design survives the build. Here's what your engineers receive.

The flow is tested before it's builtResearch and prototypes settle the argument while changing it is still cheap.
Engineers can build itSpecs, states, and edge cases are all in the handoff, so the build doesn't turn into a second design phase.
A system, not a pile of screensComponents and rules that stay consistent as the product grows past the screens we drew.
Decisions have a reasonChoices trace back to research, so design reviews are about evidence instead of taste.
Accessible by constructionContrast, focus order, and target sizes are decided in the design, long before any audit.
It scales past the engagementYour team keeps designing in the same language after we stop.

Where this lands hardest

The four situations this practice is asked for most often, and what it is actually doing in each.

SaaS product interfacesDense, task-driven screens where scanability and consistency matter more than expression.
Teams outgrowing their first designA design system for a product that has been growing screen by screen without one.
Marketing and landing surfacesPages where the design is the product, built to be measured against conversion.
Brand and identity workA visual language that holds together across product, marketing, and the assets around them.

What it connects to

It works inside the stack you already run. These are the connections this practice is built against most often.

Your engineering stackComponents specified against the framework your team actually builds in.
Existing design systemWe extend what you have where it's working, instead of replacing it for the sake of a fresh start.
Prototyping and testing toolsFlows tested with real users before the build, in whatever your team already runs.
AnalyticsThe analytics plan is part of the design, so the questions you'll ask later have answers.
Content and brand assetsType, color, and voice carried through every screen, never reinvented per page.
Handoff and documentationSpecs, states, and tokens delivered in the tooling your developers open every day.

Design engineers can build

Research-led flows before pixels, design systems instead of one-off screens, and a developer-ready handoff, all tested with real users before a line of code.

  • Research-led flows before pixels
  • Design systems and specs, not just screens
  • Prototyped and tested with real users
  • Developer-ready handoff

How an engagement runs

Four stages, in order, and exactly what happens in each.

Weeks 1-2ResearchReal users, real tasks, and what the existing product already tells us, all before anything is drawn.
Weeks 3-4Flows and prototypesThe structure settled and tested at low fidelity, where changing your mind costs a day.
Weeks 5-7System and screensComponents, tokens, and states built as a system, with the screens as its first application.
Week 8HandoffSpecs, states, and edge cases documented against your stack, and your team walked through them.

Chalk erases. Timber doesn't.

Solve it while it's still cheap to change

Every decision is grounded in how people actually use the product and tested before build. Then it ships as a developer-ready spec, so what you approve is what gets made.

6 things that come off the floor

Design that stops at a Figma file becomes an argument at build time, so everything here is something an engineer can implement directly. The system, tokens, and specs travel together, and accessibility is on the list, not left for a later audit, because retrofitting it costs several times more.

  • A full UI design system across web and mobile
  • Research-led flows and validated prototypes
  • A distinct brand and visual identity
  • Developer-ready specs, tokens, and measurements
  • Landing pages and campaign creative
  • Accessibility built in to WCAG AA

Why bring this to us

Six commitments, each one something we actually do differently.

We research before we drawBeautiful is easy. Beautiful, usable, and buildable is the job, and only research gets you the middle one.
We deliver systems, not screensOne-off screens diverge the moment your team adds the next one.
We design what can be builtEvery screen is checked against the stack it will be built in, by people who have built in it.
We test with real usersA prototype in front of five real users settles arguments that a design review will run for weeks.
We hand over properlyStates, edge cases, and tokens, so the build never becomes a second round of design decisions.
We leave you able to continueThe system and its rules are yours, documented well enough to extend without us.

What people ask before they start

Do you only design screens, or the whole experience?

The whole experience: research, flows, UI, design systems, brand, and handoff. We shape how the product works, not just how it looks.

Will developers be able to build what you design?

Yes. Everything ships as a developer-ready spec with tokens, states, and measurements, and we work closely with your engineers so the design survives the build intact.

Can you work within our existing brand?

Absolutely. We design within your brand and tighten the visual system where it helps. We can also build a new identity from scratch.

How is accessibility handled?

Contrast, focus states, and touch targets are designed to WCAG AA from the first screen, never retrofitted at the end.

Have a project?

Let's talk

Running a large platform, shaping a first MVP, or getting a product ready for a funding round? Tell us where you are. We'll shape the process around it, and stay with you after launch.