Skip to main content
jb
Services & Engagements

Your design system should make shipping faster.

Right now, it's probably making it slower. Creating rework, accessibility risk, and friction between design and engineering. Let's fix that.

Does any of this feel familiar?

The patterns I see over and over

If two or three of these describe your team, you're probably leaving a lot of sprint velocity on the table.

Designers and engineers keep solving the same problems every single sprint.

No shared source of truth, so features get restarted mid-build.

Accessibility debt is quietly stacking up into real legal risk.

A system exists, but no one uses it consistently.

Documentation doesn't match reality, so teams fork components instead of extending them.

Quick gut-check

Which engagement fits?

A 60-second quiz that points you at the right starting point — without the calendar invite.

sixty seconds

Which engagement actually fits?

Five questions, no signup, no email. You’ll get a single, specific recommendation — and an honest one if I’m not the right call.

0 of 5 answered
Q1 Where does today’s pain actually live?

Pick the one that stings most.

Q2 What does your team work from today?
Q3 How is a new component born?
Q4 In 90 days, what does “win” look like?
Q5 Where’s your team’s energy going?
How I can help

Three ways to work together

Every engagement starts with an audit. I won't build anything until I know what's actually broken.

Start here

Design System Audit

A structured look at what's working, what's broken, and where the friction really lives. Before anything gets built or rebuilt, we need a map.

  • Component & token inventory
  • Accessibility & consistency review
  • Prioritized action plan you can run
Start with an audit
Build the foundation

Component Library Starter

A solid foundation your team can grow with. Designed for longevity, not a quick patch you'll rip out in six months.

  • Accessible, composable core components
  • Design tokens & theming architecture
  • Docs your team will actually read
Learn about the starter
Fix the handoff

Design-to-Code Workflow

The friction between design and engineering isn't a people problem, it's a process problem. I fix the process.

  • Figma ↔ code parity that holds up
  • Handoff rituals that don't waste sprints
  • Shared language across design & eng
Learn about the workflow

I only take on a limited number of engagements at a time so every client gets genuine attention.

How engagements run

A simple, honest process

No mystery, no theater, no month-long discovery deck.

  1. 01

    Intro call

    30 minutes. You tell me what's hurting, I ask the questions no one else has asked. We figure out if we're a fit. No pressure either way.

  2. 02

    Audit & scope

    I dig into your system, your code, and the way your team actually works. You get a clear map of what's broken and a scoped plan to fix it.

  3. 03

    Build & embed

    Whether it's a component library, workflow fixes, or both, I work alongside your team, not in a silo. Everything I build, your team owns.

  4. 04

    Handoff & support

    Your team runs with it. I stay close for questions, edge cases, and the occasional "wait, how should we do this?" moment.

The problem, in pictures

What an audit actually finds

The kind of small, quiet inconsistencies that compound into rework. Toggle “show issues” to see what a quick pass surfaces.

take a look

What an audit actually finds.

Pick a screen. Toggle “show issues”. The dashed boxes are the inconsistencies a quick pass would flag — the kind that quietly cost your team sprint velocity.

your-app.com/pricing

Starter

$19/mo

  • Up to 3 projects
  • Email support
  • Basic analytics

Business

$99/mo

  • Unlimited projects
  • Dedicated CSM
  • SSO & audit logs

Want this on your screens? An audit produces a 30-page version with priorities and a fix plan. See the audit →

See it in motion

What a design token actually does

Drag a slider, change the whole card. That’s the leverage a real system gives a team — every component pulls from the same vocabulary.

drag the knobs

A design token, made visible.

One source of truth, many components in sync. Move a slider — the card on the right reacts. That’s a design system in miniature.

14px
1.00×
Primary color
Density

No JavaScript per component. Just CSS variables.

preview
New release v2.4 · today

Button & Card components updated

Radius and spacing tokens now drive both. Change one number, two components agree.

tokens a11y v2
1 token
7 elements
0 overrides

Try setting radius to 0 for a brutalist feel, or 28+ for friendly & rounded.

Not sure where to start?

Take the free Design System Scorecard. Ten minutes. No fluff. You'll know exactly where your system stands.

Get the scorecard

Let's fix your system.

Book a 30-minute intro call. We'll talk about what's breaking down and whether an engagement would actually help.