I speak at conferences, meetups, webinars, and podcasts about web growth, AI tooling, conversion, and how modern web teams operate. Practitioner stories, not panel platitudes — built from running web at Pipedrive (24 languages, hundreds of A/B tests a year) and operating my own portfolio of products with AI agents in the loop.
Conferences, meetups, webinars, and podcast interviews — anywhere the conversation about web, AI, and growth is worth showing up for.
Why solid products stall after launch — the messy gap between product, GTM, and growth, where ownership breaks down, and how launch surfaces (websites included) quietly expose whether cross-functional alignment actually exists.
Talk on the new operating model for web teams in the AI era — how search behavior, traffic shape, and on-page craft are shifting, and what web teams can do this year. Exact session date TBA.
Improving conversion when AI is eating organic traffic, doing more with less, and why the website still matters more than most teams think.
How Pipedrive's web team is structured, how it operates at scale, and what it takes to run web at a global SaaS company.
I don't run with a fixed deck per topic — each session gets shaped to the audience, time slot, and what the event actually cares about. These are the areas I'm comfortable going deep on, in any format from a 15-minute keynote to a half-day workshop.
How modern web work actually gets done with Claude Code, MCPs, context repos, and skills in the loop. What a one-operator portfolio looks like at the cadence of a small team, and what bigger orgs can borrow from it. Lessons from running web at Pipedrive in 24 languages alongside an independent product portfolio.
What it actually takes to run web inside a SaaS org — stakeholders, alignment across product, brand, growth, and lifecycle, and where ownership tends to break down. Why web is usually under-leveraged and how to position it as a real function, not a service desk that ships pages on request.
How to actually move the numbers on a B2B SaaS website — research-led hypotheses, building an A/B testing program that survives contact with reality, and the recurring patterns of wins (and "won't work twice") I've seen across hundreds of tests. The practical version of CRO, not the deck version.
What it actually takes to run a multi-language website without it becoming a maintenance nightmare — content workflows, translation quality, market-specific UX, performance, where AI-assisted localization helps and where it quietly breaks things, and when not to localize at all. Drawn from running Pipedrive's web in 24 languages.
Easiest way to reach me is a LinkedIn DM — share the audience, format, date, and what topic you'd like me to bring. I reply fast.