Hook product moments to trigger customer conversations that reveal monetizable use cases
For horizontal products with many use cases, you can't guess which ones will pay—you need systematic conversation triggers. Build hooks at key product moments (signup, first poll created, first response received) that automatically prompt users to share feedback or book demos. These aren't sales calls—they're discovery calls where you learn what problems users are trying to solve. Through hundreds of these conversations, patterns emerge showing which use cases have budget, urgency, and willingness to pay. This intelligence then drives what features you build, what goes behind paywall, and who you target for sales. The conversation hook must be authentic ('Can you share product feedback?') not salesy ('Book a demo to unlock premium features').
When to use
When you have horizontal product with many diverse use cases. When you're unsure which features to monetize. When free users aren't converting and you don't know why. When you're early-stage (sub-$1M ARR) and need to understand your buyers. When deciding what to build next or what to put behind paywall.
Don't do this
Building features based on internal assumptions without customer input. Waiting for customers to reach out to you. Only talking to customers after they pay. Using generic 'book a demo' CTAs instead of authentic conversation hooks. Not systematically capturing and analyzing insights from these conversations. Treating every conversation as sales opportunity instead of learning opportunity.
1 Founder Who Did This
Every Polly signup triggers email asking 'Do you have any product feedback for us?' Also offers demo booking. These hooks enabled hundreds of customer conversations revealing which use cases would convert (company all-hands, sales kickoffs, post-event feedback) versus which just drove free viral adoption (lunch polls, class naming).