Product leadership on a part-time mandate
Zero to Launch
From the first version through launch and beyond.
You have an idea, a team and pressure on the timeline — but nobody who decides what to build next, thinks with you on the technical side, and is still there after go-live. That is what I take on: I steer your product until it is live, part-time. We usually start with a first version that actually ships. After that I stay as long as it is useful to you.
15+ years of product work in regulated environments · Raiffeisen Switzerland, Sparkassen-Finanzgruppe · EU AI Act certified
First version → and beyond
Clarity
Problem, scope, first version
Build
Prioritise, decide, steer
Live
In production, first users
After
Partner after launch, part-time at your side
One person across all four steps for more quality and speed.
The bottleneck
Between decision and delivery, speed falls away.
The ideas are there, the problem is known. Where do we start? The team can build. Delivery still does not move — because nobody closes the gap in between.
Agencies drop a concept and move on. Engineering waits for decisions nobody makes. And a full-time Head of Product is, at your stage, either too expensive or simply too early.
What is missing is someone who decides what to build next, supports the team on the technical side — and is still there in three months.
What you get out of it
Five things that change immediately
01Live, not a concept
No stack of concepts, no roadmap nobody reads. At the end of the first version there is a product real users can operate. From then on you discuss feedback instead of assumptions.
02One person instead of three roles
Product decisions, UX clarity and technical judgement come from one place. That saves you alignment rounds, handovers and the question of who actually decides. You get the experience from large programmes without buying their overhead.
03Speed with AI, without regret
AI makes your team fast — and at the same time produces code nobody has really read by the end. I make sure it is clear what gets checked: definition of done, reviews, tests, handling of data and traceability. You keep the pace without getting the bill for it in six months.
04A partner after launch
After launch the real work starts. I stay with you part-time: prioritise, sharpen, next releases — for as long as it holds. No handover, no knowledge that leaves with the contract.
05Discipline from an environment that does not forgive
15 years of digital products in banking and finance: migrations without a big bang, releases that still hold on Monday morning, quality under real pressure. What holds there will hold for you even more.
Why this runs differently from an agency
I steer the product, help actively in delivery when speed is needed, and stay on as a sparring partner when others have long moved on. You are not buying a project, but someone who stands next to you until the thing is running.
Mario Nüesch
Your partner at your side
Proof
Where this comes from
Raiffeisen Switzerland
Product ownership for the websites and applications of one of Switzerland’s largest banking groups, for more than ten years.
StarFinanz / Sparkasse Germany
Product management for delivering a finance app for children and young people of Germany’s Sparkassen.
Own SaaS starter kit
Authentication, billing, mailing, databases and more — a starter kit that makes the first version possible in weeks instead of months.
How it works
Four steps — and the last one does not stop
01
Clarity
We sharpen the problem, the scope and the first version. After that you know what will be built, what will deliberately not, and how we measure success. Usually one to two weeks.
02
Build
Prioritise, lock UX, build with your team — and get hands-on myself where it would otherwise stall. Quality standards from day one, not after the first bug.
03
Live
The first version goes into production. Usable, not a demo. From here real user behaviour counts instead of assumptions — and we see where to sharpen next.
04
Beyond
Part-time at your side: next releases, prioritisation, and a second opinion for you and your team when it matters. For as long as needed.
Where I help
What I take on when we work together
Not every team needs all of this. I step in where it is currently stuck, keep product, engineering and the team connected — and take on the rest when it takes work off your plate.
Product & steering
- Product management and ownership
- Sharpen the roadmap and product vision
- Cut and prioritise releases
- UX clarity, testable requirements
Team & stakeholders
- Coordination of individual team members
- Alignment with business, IT and leadership
- Communication through the right channels
- Orchestration of work and handovers
Engineering & AI
- Think through tech-stack decisions
- Build alongside where the team lacks speed
- Quality standards for AI-generated code in the team
- Privacy and the EU AI Act considered from the start
After launch
- Watch and measure operations continuously
- Next releases and sharpening
- Sparring for you and your team
- Onboard new people into the product
Is this a fit?
For you if …
- you own the product — as founder, CEO or CTO of a mid-sized or fast-growing company in DACH
- you are building a new product — SaaS, a mobile or desktop app, a platform, or an internal tool you use yourselves
- you want someone who decides, gets hands-on where needed, and stays — not just one of those things
- you prefer a part-time mandate over a permanent hire — I work like part of your team, but stay independent
- your team is getting faster with AI and you want quality to keep up
Less of a fit if …
- you are a large bank filling a 100% mandate through a recruiter — that runs through the usual channel for me; write anyway
- you only want a cheap coder — there are faster and cheaper ways to get that
- “something with AI” is the goal. Without a real problem behind it, I do not start.
- you want an agency that takes everything off your hands and only sends the invoice
- your timeline and scope are already set in stone and I am only meant to execute
What an engagement usually looks like
At the start we create clarity and then plan the implementation of the first version that is meant to go live. After that it often continues part-time — next releases, prioritisation, exchange.
What that means in practice depends on your product, your team and your timeline. That is why you will not find clickable packages here. We clarify scope and time commitment in conversation, and after that you know where you stand.
Let's talk
Write me three sentences about what you are currently working on. I will tell you honestly whether I am the right person and how we can move forward together.