Customer intelligence
Account tiers and feature requests
Define customer tiers and track normalized requests across account evidence.
- Audience
- product leaders, customer teams
- Required role
- Product leader or administrator.
- Product access
- Plan customer intelligence
- Navigation path
- Plan > Account tiers and Plan > Feature requests
Outcome
Normalize customer tiers and feature request evidence for transparent prioritization.
Before you begin
- Reviewed customer account matching
- An agreed tier definition
Define tiers
Create tier definitions from explicit commercial or strategic criteria. Document ownership and avoid silently changing historical meaning when the criteria evolve.
Create request definitions
Normalize recurring requests under a clear definition while preserving every supporting signal. Split requests that require materially different outcomes.
Review request evidence
Inspect affected accounts, tiers, source dates, and original records. Remove duplicates and reject weak matches before using counts in prioritization.
Use in prioritization
Combine request evidence with reach, severity, account context, strategy, delivery cost, and outcome potential. Customer tier should add context, not automatically determine the roadmap.
Related guides
Customer accounts and health
Combine customer evidence, requests, usage, and health into one account view.
Signals, insights, and themes
Review source evidence, extract insights, and group recurring customer needs.
Create and review a product plan
Turn a validated theme into a scoped, source-cited plan ready for delivery.