RS360: Kill the Hippo

The podcast discusses the challenges of building SaaS businesses in the current landscape, particularly emphasizing the importance of user research and strategic prioritization in product development. With AI lowering the barriers to building software, the key differentiator for success lies in deeply understanding customer needs and aligning product decisions accordingly. The discussion highlights common pitfalls, such as building features based on loud but unrepresentative customers or chasing popular trends without validating market fit. Maintaining a clear Ideal Customer Profile (ICP) is critical, and companies - even those with strong product-market fit - must continuously reassess their ICP as markets evolve.

A central theme is the value of direct, ongoing engagement with customers through conversations rather than relying solely on surveys or passive feedback. Real-world case studies illustrate how companies like Buffer and BookMe regained traction by refocusing on their core users after straying upmarket. The conversation also covers effective prioritization frameworks like RICE, while acknowledging their limitations due to subjective scoring and potential bias. Ultimately, the emphasis is on founder-led customer discovery, learning from both successful and struggling businesses, and making intentional decisions about product evolution - including when to sunset features or pivot entirely to serve a new audience.

• What if you redefined your Ideal Customer Profile (ICP) based on silent power users instead of vocal support requesters?

  • Move: Identify your top 10 highest-retention customers using analytics, then personally interview them this week to uncover their workflows, goals, and unmet needs.
  • Why Now?: AI lowers barriers to entry, increasing competition - precision in targeting reduces churn and acquisition costs. Most SaaS companies drift from their true ICP over time without realizing it.
  • Expected Upside: Sharper ICP leads to more effective marketing, fewer wasted features, and higher LTV from better-aligned product evolution.

• What if you killed your most requested feature because it served the wrong customer segment?

  • Move: Audit your feature request log - flag the top 3 most upvoted items, then map each to the customer segment requesting them. Deprecate or hide one that aligns with low-retention or non-core users.
  • Why Now?: Popularity-driven development creates technical debt and UX bloat. The market shift toward AI and simplicity rewards focus over feature volume.
  • Expected Upside: Streamlined product reduces maintenance load, improves onboarding clarity, and strengthens positioning for your real ICP.

• What if you hired your next product thinker from your existing user base instead of the job market?

  • Move: Scan your user list for power users who've submitted detailed feedback or built integrations; reach out to 3 this week with a proposal for a paid advisory or part-time product role.
  • Why Now?: Founder-led product direction is critical early-on, but scaling requires deep customer empathy. Former users bring intrinsic understanding of pain points and context.
  • Expected Upside: Faster, more accurate iteration with built-in validation - reduces guesswork and increases feature adoption rates by aligning development with real usage patterns.

• Interview at least 3 - 5 active users quarterly using in-person or video calls to uncover unmet needs and avoid over-relying on passive feedback like surveys.
• Define and document your Ideal Customer Profile (ICP) explicitly, then validate it annually by analyzing who gets the most value from your product, not just who requests features.
• Run all feature ideas through a simple RICE-like scoring system (Reach, Impact, Confidence, Effort) to expose bias and ensure decisions are structured, even if the final call relies on intuition.
• Pause new feature development at least once per quarter to focus on refining existing functionality - e.g., reducing clicks, fixing UX friction - based on direct customer observations.
• Consider hiring or consulting with former customers for product input, as their real-world usage can reveal flaws and opportunities that internal assumptions miss.