Recruiting participants without a panel budget

Panels are great for strangers. For existing users, they're the wrong tool — you're paying a recruiter to find you someone you already have in your database. Below, six sources ordered by signal quality. The higher up the list, the closer the participant is to the problem you're solving.

1. Your existing users

Highest signal, lowest friction. These are the people whose behavior is already shaping your roadmap. Reach out via in-app message or a targeted email. Keep the ask small: "Fifteen minutes, this week or next, about how you use [feature]."

The trick is not being annoying. Filter to users who've been active recently, and don't ask the same person twice in a quarter. A simple internal spreadsheet of "who we've talked to, when" prevents the common failure mode of rinsing your power users.

2. Your waitlist

People who opted in but haven't used the product yet. Strong intent signal — they raised their hand for a reason — and you can ask about that reason directly. Particularly useful when you're researching the shape of a problem, not the usability of an existing solution.

Expected response rate from a cold waitlist email is around five to ten percent. From a waitlist that's been warmed with a few newsletters, closer to twenty.

3. Your customer support tickets

People who filed a ticket have a concrete opinion and proven willingness to express it. Filter for tickets that asked how-to questions — those are users who were trying to do something and got stuck, which is exactly the population you want for discovery research.

Avoid escalated or angry tickets for this purpose. Those users are informative too, but they're a different conversation. Mixing them into a general discovery study muddies the data.

4. Your Slack community or Discord

If you have one, it's a goldmine — highly engaged users who already know how to articulate their experience. Post a short request; expect a response rate north of twenty percent. The tradeoff is small sample size and selection bias: community members skew toward the power-user end of your spectrum.

Useful for depth. Not useful for representativeness.

5. Your teammates

Good for sanity checks: "Does this copy make sense? Can you find the settings page?" The moment you try to use teammates for discovery research, you'll get misleading answers. They know too much, care too much, and want to help.

Use them to catch embarrassing errors before external sessions. Don't use them to decide what to build.

6. LinkedIn, X, and Reddit outreach

Effortful but useful for net-new audiences — when you're researching a problem outside your existing customer base. The effort is in the targeting: you want people who are currently doing the thing, not people who are generally in the field.

A well-targeted LinkedIn search ("senior PM at early-stage B2B SaaS") plus a short, specific message ("I'm researching how small teams handle feature prioritization; would you have fifteen minutes this week?") converts at two to five percent. Subreddits with active professional communities (r/ProductManagement, r/UXResearch) are higher-yield but you need to participate first, not parachute in.

On incentives

A twenty-five dollar gift card covers a fifteen-minute session for most audiences. Enterprise buyers don't care about gift cards — offer a product credit or a charity donation instead. Most people will do it for free if you ask kindly and respect their time. Pay anyway, when you can. It's the right thing, and it compounds into a reputation for being easy to work with.