
I build platforms as products, and the organizations that run them.

I'm a Principal Product Manager, Platform at Cint. My work spans platform products, APIs, developer experience and increasingly AI-native interfaces such as MCP, along with the organizational structures around them.
I work where product strategy, system architecture and team design turn out to be the same question.
Product work atFull CV →





What I work on
Four things I want to build more of
Platform as a product
Capabilities teams choose to use
Shared platforms create value when teams want to use them, not simply because they have to. That means treating internal developers as real users: understanding their problems, creating a roadmap around them, measuring adoption and enabling teams instead of becoming their gatekeeper.
APIs, MCP & ecosystems
The surface others build on
APIs are products with users, lifecycle decisions and a developer experience of their own. MCP adds a new kind of consumer: AI agents. I'm interested in how reusable product capabilities can serve developers, partners and machines without creating another layer of special-case integrations.
Product strategy
Where to invest, and why now
Direction that still makes sense when explained to a customer, an engineering lead and a board, including where to invest, what to stop doing and why the trade-offs are worth it.
Team topologies & org design
Organizations shaped for flow
Team boundaries shape the systems we build. I care about ownership models that reduce cognitive load and coordination, let stream-aligned teams move independently and keep platform teams from becoming another dependency.
Outside the job
Things I build on the side
I like building things outside my day job: sometimes around a problem worth solving, sometimes simply to understand an idea by making it real. AI tools have changed how far I can take those ideas myself; I increasingly use them across product thinking, design, prototyping and implementation. Not everything needs to become a company.
Building · Mandoria
Making care bureaucracy bearable
Care, health and insurance processes often turn the affected person into the integration layer between doctors, insurers, care services, suppliers and authorities, repeatedly carrying the same information from one process into the next.
Mandoria won't abolish that system. It brings information, processes, deadlines, documents and forms into one place, so more of the organizational load can sit with software instead of the person navigating it.
I'm building it solo with AI deeply embedded in the process, using tools such as Claude across product thinking, design and implementation. Part of the experiment is understanding how much of a real product one product person can now build independently.
Building · folgen
Series, one episode at a time
Streaming has spread the shows I watch across half a dozen services, and “where was I?” ends up scattered across notes, memory and apps that live on ads.
folgen is a calm, artwork-led series tracker: one tap ticks off an episode, and it shows what's next, what airs soon, where a show streams in Germany and an honest look back at the year in series. It runs as an installable web app on iPhone and in any browser, works offline and is open source under the MIT license. The interface is German.
As with Mandoria, AI is deeply embedded in how I build it, with Claude Code involved in everything from product decisions and design to code, reviews and releases. And I build it in the open on GitHub, milestones and decisions included.
AI-assisted builds · experiments
Building to understand
I use small builds to explore ideas quickly: websites, product prototypes, AI workflows and tools that may never need to become full products.
Claude and other AI tools are increasingly part of that process, shortening the distance between an idea, a product decision and something I can actually use.
More experiments and unfinished things live on GitHub. See what I'm building on GitHub ↗
Open to
Open to the right work
I'm most interested in problems around platforms, APIs, developer experience and product organizations, particularly where product, engineering and organizational design overlap. That can take different forms.
Advisory & sparringOpen now
A second perspective on platform, product and organizational decisions, whether it's one difficult question, a strategy that needs challenging or an ongoing sparring relationship.
Mentorship & talksOpen now
Mentorship for product managers taking on broader scope or leadership responsibilities, and talks about platform products, APIs, product organizations and the realities of evolving systems that already exist.
The right product roleNot actively looking
Principal or product leadership roles where platforms, APIs, ecosystems or developer experience are a meaningful part of the product problem, ideally with enough scope to work on the organization around the product as well.
Fractional platform product leadershipNot actively looking
For organizations that need experienced platform product leadership for a defined period, to clarify the problem, establish ownership, shape a strategy and leave a team able to carry it forward.