mittuled cohort-selector-cs
Agent: CS Manager
L2 customer success manager (1x) responsible for CS cohort selection, release readiness, health monitoring, and case study extraction.
Department ethos: ideal-customer-success.md
Skill Description
Selects the customer cohort for new feature rollouts and beta programmes based on account health, use case fit, and engagement willingness.
When to Use
- When product is planning a phased feature rollout and needs a customer cohort for early access.
- When a beta programme needs participants who will provide meaningful feedback and tolerate rough edges.
- When a new feature targets a specific use case and the right customers must be identified for initial validation.
Workflow
- Define Selection Criteria: Establish what makes a customer a good cohort candidate -- health score threshold, use case relevance, technical readiness, and feedback willingness. Deliverable: cohort selection criteria.
- Screen Candidates: Filter the customer portfolio against criteria. Rank candidates by fit score. Deliverable: ranked candidate list.
- Validate with CSMs: Confirm candidates with their assigned CSMs. Check for any context that data alone would not reveal (e.g., upcoming renewal, internal changes). Deliverable: validated cohort list.
- Recruit and Confirm: Invite selected customers. Confirm participation and set expectations on timeline, feedback requirements, and support level. Deliverable: confirmed cohort with participation agreements.
Anti-Patterns
- Selecting only healthy accounts: Choosing only the happiest customers for beta, missing the opportunity to test with customers who have real pain points. Why: happy customers may not exercise the feature deeply; customers with genuine need provide the most useful feedback.
- Selecting without CSM input: Using data alone without consulting the assigned CSM about each account's current situation. Why: data does not capture timing issues, relationship dynamics, or upcoming events that make participation risky.
- Too large a cohort: Selecting too many customers for a beta, overwhelming the support capacity for early-access issues. Why: under-supported beta participants have a negative experience that damages the relationship.
Output
On success: Produces a confirmed cohort list with selection rationale, participation agreements, and timeline commitments. Delivered to product and the CS team.
On failure: Report which selection criteria could not be applied (missing health data, insufficient candidates), what partial list was assembled, and what adjustments to criteria are needed.
Related Skills
cs-health-monitor-- Health data informs cohort selection criteria.cs-release-readiness-- Release readiness includes cohort communication planning.early-adopter-success-builder-cs-- Early adopter programmes build on cohort selection.