Design and frontend — from one generalist, not three.

One person, high task density, AI-supported — the chain without the breaks. UX research, requirements engineering and AI-assisted build in one head: evidence becomes machine-readable requirements the AI builds against — tested behaviour, not a pretty demo.

Three ways to work with me

Three offers for companies

Pick the shape that fits the moment — a fast build, flexible senior capacity, or bringing AI into your team as a lasting capability.

01

Turn an idea into reality — in days

When you have an idea or feature and need to see it real and testable fast.

Research-backed, machine-readable requirements go straight into an AI-built, running prototype — tested with real users, not a slideshow.

  • ✓ A clickable, tested prototype
  • ✓ Days, not months
  • ✓ A decision you can defend
02

Bridge a resource gap — without a permanent hire

When your team needs senior design & frontend power for a few months.

I plug in as one expert covering research, requirements and build — high task density, AI-supported. Scaled up when you need it, down when you don't.

  • ✓ Senior capacity on demand
  • ✓ No headcount commitment
  • ✓ One expert, not three contracts
03

Establish AI in your company — as a capability

When you want AI-assisted design & build as a repeatable process, not a one-off.

I set up the method — Agentic Design System, machine-readable requirements, a CI that checks behaviour and accessibility — and coach your team to run it.

  • ✓ A repeatable, enforceable process
  • ✓ Your team runs the chain
  • ✓ Evidence → requirement → tested build
The difference

One generalist with AI instead of three specialists

Classically a feature runs through research, concept, design and development — with handovers that lose time and evidence. One person with high task density and AI support covers the same chain, without the breaks in between.

Vibe-coding UX + requirements engineering

One continuous expert, AI-supported
  • ✓ Research with real users
  • ✓ Machine-readable requirements (contract stories)
  • ✓ AI builds against the requirement
  • ✓ Behaviour & accessibility checked automatically
  • ✓ 50–80 % less prototyping time
  • ✓ A running prototype in days

The classic chain

Several trades, several handovers
  • ✓ Research with real users
  • ✗ Requirements scattered across slides & tickets
  • ✗ Evidence lost at the handover
  • ✗ Accessibility only at the end (or never)
  • ✗ Weeks to the first testable state
  • ✗ Three invoices instead of one
Slow & costly
Why it's faster

Efficient prompting means the right requirements in the right format

⏻

No guesswork in the prompt

Machine-readable requirements let the AI build the right thing in one pass — instead of something similar next to it.

🔗

Evidence stays connected

Every requirement carries its chain back to the research. No lost rationale at the handover.

✅

Quality built in

States, flows, WCAG and acceptance are part of the contract — a CI checks them automatically.

👤

The human decides

AI speeds up the building, not the deciding. What's good stays a human judgement.

Calculator

What does it save on building your features?

An estimate for the design-and-prototyping phase — exactly the part I compress with AI. Research with real users stays untouched.

8
12 days
Classic effort from concept to a testable prototype.
€880
= 110 €/h at 8 h · default 880 € = my rate of 110 €/h.
50 %
My evidenced range in prototyping: 50–80 %.
Saving per year
€0
0 person-days freed for the next idea.
Classic€0
With RE + vibe coding€0
0×
faster to a testable state
0 %
lower prototyping cost
Model estimate, not an offer. The efficiency gain applies only to the design/prototyping phase; research, alignment and production hardening are not included. Real figures depend on the project.

Not sure which offer fits? Let's find out in 20 minutes.

Tell me the moment you're in — an idea, a gap, or a capability to build — and I'll say honestly whether and how I can help.