Finding your ICP, prioritizing feature requests, and competing on value

Executive overview

Most founders default to highest-paying customers as their ideal customer profile (ICP), but the better signal is retention plus expansion — customers who stay longest and grow their usage most. Feature prioritization follows a similar logic: skip complex frameworks early on and use a simple pain-vs-effort matrix, guided by product vision and customer intuition. Competing on price is a losing game; differentiation through value and brand is what separates durable businesses from commodities.

If you can't articulate why you're different, you're competing on price — and you'll lose.

Defining your ideal customer profile

• ICP is not necessarily your highest-paying customer — look for oldest customers who have also expanded usage the most
• Retention (staying power) and expansion (growing usage/spend) are the two SaaS growth levers; ideal customers score well on both
• Most products have multiple ICPs; rank them by their combination of retention and expansion potential
• A third angle — promotion — applies when customers (e.g., bloggers, infomarketers) have audiences and can refer at scale; rare, but can drive explosive early growth
• Horizontal tools make ICP definition harder; vertical SaaS narrows the field and simplifies the choice
• Personas are only useful if grounded in real customers and tied back to retention/expansion metrics

Prioritizing feature requests

• Simple pain vs. effort matrix beats complex frameworks early on: high pain + low effort → just ship it; high pain + high effort → evaluate impact on core metrics first
• Low pain + high effort → drop it; low pain + low effort → do sparingly, don't let these crowd out growth work
• Whether the requester is an ICP matters, but stay flexible early when you're still testing hypotheses
• Product sense — the "art" — comes from deep, repeated customer conversations; it can't be replaced by data alone
• Estimating adoption ("would 5% or 30% of customers use this?") is a useful gut-check even without hard data
• Product vision acts as a filter: features that pull you into adjacent markets or second-rate clones of competitors should be declined

Competing when a rival undercuts your pricing

• Compete on value, not price — make it an apples-vs-oranges comparison, not apples-vs-apples
• Identify the "light bulb" moment in your sales pitch: what makes a prospect lean in? That's your core value
• Usage-based pricing vs. flat pricing: start slightly cheaper than the competitor's flat price, then let value prove itself as usage grows
• Undifferentiated products become commodities; building a brand moat lets you charge more and still win deals
• Leaning into being more expensive (not despite it, but because of it) can itself be a positioning strategy

How product managers should spend their time

• The PM's unique contribution is prioritization — surfacing what's important for customers and for the business
• More time aiming (synthesizing inputs) than executing is the right balance
• Synthesis happens in conversation, not in isolation — share working theories with teammates or customers and let them challenge it
• Inputs to synthesize: user interviews, market signals, surveys, analytics, team observations
• Avoid projecting false confidence; ask for pushback even when presenting a clear direction
• Roadmap tools (AirFocus, etc.) are useful early when immersing in a new market — but have sharply diminishing returns after the first few quarters
• Roadmaps should be outputs of alignment conversations, not outputs of a feedback-categorization process