You have the technology. I design.
Some companies have their developers in-house. Others have a system that stays as it is for good reason. Then what is needed is not new technology but design that can be built within it. Concept, UX and design, prepared so your team can work with it.
What arrives at your end
A concept that answers questions
Site structure, user journeys, what goes where and why. That is settled before the first screen is designed. Otherwise you end up discussing colours later when the real issue is the structure.
Screens for all widths
Desktop, tablet, phone. And all the states that occur in everyday use: empty, loaded, filled in, faulty. Not just the pretty case.
A design system instead of single images
Colours, typefaces, spacing and components with their variants, in XD or Figma. Your team rebuilds building blocks, not pixels.
A handover you can read
Dimensions, tokens, behaviour on hover and focus, animations in words and numbers. Whoever implements the design should not have to guess.
Accessibility from the start
Contrast, focus order, target sizes and text alternatives are in the design, not in an audit afterwards. Since 2025 that has been mandatory for many.
I stay reachable
Questions come up while building, always. I answer them, look at interim states and say where it is not right yet. That is part of it, not on top.
How it went at BBSoft
BBSoft has been developing software for civil engineering for decades. There the website is not a business card but a sales channel, networked with internal processes and systems. And the developers are in-house.
So it went like this: design, copy and SEO came from outside, the technical implementation stayed in-house. We were on site in Donaueschingen and worked out the concept with the team. The rebranding became a relaunch, the relaunch a brand world. What I delivered, BBSoft could build in their own environment, without anyone from outside having to touch their systems.
Who this suits
In-house teams
You have developers but nobody who designs interfaces. The system is often already fixed: TYPO3, Drupal, Shopware, an intranet, an in-house development. The design has to fit in.
Agencies
You need design and UX added for a project without hiring anyone. I work in the background or at the table with you, whichever suits you.
Software companies
It is not about a website but about the product itself: dashboards, forms, admin interfaces. There the design decides whether people like working with it.
How the delivery works
Getting to know each other and the frame
What can your system do, what can it not? Grid, components, breakpoints, style guide. We clarify that first, ideally with someone from development present.
Concept and wireframes
Structure and user journeys as sketches. Here things still get moved and cut, which is cheap. Later it is not.
Design and design system
Screens in rounds, with feedback from your developers. In parallel the design system grows so that everything fits together in the end.
Handover and support
Specification, access to the design file, HTML or Markdown. After that I am there for questions and look at the implementation before it goes live.
When something unforeseen comes up
Sometimes the system will not give you something. A component, an interface, an import that was in no plan. For that I have Benjamin at my side: Benjamin Trenkle has been developing the Joomla! core since Joomla! 1.0, helped build the multilingual features, was release lead of Joomla! 4.1 and sits on the Security Strike Team. When something jams somewhere, he often knows the people behind it.
Programming for special cases
The piece your team cannot build or does not want to build right now. Clearly delimited, documented, handed over so you can maintain it yourselves afterwards.
Advice before it gets expensive
A second opinion on architecture, security or performance. A conversation at the right time often saves weeks.
Only when needed
Benjamin is not part of every project. He joins when he is needed, and you know beforehand what it costs.
Frequently asked questions about delivery
In which tool do we get the design?
In Adobe XD or Figma, with access for your team. Or directly as HTML from which the specifications can be read: dimensions, spacing, colour and type values. Markdown is possible too, if your developers would rather read than click.
Do you build the site yourselves too?
Not in this model, that is the point: your developers implement, I deliver. If you do need someone to build, there are the other paths for that: WordPress, Joomla! or hand-built HTML.
Do you work to our specifications?
Yes. Style guide, component library, fixed colours, a given grid: those are not restrictions but the frame within which the design has to work. For TU Munich I worked within the university's corporate design, for BBSoft within the systems the website is networked with.
How detailed is the handover?
So that nobody has to guess. Every screen in all widths, every state, plus a specification with dimensions, spacing, behaviour on hover and focus and a short description of the animations. And I stay reachable if questions come up while building.
What if our team cannot implement something?
Then Benjamin joins in. He programs what your system will not give you, or advises before a decision gets expensive. You know beforehand what it costs.
Matching projects
Rebranding & websiteBBSoftNew logo, new claim, slimmed-down website: how an established civil engineering software company got a brand world without losing its …To the project →
PlatformIFG trainingOver 50 websites became one training platform: how design, course catalogue and booking came together without …To the project →
In corporate designTU MunichBilingual WordPress website for the digitalisation of TU Munich (TUM): corporate design, blog, ideas portal – in …To the project →
You have a system and need design for it?
Write to me about what you work with and what is to be created. I will tell you honestly whether I am the right person for it, and whether Benjamin should join.