The clearest way to show how I work: one venture I drove from a cold market signal to paying users with zero churn — and the operating model that got it there.
Case № 01Master use case · how I work, end to end
DACH · 2025~6 min read
The pitch
From signal to product-market fit.
One venture, end to end. From a cold market signal to paying users with 0% churn. Plus the operating model that made it possible.
The numbers — end to endValidation → PMF
01 · Validation cost
< €10k
Signal to validated buyer.
02 · Ad spend
€0
Cold email to a waitlist page.
03 · Build time
~2.5mo
Two-week cycles, end to end.
04 · Churn at PMF
0%
Paying users. They keep using it.
The pivot — stage 03
The pain was real. The budget was one layer up.
Picked the wrong audience first. Interviews exposed it. Rebuilt around the buyer one layer up.
Wrong
Has the painNo budget
vs.
Real
Has the budgetDecides
The case has the pipeline, the operating-model change, and the result. About six minutes.
03 — How to work with meOne entry door · one expansion
Start with a day. Then decide.
A paid diagnostic day to find what's actually broken. If it's worth fixing, I ship the fix end-to-end over 90 days: product, engineering and growth. Either side can stop after day one.
Start hereDAY 0
Diagnose
One day inside your team.
1 day · on-site · written diagnosis
Where the gap between shipping and moving the numbers actually sits.
A 90-day plan with the structural fix, scoped to a shippable outcome.
In your repo. In your standups. Shipping. Not a workshop. Not advisory. Not a coach.
04 — What it's like to work with meFrom founders & researchers
"Parachute in and build what runs."
“
Mario has an incredible gift for early-stage venture building. He took us from an initial idea to a validated MVP within a few weeks.
Janis Schumacher
FOUNDER IN RESIDENCE · 120 VENTURES
“
He rolls up his sleeves and gets things moving. True to his “parachute in and build what runs” mindset.
Andrej Bielicky
FOUNDER IN RESIDENCE · 120 VENTURES
“
Mario turned, in less than two weeks, years of scientific research into tangible product features that anyone could understand.
Michael-Bernhard Zita
RESEARCHER · CFEPS
05 — Common questionsBefore you reach out
Five questions I get most.
01What is a Principal Product Operator?+
One operator who carries product, engineering, and growth in a single head. Instead of hiring three roles and managing the handoffs between them, you point at the outcome and I ship it end-to-end, AI-native. Hands-on in your repo and your standups, not advising from the side.
02How long is the engagement?+
Most engagements run 90 days. The window starts with a paid diagnostic day to find what is actually broken. If both sides decide it is worth fixing, we move into the 90-day build and I ship the fix. Either side can stop after the diagnostic day.
03What does AI-native actually mean here?+
The product and the way it gets built are designed around AI as leverage, not bolted on after. PLG and experimentation are worked into the product itself, and the same operator who decides what to build also builds it, so the loop from customer signal to shipped outcome stays short.
04Who is the right fit for this work?+
Fast-growing Series A and bootstrapped teams in DACH that are funded, staffed, and shipping every week, but where the numbers have stopped moving. Typically velocity is up and retention or activation is flat. The fix is structural, not more headcount.
05What stays after the 90 days end?+
The outcome itself, shipped and in production, plus a clean handoff of what runs to whoever inherits it. The team keeps shipping against customer outcomes, not tickets, after I leave.
06 — How to startThree lines is enough
You get a reply in 1–2 business days.
If two sentences are enough, email me directly.
Stage — where you are right now
Symptom — what's actually breaking
Timing — when you'd want me to start
Tell me what's going on. I read every reply myself.
Analytics
This site can use Vercel Analytics (cookieless, aggregate) so I can see which pages get read. Nothing loads until you accept.
