For years Brian Donohue thought the six-week cycle was the sweet spot — they’d arrived at it independently, the same place Basecamp landed. Then Intercom rebuilt its support product around large language models, and the cycle, the triad, and the stable teams all went out the window.
Listen to this episode on Spotify or Apple Podcasts
Guest Bio: Brian Donohue
Brian Donohue is the VP of Product at Intercom, where he leads product development for Fin, the company’s AI agent for customer support. Rising to prominence through more than a decade at Intercom, he became one of the defining figures behind the company’s transformation from a traditional SaaS helpdesk into an AI-first customer service platform. Under his leadership, Fin grew from a June 2023 launch with a 25% resolution rate to a sustained average of 65% resolution across all paying customers — widely regarded as one of the most measurable success records in enterprise AI product development.
Previously, as Director of Product Management at Intercom, Donohue oversaw multiple product areas during the company’s rapid growth years, building deep expertise in outcomes-driven development, user onboarding, and messenger interface design. Before Intercom, he served as Director of Design at Houghton Mifflin Harcourt, where he accumulated more than twenty years of combined design and product leadership experience across enterprise and consumer contexts.
Donohue has been a vocal advocate for technical rigor in AI product development, having championed the adoption of consumer-grade A/B testing methodologies within Intercom’s R&D organization and the firm’s transition to outcome-based pricing — charging per resolved customer conversation rather than per seat.
Key Conversation Topics
Continuous reassessment as strategy — Intercom questioned “are we going bold enough?” every three months rather than making one big bet. Incremental big swings added up to a massive shift.
Inherited product blindness — Even though Fin was “built from scratch,” Intercom was still anchored to old UX decisions (button-based resolution confirmation) that took two years to recognize and fix. The fix actually significantly improved resolution rates.
Outcome-based pricing aligning incentives — Charging per resolution ($0.99/resolution) aligned what customers want, what the product team optimizes for, and what finance cares about in a way seat-based pricing never could. Resolution rate climbed from ~25% at launch to ~65%.
The AI operating model shift — Throwing out the six-week cycle, the triad, and traditional team topology. “Follow the work” rather than organizing around stable teams. Destabilizing but effective for speed.
Technical uplift required for AI product managers — Natural language as the programming interface doesn’t lower the bar — it raises it. Engineers think in rule sets and constraints; PMs now need that same rigor.
R&D Services as a critical new muscle — Forward-deployed R&D folks (like Palantir’s model) are essential for getting customers to value. AI transformation requires hands-on implementation support. PLG counterintuitively did NOT get amplified by AI.
Build to think / prototyping value for PMs — The real opportunity for PMs isn’t doing final design — it’s using AI tools to prototype fast enough to validate ideas before bringing in designers.
Themes
AI agent product development at scale
Outcome-based pricing in SaaS
Organizational transformation under AI pressure
The paradox of technical uplift under “democratized” technology
A/B testing rigor borrowed from consumer product applied to AI
Hey,
Thanks for reading this. I mean that. There's a lot of content out there competing for your attention, and you spent some of it here. I hope it was worth it. Even better, I hope it prompted you to think about something differently enough that you'd share it with someone who'd get something out of it too.
I started this podcast because tactics never stuck with me. What stuck were stories — business biographies, autobiographies, the decisions people made and why they made them. The principle only clicks once you know the story behind it.
So I built the thing I wanted to listen to. Every week I have two conversations with people who build in technology and product. Then I write the essay in my premium newsletter (Taste Maker) to distill the principles and reflect on the narrative — one that puts you inside the conversation, through my eyes. What caught me off guard. What I kept thinking about after we hung up. Where the principle actually lives once you strip away the jargon.
I make this for myself first. If you read the way I do, you’ll want it too.
PS — If you want to pitch coming on the show, or you know someone I should talk to, shoot me an email at caden@hey.com with "January752" in the subject line so it gets past my filters. I'm not optimizing for famous guests. I'm optimizing for interesting conversations, even from people who aren't LinkedIn influencers.
