Design systems
Design systems in Augsburg: consistent design, faster development
For product teams who want to spend less time on alignment and one-off fixes and build new pages faster and more consistently.
I work from Königsbrunn near Augsburg: on site in and around Augsburg, otherwise remotely across Germany.
Free intro call- Tokens
- Components
- Figma
- Documentation
What's included
Scalable, token-based component libraries for consistent products. I build design systems that empower teams to work faster and more consistently.
- Design token architecture
- Component library (Figma)
- Documentation & guidelines
- Theming & dark mode
- Design-dev handoff
From audit to a usable design system in 4 to 10 weeks
- Week 1
Step 1: Interface audit
I collect what already exists: colours, typefaces, buttons, forms. This shows where things have drifted apart and what can be reused.
Typical outputs
- Interface inventory
- List of inconsistencies
- Priorities
- Weeks 2 to 3
Step 2: Design tokens
I define the foundations as tokens: colours, typography, spacing, radii. With variants for theming and dark mode.
Typical outputs
- Token architecture
- Colour and type scales
- Dark mode
- Weeks 3 to 7
Step 3: Components
On top of the tokens I build a component library in Figma, with variants and states, accessible following WCAG.
Typical outputs
- Component library
- Variants and states
- Example pages
- Weeks 7 to 9
Step 4: Documentation
I describe when to use which component and what to watch out for, short and clear for design and development.
Typical outputs
- Guidelines
- Usage examples
- Dos and don’ts
- Weeks 9 to 10
Step 5: Handover and rollout
I introduce the system to your team, align the handover to development and agree how it will be maintained and extended.
Typical outputs
- Team introduction
- Design-dev handoff
- Maintenance process
A design system is more than a set of components.
Token architecture
Colours, typefaces and spacing as central values that look the same everywhere.
Component library
Reusable building blocks in Figma with all variants and states.
Theming and dark mode
Several themes or brands on one shared foundation.
Accessibility
Contrast, focus and sizing following WCAG, built into the components.
Documentation
Short, clear guidelines your team will actually read.
Design-dev handoff
The same names and values in Figma and code, so nothing gets lost.
Packages
Two typical routes. We agree scope and price in the intro call, tailored to your project.
Foundations
For small teams who want to start with a solid base of tokens and core components.
- Interface audit
- Design tokens for colour, type and spacing
- Core components such as buttons and forms
- Short documentation
- Handover of the Figma library
Complete
For teams with several products or brands who need a scalable system.
- Everything in Foundations
- Full component library
- Theming and dark mode
- Detailed guidelines
- Design-dev handoff with your developers
- Team rollout and maintenance process
Why work with me
Built from real practice
I design components the way I build them myself, with tokens, states and accessibility from the start.
One point of contact
You talk to me from the first idea to launch, with no hand-offs and nothing lost in translation.
Honest advice
I tell you openly what is worth doing and what is not, even if that means a smaller job for me.
On site and remote
In and around Augsburg we can meet in person; elsewhere in Germany we work easily over video.
Tools
- Figma
- VS Code
- Webflow
- Claude
Frequently asked questions
All FAQsIs a design system worth it for small teams?
Yes, in a lean form. Even a few tokens and core components save discussion and stop every page from looking different. The system then grows with your product.
How much does a design system cost?
It depends on the scope: the number of components, themes and products. After the free intro call you get a concrete quote.
Do you work with our development team?
Yes, that is essential. I align names and values with the developers, so Figma and code speak the same language.
Can we build on our existing Figma library?
Yes. I tidy up existing files, make them consistent and add what is missing, rather than starting from zero.
Who maintains the system afterwards?
Your team. Together we agree who approves changes and how new components are added. If you like, I can keep supporting the maintenance.
Related services
Interested in design systems?
In a free, no-obligation intro call we work out what you need and how I can help.
Free intro call