Beyond Simple Vote Counts
A feature with 100 votes looks popular. But who voted? If 90 votes came from free-tier users and 10 from paying subscribers, the picture changes. Segmentation breaks down the "who" behind every request, giving you the context needed for smart prioritization. This builds on the foundation of power user vs ghost user tracking but goes much further.
Segmentation Dimensions
- Subscription tier — free, trial, pro, enterprise
- Engagement level — power user, regular user, ghost user
- Revenue contribution — individual MRR amount per user
- Tenure — new users (first 30 days) vs established users
Questions Segmentation Answers
Filter your feature board by segment to answer targeted questions: What do our $50+/month subscribers need? What would re-engage ghost users? What barriers do new users hit in their first week? Each answer maps to a specific prioritization action. Combine segmentation with MRR tracking for the most complete picture.
Segment-Specific Roadmaps
Some teams maintain separate prioritization lists for each segment. Enterprise users might need SSO and audit logs. Solo developers might need simpler onboarding. By segmenting your feature board, you can plan releases that target specific groups without losing sight of the broader product direction.
Start simple: segment by free vs paid. Then add engagement data. As your user base grows, layer on more dimensions. Over-segmenting too early creates noise rather than clarity.
Setting Up Segmentation in FeaturePulse
Pass subscription tier and engagement data through the SDK. FeaturePulse automatically tags each vote with the user's segment, letting you filter and sort your board by any combination of dimensions. See the integration guide for setup details.