Agente de Búsqueda de Candidatos Beta

The Beta Roster Without the Recruitment Email Blast

Product teams launch betas and recruit candidates by emailing every customer and hoping for the best. Most respond "sure, sign me up" without the use case actually fitting, and the beta data is muddy from week one. The Beta Candidate Finder Agent works the other direction: given an upcoming beta and its target use case, it surfaces the 10–20 customers whose CSM notes, support patterns, and product usage best match — so PM and CSM can have intentional conversations with the right accounts.

How It Works

The agent runs weekly against the active beta roster maintained in Notion. For each beta with status 'recruiting,' it pulls the target use case description and feature scope, then searches across CSM call notes, support tickets, and (if connected) product usage patterns for accounts that match the use case. Each match is scored on: use-case fit, account health, willingness signal (any prior beta participation, public advocacy), and PM-relationship status. The top 10–20 candidates land in a Notion roster; PM and CSM get a Slack ping when a beta has fewer than 10 strong candidates.

Required Connections

• Salesforce or HubSpot — account and CSM-relationship data
• Demodesk — CSM call notes
• Zendesk or Intercom — support ticket history
• Notion — beta roster destination
• Slack — PM/CSM notification

Scope Note

Reassigned from Product to CS / PMM per the v1 plan: product teams shouldn't recruit, CS/PMM should. The agent reads product-usage data (when connected) but the recruiting motion stays in the customer-relationship team.