Berlin · 10+ years · DACH enterprise
Ways to work together
I embed with engineering-led companies that need product leadership they can trust with their most complex systems. Two engagement models, both shaped around your team.
Embedded Product Lead
Most commonCustom · per engagement
You have the engineers. I own the roadmap, discovery, and the operating rhythm that outlasts the engagement.
- Full roadmap ownership: strategy through delivery
- Discovery, prioritisation, and stakeholder alignment
- Operating cadence and KPI dashboards that stick
- Cloud, data, and AI product initiatives
Advisory & Sprints
Custom · per project
An outside eye to frame the problem, pressure-test it, and hand your team a plan they can execute.
- Product, platform, and org audits with action plans
- Strategy sprints and roadmap resets
- Go-to-market and adoption playbooks
- Due diligence and vendor selection
Common questions
- How long is a typical engagement?
- Embedded engagements run three to six months minimum, long enough to own delivery and leave the team self-sufficient. Advisory sprints run two to six weeks with a defined deliverable.
- Do you work remotely or on-site?
- Berlin-based, embedded in your tools: Slack, Jira, incident calls. On-site for kickoffs and key milestones across the DACH region.
- What does "Custom" pricing mean?
- Scope, duration, and team size set the price. Book a call, tell me the problem, and you get a clear number, not a vague range.
- Can you work under our compliance requirements?
- I've shipped under GDPR, BSI, KRITIS, and Gematik. Compliance shapes the architecture from the first design decision, not the week before launch.
- Which model is right for me?
- If you have engineers but no one owning the product, that's Embedded. If you know what's wrong and need a plan your team can execute, that's Advisory.