Beta Customer Discovery
On the schedule you choose, the agent listens for people publicly posting about the problems you solve, qualifies them against your ICP, and drafts a helpful public reply and a warm DM for each — landing one approval before anything is sent.
Saves you ~2.6 h / week
How it works
- Trigger
- On the “Beta discovery run” schedule.
- Job
- Listen for problem posts, qualify, draft helpful replies and DMs, and approve.
- Outcome
- A qualified beta-customer list with helpful outreach drafts.
What it installs
Agents 2
-
Discovery Agent
Social-listens for the problem you solve and drafts value-first outreach for approval.
-
Beta Customer Discovery Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Beta Customer Discovery quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Beta Customer Discovery
Listen for problem posts, qualify, draft helpful replies and DMs, self-critique, and approve.
Goals 1
-
A steady flow of qualified beta prospects from real problem posts
Discovery exists to keep finding people who describe your problem in public and reaching them with genuine help — a reliable pipeline of qualified beta conversations, not promotional spam. Success looks like: Every run produces an approved batch of qualified prospects in which each carries its source post and exact pain phrase, each public reply helps even if the person never uses the product, the maker relationship is disclosed, surface norms are respected, and the beta is framed as mutual help.
Skills 2
-
social-listening
Build a pain-phrase keyword map, listen across the surfaces your buyers post on, and qualify posters by signal strength, ICP fit, and recency. Adapted from public growth playbooks.
-
helpful-reply
Write value-first public replies and warm DMs to people posting about your problem — help first, disclose the maker relationship, frame the beta as mutual help, never lead with a pitch. Adapted from public growth playbooks.
Schedules 1
-
Beta discovery run
Runs beta customer discovery on the schedule you choose. ## Professional quality control Objective: complete the recurring Beta Customer Discovery operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify ICP fit, trigger evidence, contact lineage, conversation state, offer and policy limits, and every personalization detail. Outreach must sound like one informed person writing to another, without generic AI phrasing, fake familiarity, filler, hype, manipulative urgency, or reusable template lines disguised as research. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
Requirements
- Browser access to X, Reddit, and your niche communities — The agent works in X, Reddit, LinkedIn, and the communities your buyers post in through their web interface in your browser to find and read posts about the problems you solve, and pauses for your approval before replying or sending a DM; until you connect it, it works from attached exports and the discovery context you provide.
Setup guide
How to Automate Beta Customer Discovery
A practical guide to finding beta customers from public problem posts: keyword maps, qualification tiers, value-first replies, and approval on every send.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.