Foundations Sprint: tokens and core components
Primitive and semantic tokens, about 15 core components in Figma and React, and Storybook docs your team actually trusts. One source of truth across Figma variables and code.
See the 8-week sprint →Nuremberg · DACH & EU · Design Engineering
Design systems and interfaces that your business can scale, govern, and ship.
I combine systems thinking with craft: roadmaps and adoption for design systems, rigorous UI and UX, and design engineering in the stack (React, TypeScript, Tailwind), so design intent survives handoff.
- 50+
- happy clients across product & scale
- 16+
- years in UX, UI, systems, and code
- 250M+
- users of products I helped design
Nord Security, Aurora. Dozens of squads.
Flyeralarm. About 90% fewer reclamations.
1st place, Into Design Systems AI Hackathon 2026.
01 / The Inconsistency Tax
Is your experience inconsistent, and your team paying the tax?
- Your UI looks different in every squad: no shared tokens, components, or documentation. Every screen is a one-off.
- Design files and production drift apart. Engineers rebuild the same patterns or ship inconsistent variants.
- Onboarding new designers or devs is slow because "how we build UI here" lives in chat threads and tribal knowledge.
- You know you need a design system, but prioritization, governance, and adoption feel overwhelming next to feature work.
It doesn't have to be this way. Let me help you solve these problems.
02 / Diagnostic
Design System Health Check
Six questions. You get a score and a read on where consistency is leaking, with no email required.
1. Your design tokens (colors, spacing, type) are…
2. How many versions of a "button" exist across your product(s)?
3. Does production match what's in Figma?
4. Can a new engineer build a screen without asking around?
5. Who owns the design system?
6. How fast are you scaling design and engineering right now?
03 / Capabilities
From design system foundations to pixels and production code
I lead and consult on design systems at scale, and I stay close to the craft: UX and UI, prototypes for validation, and design engineering when your team needs someone who speaks both Figma and the repo.
This is a fit if
- You are scaling a product org and need one source of truth for UI: tokens, components, and patterns
- Design and engineering disagree on what "done" looks like, and you want a tighter design-dev workflow
- You have legacy UI drift and need a system plus a rollout plan
- You want a senior partner who can own UX and UI and contribute production front-end when it matters
Speaking both Figma and the repo
Figma components and React props wired up with Code Connect. Your engineers open Dev Mode and see the real TypeScript contract, not a guessed CSS snippet.
See how handoff works →
AI-ready systems and MCP
Give coding agents a contract they can actually read: clean token schemas, component guidelines, and lint checks in CI so agents use your system instead of inventing a new button.
Read how I work with agents →
40-Point Design System Audit
We count your button variants, token drift, and parity gaps across six lenses. You get a scored baseline, a cost-of-inaction estimate, and a 30/60/90-day roadmap.
See the audit →04 / The First Paid Step
The Design System Audit
In one to two weeks you'll know where you stand, what the inconsistency is costing you, and the prioritized plan to fix it.
- Findings ranked by severity, with evidence
- Cost-of-inconsistency framing
- A prioritized, costed roadmap
- A live readout with design and engineering
Fixed price. The fee is credited toward a follow-on build.
Get a free consultation →
05 / Selected Work
Work I've shipped and handed off
Product, platform, and design-system work I've already delivered. One engagement cut reclamations by about 90% and unlocked significant revenue.
-
Aurora
Design systems and design engineering at Nord Security. Dozens of teams, millions of users, on a production system that has to survive handoff every week.
-
Flyeralarm
Design system, branding, and front-end on two software platforms. Automatic print-data error correction cut the reclamation rate by about 90%.
-
Swap Wizards
Figma plugin that smart-matches and swaps components when names don't align. 1st place, Into Design Systems AI Hackathon 2026.
-
Skore and Collection
E-learning UI that had been stuck in the early 2000s, plus a broader set of product and platform interfaces.
-
Nexus UI
A fictional Series B system in this repo: tokens, components, live docs, and governance pages.
View the docs site →
06 / Objections
Honest answers to the usual objections
Can one person really handle our design system?
You get a principal with 16+ years and enterprise-scale experience, plus agentic workflows that compress the mechanical work so one senior partner delivers like a small team. For larger rollouts I bring in trusted specialists. You always work with me, not an account manager.
We were going to hire for this.
Hiring a true design engineer takes months. The role falls through most hiring filters. I get you moving now, de-risk the direction, and can hand off to your future hire, or stay on a light retainer.
Isn't AI making this cheaper?
AI speeds up the production work, which is why I can deliver fixed-price and fast. The value is judgment, systems strategy, and adoption. Those are the parts AI can't own.
Why not a bigger agency?
Agencies rarely bridge to production code or own adoption. I live in the seam between Figma and the repo, and I optimize for a system your team actually uses.
How do we start without a big commitment?
Take the Health Check, or get a free consultation. The first paid step is a fixed-price audit, credited toward any build.
Do you work remotely across DACH and the EU?
Yes. Remote-first, based in Nuremberg. German (native) and English (fluent).
07 / Ready to scale?
Let's talk systems, product, or both
Share where you are today: roadmap, team shape, and whether you need strategy, hands-on system build, UX and UI, or design engineering. I'll reply with honest next steps.