Role → Platform PM (Core & AI) @ Certa (prev. Frontend Engineer)
Focus → B2B SaaS · AI/ML Products · Fintech & Compliance
Superpower → I came from engineering — I speak both languages fluently
Now → Building an open-source, AI-native signal aggregator for PMs
I'm a builder-first product manager with a frontend engineering background. That means I don't just write specs — I prototype, I read PRs, and I can actually feel the pain when a system is over-engineered.
At Certa, I own the core platform and AI surface — working at the intersection of enterprise workflow automation, compliance, and integrations — one of the most technically complex surfaces a PM can own.
Things I care about deeply:
✦ Reducing time from customer insight → shipped feature
✦ Building products that engineers are proud to work on
✦ AI that actually earns its place in a workflow (not just a chatbox)
✦ Open source as a distribution strategy, not just a license
✅ Shipped — n8n-debugger
An open-source AI-powered debugger for n8n workflows. Paste a broken workflow, get a diagnosis. Built for the thousands of teams running automation on n8n who spend more time debugging than building.
What it does: AI analysis of failed n8n workflow executions
Who it's for: Developers & ops teams running n8n automations
Why it exists: Debugging n8n is painful. It shouldn't be.
Stack: n8n · AI · Open Source
An open-source, AI-native tool that pulls product signals from Slack, Linear, Intercom, GitHub Issues, and more — and connects them directly to roadmap outcomes. Not another voting board. An actual reasoning layer.
Stack thinking: Next.js · Python · Claude API · pgvector · MCP
Why OSS? Every PM team has this problem. Nobody should pay $70K/yr to solve it.
📣 Follow @stephin007 to catch the launch
| Domain | What I bring |
|---|---|
| 🏢 B2B SaaS / Enterprise | Integration complexity, multi-stakeholder discovery, enterprise sales loops |
| 🤖 AI/ML Products | Prompt design, model evaluation, when AI adds value vs. when it's a liability |
| 🔐 Fintech & Compliance | Regulatory constraints as design parameters, not blockers |
| ⚙️ Integrations & Infra | I've built the things I now spec. That changes how I write requirements. |
I'm not an engineer anymore — but I still think like one.
Languages I can read, write, and debug:
Tools I actually use:
Open to:
✦ OSS collaborations (especially PM tooling & AI automation)
✦ Advisory for early-stage products at the AI × compliance intersection
✦ Conversations about what good product actually looks like
