The realities ofparticipant panels
A practitioner's guide to advocating for, building, and sustaining research panels, drawn from 25 industry interviews.
- 1The realities of panelsWhy this isn't a how-to guide, and what we mean by panel
- 2Why teams build panelsThe drivers behind owned panels, and when to buy instead
- 3Setting up your panelStakeholders, tooling, segments, size, and first recruits
- 4Keeping it healthyEngagement, consent, representation, metrics, and endings
Part one
The realities of panels: it only looks easy from the outside.
About this project
This piece is part of the ResearchOps community's ongoing volunteer project exploring the Participant Lifecycle. Based on community feedback, this series focuses on participant panels.
Panels are often seen as a cornerstone of scaling research because they promise to solve one of its biggest headaches: recruiting participants. But like most initiatives, they succeed less often than you might hope, and the path to making them look easy is long, winding, and not entirely within your control.
As diligent researchers, we started with desk research. Content on panels has exploded in recent years (see Kate Towsey's Research That Scales), and we figured a roundup of existing research would be a great start. While we found plenty of articles about panels, most of it stayed high level and almost all of it was written by vendors with a product to sell. We found few case studies and virtually no unbiased guidebooks on how to navigate the decisions teams actually face when building a panel.
To fill that gap, we interviewed 25 practitioners from the ResearchOps community who had set up a panel, managed one, or often both. This series draws on their experiences across a range of panels, including B2C, B2B, government, and non-profit or third sector.
This was supposed to be a how-to guide
We started with a simple goal: write a how-to guide for building and running a participant panel, grounded in the experiences of real researchers. A small convenience-sample survey surfaced consistent themes around the objectives, challenges, and success metrics of panels, and we planned follow-up conversations to add context, color, and detail.
But then we talked to people. As expected, many echoed the core themes from our survey and desk research. What we didn't expect was how much each researcher's context and constraints revealed a bouquet of experiences rather than a repeated linear path.
So this series won't give you a single playbook for building a panel. Instead, it shares the stories practitioners told us, in the hope they help you tackle your own mix of challenges and constraints.
What do we mean by panel?
Ask ten researchers to define a panel and you'll get ten answers, but most converge on something like this: "a set of potential respondents who have declared that they will cooperate for future research projects." That's useful to hold onto, because it names the one thing every version of a panel shares: access. Beyond that, size, audience, and management style all vary.
That variance is wide enough that "panel" can mean a plain spreadsheet you email twice a year, or something with screening, profiling, and dedicated tooling behind it. Both get called a panel, and both can be good.
As Ted Kendall put it:
If you had a customer list and you were just sending out a regular survey every once in a while, you can do that, and you can call it a panel. But it's not leveraging what a panel can be.
General panel fundamentals
Consent to repeat contact
Participants have agreed to, and expect, being contacted again.
Utility beyond one project
Their value to the organization outlives any single study.
Baseline data up front
Some level of profile data is collected at sign-up for screening and targeting.
Built for research
The relationship exists primarily for the organization's research purposes.
What isn't covered here
Four adjacent things get called panels, or get confused with them. This series leaves them alone.
Communities
We consider panels fundamentally hub-and-spoke: one organization developing individual relationships with many individuals. When panelists start interacting with each other, it moves closer to a community. The two overlap in practice, but communities are out of scope.
Third-party panels
Most of these stories reflect owned panels a researcher set up and grew. Third-party providers can fast-track panel creation, but this series is designed to support anyone building their own.
Customer advisory boards
Leveraged similarly to panels, but the nature of the relationships, size, and duration tend to differ. We don't broach advisory boards here.
Synthetic panels
A newer, and still hotly debated, form of research. This project doesn't touch synthetic research, digital twins, or other customer-like panels.
There is no one way
The zone of success for a panel is defined by three forces: your participants, your organization, and the resources you can marshal to create and sustain the panel. To succeed, you need a way that works for all three.
Throughout this series you'll hear from researchers on how they navigated real-world constraints. Every quote and case study is a real conversation, not a composite. The point isn't that you should do exactly what any one of them did. Rather, we hope you use their stories to better define and navigate your own constraints.
How this series is organized
The articles roughly align with the phases our experts encountered. In practice, your experience may not line up one-for-one with the order laid out here. You may need to bounce back and forth as you have the necessary conversations and build support and buy-in.
Part two
Why research teams build panels, and when they should buy instead.
Recruitment is the bottleneck
If you've spent any meaningful time doing research, you already know the feeling: a project lands, the brief is clear, and then you spend weeks in preparation alone. Finding people. Chasing responses. Coordinating calendars. Sending the same email for the fifth time.
Recruitment is a persistent operational bottleneck in research.
The biggest time sink in UX research is finding, recruiting, and identifying participants.
Teams that have built participant panels describe a different experience entirely: one where the infrastructure is established before research needs emerge. But before building a panel, consider the factors below when deciding how to proceed.
Speed and efficiency
The numbers are hard to argue with. According to User Interviews, sourcing 50 B2B participants through ad-hoc recruitment can take roughly 47 times more labor hours than through an owned panel. Across the industry, community-based recruitment is cited as five times faster than ad hoc methods, with some teams receiving answers to UX questions within a single day.
The goal most practitioners describe is getting in front of users within a standard one-to-two-week sprint, something that's nearly impossible when sourcing from scratch.
Describing the appeal to stakeholders plainly:
We could put in a few-minute survey on a Friday and then on Monday morning we have all these results and we can analyze it. It's super fast where everything else would take a lot longer.
Self-service and democratization
One of the less-discussed benefits of a functioning panel is what it unlocks for people who aren't researchers. Paired with other ReOps infrastructure like guardrails, templates, and guides, panels allow product managers and engineers to run their own studies without sitting on a research roadmap or waiting for UXR capacity.
As Rebecca Okoroji put it:
There's no way we can run the studies for all of our stakeholders. So what we try to do is enable them to talk to customers or users themselves. The panel was meant to be broad, available, and people can self-serve.
Jen Cardey
Jen inherited a panel living on a Google Sheet: roughly 2,500 contacts, manually managed, and hard to scale. She migrated it into a panel management tool and then launched "Research Lite," a self-service program that opened panel access to engineers, designers, and PMs across the product org.
For Jen's team, the reaction from stakeholders was immediate: "We can just come to you, get a research turnaround in a couple of weeks. It's so much faster than we ever expected."
Quality, depth, and longitudinal potential
Panels can improve more than speed. Recruiting from a known customer base means participants are already familiar with the product, company, or testing process, which reduces onboarding friction and improves the quality of the conversation.
On progressive profile building as the core advantage of a panel:
Deep profiling is the real beauty of panels. I can aggregate all of the information we've ever gotten from this user: their basic screener, what research they've participated in, everything.
That means when research calls for feedback from specific segments, such as those with more or less product familiarity or heavy use of a specific feature, she can connect with customers whose experiences and characteristics align with the needs of the study.
For teams doing longitudinal work, panels are often the only viable option. One ReOps lead at a bioscience organization manages a participant tracker of clinical specialists, a global population of roughly 200 to 300 people, using year-long consent and automated scheduling to protect a genuinely finite resource. Because their research depends on repeated engagement with the same population over time, maintaining a panel is less a convenience than a necessity.
The practices of panel management also lend themselves to small longitudinal cohorts. Rachel Wigen-Toccalino, Staff UXR Program Manager in healthcare, ran six-month engagements with cohorts of 8 to 10 people to track how user experience evolved as products were iterated. Built-in consent forms, processes for mass outreach, and tracking who has participated recently versus who hasn't let her cleanly refresh her group for each study.
Arya Guinney
Arya built her panel using a tool already included in her organization's existing contract. The motivation was straightforward: previous research was "inherently anonymous." The team had tracked customer sentiment scores but had no way to connect them to actual behavior or follow up with the same customers over time.
The panel solved for the "why," enabling the team to engage customers longitudinally and capture video reactions to new concepts. "We wouldn't be able to tie that to actual behavior and purchase history before. Now we can stack what someone says against what they've actually done."
Cost
DIY recruiting (versus a third-party panel) is often perceived as the budget-friendly choice. But ad hoc recruiting is rarely cheap once you account for labor. User Interviews breaks it down: a mid-career professional earning roughly $73 an hour, manually recruiting 20 B2B participants, costs an estimated $4,831 in labor alone. A panel reduces that to around $870 and saves 63 hours of work.
At scale, the gap widens. For teams recruiting 100 qualitative participants per month, panel-based approaches cost between $5,580 and $16,452 less than ad hoc methods. Beyond labor and time, panels eliminate the procurement drag that makes research irrelevant by the time it's complete. As Prama Ayalasomayajula, UX Researcher for a B2B CRM, noted, traditional vendor procurement can take 60 to 90 days, a timeline that doesn't serve anyone.
Ted Kendall
Ted was running research for a CPG team with a limited annual budget, priced out of the large studies his counterparts were commissioning for upwards of $80,000. By building an internal panel, and making it feel human with consistent communication and a familiar face behind every email, he brought per-survey costs down to roughly $1,200 and cut turnaround from the industry standard of four weeks to eleven days, brief to final report.
Response rates hit 50 to 75 percent, largely because Ted consistently closed the loop: participants could see exactly how their input changed the product.
Diversity and hard-to-reach audiences
Ideally, panels give researchers deliberate control over whose voices they hear. Rather than relying on whoever responds to a generic recruitment post, panel managers can intentionally recruit underrepresented groups, target by behavior or geography, and avoid over-indexing on the loudest or most engaged voices. For niche professional audiences such as developers, C-suite executives, or clinical specialists, a pre-vetted panel can be especially valuable.
Katie Encabo
Katie managed the build-out of an opt-in research panel for a regional government initiative operating across multiple counties. Their goal wasn't speed or cost savings, it was representation. "Their purpose was inclusivity and giving constituents an opportunity to participate in government decisions."
The panel was designed to be as open and accessible as possible: local events, intercept surveys at venues like the zoo, grassroots outreach including billboards and table tents. The value proposition wasn't cash, it was civic voice. The panel took two to three years to reach a scale where the data could be trusted, but the payoff was a platform that made representation a structural feature of the research process, not an afterthought.
PII, compliance, and legal drivers
For many researchers, a panel isn't just operationally useful. It can also provide structure for managing consent and participant data responsibly. Spreadsheets become difficult to manage as requirements around opt-outs, consent records, deletion requests, and participant data grow more complex. In regulated industries, the risk of non-compliance is a direct cost.
Making the case for her panel tool by pointing to the financial risk of non-compliance:
Spending a little money on a proper tool now saves a ton compared to regulatory scrutiny later.
In B2B environments, formal opt-in panels can also provide clearer processes for documenting consent and establishing how and when researchers are permitted to contact users.
Shri Amarnath
Shri collaborated with legal from the very beginning to establish formalized terms and conditions for their branded panel, the Dayforce Research Group. Because their data processing agreements strictly limited direct contact with certain end users, these early conversations established clear guardrails for what they could and couldn't do. The legal team mandated that no individual be contacted more than four times a year, a rule Shri programmed into their panel tool (Ethnio) to automate compliance.
"Those initial conversations that we had with the legal team to establish formalized terms and conditions really helped us set up guardrails."
When not to build a panel
Panels aren't the right answer for every organization. Several practitioners were direct about the conditions that make them a poor fit: no existing customer base, or research demand too low to justify the investment.
"If people don't even value ResearchOps, that's a very, very hard start."
"Owning is an expense. If this isn't your forte, is it worth making it your forte? Can you keep it going for more than six months?"
The failure mode most often described isn't a bad launch, it's a quiet fade: a panel that gets built, has a short run of success, then goes silent and loses members before it ever proves its sustained value.
When to choose which strategy
Build if
You have the operational capacity to manage the database, and either conduct frequent, iterative research with your own customer base or need consistent access to specific audiences (like your competitors' customers or niche power users).
Buy if
You have one-off research needs, lack sufficient staffing to operate the panel, lack the processes to adequately handle customer data, or need to reach a broad, representative consumer base outside your current ecosystem.
Build vs. buy
Standing up an in-house participant panel, or outsourcing recruitment. Where each path pays off, at a glance.
While the decision to build is a single moment, a good setup can assure the panel earns its keep for years. In the next piece, we'll walk through how to set up a panel built to last: the stakeholders to involve early, the tooling decisions to make, the recruitment criteria worth capturing on day one, and where to find your first participants.
Part three
Setting up your research panel.
A panel is a lifecycle, not a thing
A participant panel is easy to picture as a thing: a tool, a list, or a group of people who answer your surveys. It's more useful to picture it as a lifecycle. Where you are in that lifecycle determines what you should be working on right now.
We think of setup in four phases.
Decide
Do you need a panel at all, and does it make more sense to build one or buy access? That's the ground part two covers.
Advocate
Make the case. Secure the mandate, the budget, and the leadership support needed to launch a panel.
Set up
Turn approval into a working panel: the right stakeholders at the table, the right tooling for your scale, clear recruitment criteria, and your first participants.
Sustain
Keep the panel healthy so it keeps delivering value year after year instead of quietly fading. That's part four.
This article focuses on the third phase. It picks up where the previous article leaves off: you have approval, resources, and a mandate. Now it's time to set up the panel you were funded to create.
Stakeholders appear in both the advocacy and setup phases, which can make it seem like we're covering the same ground twice. We're not. Advocacy is about persuasion: convincing leadership that a panel is worth funding. Setup is about execution: coordinating with legal on consent and governance, with sales and customer success to protect client relationships, and with marketing to ensure your first recruitment campaign doesn't collide with a major launch.
No, advocacy doesn't end the moment the budget clears. You'll keep re-earning buy-in long after. But you have to start building somewhere. This is where.
Who to involve before you build anything
Setting up a participant panel is not a solo project. The practitioners who have done it well are consistent on this point: the biggest mistakes happen when someone tries to build in isolation and ends up asking for favors rather than collaborating on a shared resource.
Getting the right people involved early, and being clear about what you need from each, is as much a part of setup as choosing your tool or writing your first recruitment email. A RACI framework maps this cleanly.
| Role | Who | What they own |
|---|---|---|
| Responsible | ReOps lead; researchers on small teams | Day-to-day build: tooling, recruitment, communications, tracking |
| Accountable | Director of Research, Head of Insights | Budget, mandate, final sign-off on strategy |
| Consulted | Legal, IT, Marketing/CRM, Sales/CSMs, Finance | Permissions, compliance, coordination, incentive logistics |
| Informed | PMs, designers, customer support, account management | That the panel exists, how to access it, what it can produce |
Research Operations and researchers
In mature organizations, a ReOps lead owns the infrastructure build: tool selection, recruitment workflows, incentive administration, communication templates. In smaller teams, a researcher may carry it alone. Either way, someone must be explicitly accountable before a single recruitment email goes out.
Content design
If your organization has content designers, involve them early. The voice and tone of recruitment emails, landing pages, consent language, and participant communications shape expectations from the very first interaction.
Management
Someone with organizational authority needs to champion the effort. Without executive support, budget approvals become "pulling teeth" and every cross-functional request turns into a negotiation. Secure buy-in before you need it.
Legal and compliance
Not because they slow things down, but because the guardrails they establish shape everything from consent and data retention to PII handling. "It was helpful to know what not to do in order to know what we should do starting out."
Marketing and CRM
Easy to overlook until you've scheduled a recruitment campaign that conflicts with a product launch. Partner early to coordinate communications, avoid customer fatigue, and gain access to existing CRM expertise and channels.
Product, design, and customer support
They don't need to help build the panel, but they need to understand what it is and how to use it. Support teams are often the first to hear from participants checking whether a recruitment email is legitimate. A simple internal briefing prevents confusion.
Sales and customer success
In B2B, they own the customer relationship and can either facilitate access or effectively block it. Involve them early so they understand how participants will be approached, what safeguards are in place, and how the panel benefits both customers and the business.
Orrin Ward
Orrin's team was launching their panel when they realized they had underestimated how protective the sales team would be of customer access. Researchers found themselves repeatedly blocked from contacting users directly.
"We pivoted halfway through and realized we needed to build a better relationship with commercial, build trust with them so that we don't have to keep fighting to be able to talk to our users." The team restructured to include Sales and Customer Success as partners in customer communications about the panel, not gatekeepers to route around. Response rates improved. So did the internal reputation of the research function.
Choosing your tooling: spreadsheet, existing CRM, or dedicated platform?
The tooling question is a balancing act. Invest too early and you risk buying capabilities you don't yet need. Invest too late and you'll spend valuable time managing logistics manually that even basic tooling could have automated. Your organizational context matters a lot: is there more time or money easily available? Is it easy or hard to get new vendors through procurement? Does leadership feel that having their own toolset signals importance internally? If you end up with a long-running panel, conditions will change, so monitor for the point where it's time to make the case for a different kind of system support.
The home-grown method
Many of the professionals we talked to have used a spreadsheet at some point. For some specialist populations, spreadsheets are sufficient altogether. One ReOps lead manages a panel of 200 to 300 clinical scientists on a spreadsheet. At that scale, with that population, a dedicated tool would add overhead without adding value. The spreadsheet is the panel.
Spreadsheet as proof of concept
The scrappy tool that gets you going can be the prototype that leads to better things. The most common pattern we heard was spreadsheet-as-proof-of-concept: starting lean to demonstrate the utility of an always-on panel before advocating for tooling investment.
There's generally a natural tipping point. Once you're managing more than a few hundred contacts, tracking who's been contacted, who's been paid, and who's been over-used becomes a job in itself.
Jen Cardey
Jen made the switch at around 2,500 contacts, after managing her panel in a spreadsheet for years. The decision to migrate wasn't driven by ambition; it was driven by pain. Tracking participation, managing incentives, and maintaining data hygiene had become unsustainable.
She moved to a panel management platform, built a second B2C panel alongside the original, and launched "Research Lite," a self-service program for engineers, designers, and PMs. The shift didn't just solve the logistics problem. It changed what the panel was capable of.
Signs it's time to invest in dedicated tooling
You're over-using the same people
With no automated way to track participation frequency, your most responsive panelists quietly become overrepresented in your studies.
You're burning out the ones who respond
Too many invitations lead to survey fatigue, causing even engaged participants to disengage or leave entirely.
Compliance risk is too high
Managing opt-outs, consent records, or PII in a shared spreadsheet may be too risky for your industry or location.
Recruitment is blocking research
If scheduling, incentives, and reminders take more time than the research itself, automation is no longer a luxury. It's the path back to doing the work.
Using the existing CRM
Not every organization jumps directly from spreadsheets to a dedicated platform. For teams that already have a customer database or CRM, the next logical step may be to leverage that infrastructure first. The CRM already contains customer profiles, contact histories, segmentation data, and communication workflows. It wasn't designed for research operations, but it can often support the early stages of panel management and bridge the gap between a spreadsheet and a dedicated platform.
| Advantages | Disadvantages |
|---|---|
| Less duplication of PII. Customer data already in the CRM reduces the need to govern a separate participant database. | You're a small fish in a big pond. It's hard to get features or changes when the system is optimized for larger, better-funded parts of the organization. |
| No new vendor. Vendor selection, procurement, and onboarding can be lengthy. The CRM is already in place. | Keeping a bright line between research and marketing. For anti-spam compliance, participant trust, and expectation management, clear separation helps. |
| Leverages existing investments. You're getting more value from technology the organization already owns and supports. | Systems can be complex. Without dedicated support or customization, CRMs can be difficult to learn, navigate, and adapt to research needs. |
Specialized panel management systems
For other teams, the risks and downsides of the spreadsheet convinced them to invest in tooling early. To understand if your context calls for specialized tooling, evaluate these upsides.
- Better coordination with your Sales or Marketing CRM. Spreadsheets don't talk to your CRM, which means you might inadvertently send a survey invite to a customer mid-contract-renewal.
- Tooling can enforce a cooldown period. With manual management, enthusiastic participants end up dominating your pool. Most panel systems have cooldowns to prevent over-engaging participants.
- Designed with compliance in mind. Right-to-be-forgotten requests and PII protection stay invisible until legal gets involved. Dedicated platforms make consent, deletion, and PII management easier to administer consistently.
Whether you choose a spreadsheet, an existing CRM, or a dedicated platform, the technology is ultimately a supporting decision. The bigger determinant of success is whether your panel contains the participants you'll need six months from now, not just the participants who are easiest to recruit today.
Build your panel success criteria
Before the first recruitment email goes out, you need a clear answer to a question most teams skip: who, exactly, is this panel for? Teams that skip this step build panels that work for the first few studies and quietly fail when a stakeholder needs a segment that was never recruited for.
Start with your research agenda
The most common mistake in panel planning is starting with whoever is easiest to reach and working backward to justify the composition. Consider a 12-month snapshot of the research you expect to run. Sketch enough of a picture to ask: what segments will we need to hear from, and how often? That question surfaces your panel's size and segment requirements faster than any tool selection or recruitment channel decision will.
A team running monthly pulse surveys needs a panel large enough to sustain repeated outreach without burning participants out. A team doing longitudinal qualitative work may only need eight to ten deeply engaged people.
Joanne Van Vranken
Joanne had a B2B panel that peaked at 31 members and was ultimately judged a failure. Not because 31 is inherently too small, but because the organization needed statistical analysis and the panel couldn't support it. The failure wasn't in the recruitment. It was in the mismatch between what the panel was built for and what it was eventually asked to do.
Define your segments
One of the beauties of having your own panel is being able to talk to specific subsets of users based on your research needs. To do that, the panel needs relevant data to understand who is available. But keeping the initial sign-up form short means being selective about what you ask up front versus what you collect through profiling surveys over time. Our experts were opinionated on what to capture on day one.
B2B: role, seniority, company size, industry, tier
Typically non-negotiable. Agustina Di Clemente aligned her segments directly with quarterly research priorities, including market size, company size, and user behavior, and reviewed them each quarter as priorities shifted.
Government: geography and demographics
Arun Upadhyay built quotas into his panel from launch, matching census data for age and gender so results could be trusted to reflect the actual population.
B2C: tenure and product use
Power users often need to be studied separately from recently onboarded users.
Everyone: participation metadata
Date of last contact, study participation history, and notes about past contributions. Skip this and you risk re-screening people you've already spoken with, or repeatedly drawing on your most enthusiastic respondents without realizing it.
Tanya Branitska, who built a developer panel, on what to ask first:
The number one question was, what's their subscription tier? What do they do? Because the research often is dependent on that section of the business.
What practitioners wish they'd tracked earlier
The most consistent regret across practitioners was what they hadn't captured about participants early on.
Recruitment source
Karen Bills wished she'd tagged every participant with their original source. As satellite communities merged into the main panel, she lost the ability to distinguish "gen pop" from "premium" participants. "Design for the next ask, not just the immediate need."
Incentive preference
Arya Guinney built an incentive preference question into her screener from the start and called it one of her best early decisions. Knowing whether participants wanted branded gift cards or neutral rewards stretched the budget while supporting response rates.
Behavioral personas over job titles
"IT Admin" and "Marketer" mean different things at different companies. Teams that captured capabilities and tasks, what people actually do day to day, found those more durable for targeting than titles.
Verification signals
With AI-generated survey responses creating new quality concerns, several practitioners wished they'd collected LinkedIn URLs or other verification markers at sign-up. It's much harder retroactively.
Account health in B2B
Integrating CRM data early, or at minimum flagging participants by relationship status, prevents sending a research invitation to a customer in a tense contract renewal. It doesn't feel urgent until it suddenly is.
How big does my panel need to be?
We are often asked how large a panel needs to be to become successful, or even "worth it." What we learned is that panel size is better treated as a calculation than a target. A basic starting point:
+ 10–20% buffer for attrition and non-response
This is a starting estimate. Your actual needs will vary based on how often participants can take part, how narrowly studies are targeted, and how much participant overlap exists between studies. Modelling panel size can get as elaborate as you want. But size isn't everything.
Engagement beats scale.
It doesn't tell me any story if I just tell you that I have a panel of 10k users if they're not engaged. If I have a 1k panel with very engaged people, that will give you better performance.
Manageability sets a real ceiling. A panel is only as useful as your ability to manage it. The right size is one your team can recruit, maintain, segment, communicate with, and learn from consistently.
Try it: use AI to build a panel size calculator
Use this prompt with an AI coding tool to explore how panel size, response rates, research demand, and participation limits interact.
Create a single-file, local-only HTML web app for simulating participant panel size. Include two primary modes:
- Panel capacity: the user enters an existing panel size and sees what combination of studies the panel can support.
- Panel planning: the user defines the studies they want to run and receives an estimate of the panel size required.
Allow users to enter study types, desired completes per study, expected response rates, studies per month, participant eligibility rates, maximum participation frequency, attrition rates, and a planning buffer. Show the calculations and assumptions clearly, flag combinations that could overuse participants, and allow users to adjust inputs to compare scenarios. Keep all data and processing local to the browser.
Start recruiting
Once your team is bought in, your tooling selected, and the recruitment criteria identified, it's time to recruit your panelists. The advice from practitioners was consistent: cold outreach to unfamiliar audiences should be a last resort, not a starting point. Begin with the warm channels already available to you.
Start with warm channels
Internal CRM databases
Consistently cited as the strongest first wave. Jen Cardey tapped her existing customer database and reached 7,000 sign-ups within one to two months. The advantage isn't just reach, but relevance.
Past research participants
Agustina found that re-engaging people who had participated over the previous three years was "one of the initiatives that performed really well." These are people who have already said yes to research once.
Marketing and product touchpoints
In-product recruitment, customer communications, and email updates put the invitation in front of people who already have some connection to the product or brand.
Across accounts, warm channels offered compelling examples of both speed and quality. One team using Slack and email received 70 percent of its responses within an hour. Others found that people recruited through warm channels provided richer feedback, in part because they were invested in improving tools they already used.
Avoid generic lists
An existing list isn't necessarily the right list. Avinash Mangar discovered this managing a WWE panel, where merchandise purchaser lists included parents and relatives buying gifts, not necessarily the engaged fans the research needed. "Reaching out through our engaged CRM base was much better." Availability is no substitute for relevance.
Consider niche communities
When standard channels fall short, consider where specialized populations already gather and how their qualifications can be verified.
Douglas Wicks
Douglas needed licensed hairstylists for a study, a population consumer panels couldn't reliably deliver. Initial panel responses were "bogus" and required extensive sifting. His solution: purchase a specialized trade magazine subscriber list, then validate participants against state licensing records. The list was expensive. The validation was manual. But it gave him the qualified population he needed, and the resulting panel became a resource for future studies with the same audience.
Reach skeptical audiences in person
For audiences skeptical of research, such as fraud investigators, clinical specialists, and regulated professionals, personal credibility can matter more than another recruitment email. Jess Ivins, Senior UX Researcher in enterprise software, found that cold emails to customers produced "crickets."
What worked was going on-site, meeting people face to face, and letting them see who was asking and why.
I realized I have to go on-site and build face-to-face relationships with these customers so they know who I am.
Get creative for harder-to-find audiences
For hard-to-reach demographics, traditional channels may be tough. Joe Jordan, President of Elliam, Inc., described one company that built a panel of teenagers ages 14 to 17 whose parents had already provided standing consent, making it easier to recruit from that population for future studies.
The through-line is simple: recruit with the audience in mind. That might mean working through an account manager, recruiting at a conference booth, partnering with a community organization, or relying on peer referrals. For hard-to-reach populations, the best path may look very different from the broad outreach that works elsewhere.
Building a panel is relatively easy. Building one that remains useful and engaged over time is harder. There are too many contextual factors for any single formula to guarantee success. But practitioners pointed to a consistent set of principles: work iteratively, find your allies and sponsors, address objections early, and understand what your organization needs today while planning for what it needs tomorrow.
What to do after setup
Contacting that first wave of participants is a major milestone, but don't mistake it for the finish line.
The failure mode for panels is rarely a bad launch. It's the quiet fade: the panel that opens with fanfare, runs well for a quarter or two, then slowly goes silent as participants churn, profiles go stale, and the people who championed it move on. A panel isn't a project you finish. It's a resource you keep alive.
That's where the next phase begins. In part four, we look at what it takes to keep participants engaged, profiles current, and your panel valuable long after the initial excitement of launch has faded.
Part four
Managing and maintaining a healthy panel.
Getting a panel started isn't easy, so if you've successfully set one up, congratulations and respect are in order. But keeping it healthy over time is a different kind of challenge.
Panels aren't Twinkies or forever chemicals. They are subject to entropy, and they require energy to keep functioning. The enthusiasm and collaboration that fueled the launch can fade as the reality of ongoing maintenance sets in.
This article looks at how practitioners keep their panels healthy without losing momentum: keeping participants engaged without burning them out, handling participant data responsibly, improving representation, and managing the ongoing work sustainably.
Keep participants engaged
Sustaining engagement means treating the panel not as a static database but as an ongoing relationship that requires care and feeding. When participants feel their time is being wasted or their voices aren't being heard, they quickly disengage or stop responding.
Humanize the panel to build rapport
Rachel Wigen-Toccalino worked with a team in healthcare, where showing care for participants was paramount. Her team provided a high-touch onboarding experience with an orientation and a clear schedule of weekly communications.
Ted Kendall kept engagement high by putting a human face on the panel. His wife served as the dedicated face of the program, handling communications and signing off with her name. The connection grew strong enough that participants would email her to say they were going on vacation and couldn't take a survey.
Part of the success of the panel was that personal rapport. It was a real person. It wasn't just Kraft. The participants felt important, and they felt like their feedback was being listened to.
Thriving panels put a face to the name
Among teams that met User Interviews' success threshold of 100+ sessions, 90.3% had set up a custom sender profile (versus 76.5% of other teams), 56.0% used a logo (versus 23.5%), and 76.1% used a custom theme (versus 64.7%).
More ways practitioners keep the relationship warm
Close the loop with sharebacks
Tanya Branitska uses polls that display results immediately: "instant gratification." Arya Guinney runs larger sharebacks showing participants how their input influenced the menu, reinforcing their connection to the brand.
Provide non-research value
Joanne Van Vranken noticed some segments of her tradespeople panel weren't called on often. She began sending quarterly newsletters with fun, non-business polls simply to say, "We haven't forgotten that you're here!"
Align incentives with what people value
Prama Ayalasomayajula found that giving B2B advertising professionals direct access to the people building the product was more motivating than money. Marta Paz's restaurant owners want early access: "That they will be able to test first all the main features that come out is their main incentive."
Avoid participant burnout
Keeping panelists active is the lifeblood of a healthy panel. Practitioners described several ways to prevent burnout, from managing contact frequency to reducing the burden of individual studies.
Enforce cooldowns and rotations
Jess Ivins uses her panel software's built-in tools: "We avoid that problem of asking the same people over and over again with an automatic ninety-day cooldown." Avinash Mangar's team surveyed fans up to four times a week, so they rotated who received each invitation.
Keep surveys short, cut tedious formats
Arun Upadhyay sets a 20-minute limit on online interviews for his government panel: "Otherwise it is way boring for them." Ted Kendall eliminated grid questions entirely: "We got a ten percent drop-off with the grid."
Use progressive profiling
Katie Encabo found that appending the same demographic questions to every survey added to the burden. Retain profile information so people "don't have to refill that information every time."
Target invitations precisely
Karen Bills heard from participants repeatedly invited to studies that didn't fit: "I'm a marketer, but I'm not related to campaigns." Understand your audience and target the invites accordingly.
Avoid consent drift with careful data handling
While burnout risks losing engagement over time, consent violations and poor data handling can put the panel itself at risk. Interviewees cautioned against consent drift, where changes, merges, or transfers between systems result in people being added to outreach they didn't consent to. Over time, that leads to poor data hygiene, accidental over-contacting, or outright violations.
Purge non-consenting users from data merges
Consent problems can emerge inadvertently when new data sources are connected. Jess Ivins experienced this when her data team synced its Snowflake database directly to the panel tool, RallyCRM. The integration risked pulling thousands of users into the panel without the required consent. Jess now purges non-consenting users from the platform to maintain panel integrity.
Keep consent updated by inheriting opt-out rules
Compliance isn't just about initial sign-up. It requires maintaining accurate consent and preference records over time, including when participants opt out or request deletion. Tanya Branitska suggests an automated opt-out inheritance workflow: "Set up an automated link between the panel and your native software to have that process automated."
Arya Guinney
Arya recognized that her company had separate marketing and research lists, and an opt-out in one system wasn't automatically reflected in the other. She addressed this through clear communication, ensuring participants understood exactly what they were signing up for and how different communication types were treated.
"I want to be clear from a legal perspective, but also from a user experience perspective, that these are separate things and you can rescind your opt-in at any time."
Increase and maintain healthy representation
A panel that skews toward your easiest, most enthusiastic respondents will quietly tell you a distorted story. The people who respond most readily may not reflect the full range of people you need to hear from, and that imbalance grows over time. Practitioners pointed to two habits.
Treat multicultural audiences as distinct groups, not monoliths
Avinash Mangar emphasized recognizing differences within ethnic and regional populations rather than treating them as homogeneous. "You can't treat certain ethnic or regional groups like monoliths, expecting their behaviors and preferences to be the same." In international research, he also adapts language and localization to engage different audiences.
Oversample or continuously recruit underrepresented populations
The diversity you recruit for at launch doesn't stay put. Smaller segments become underrepresented as participants leave, while the people who remain change. A participant's role, life stage, or relationship with your product can shift enough that they no longer represent the segment you recruited them for.
Someone who was a "career starter" two years ago may no longer fit that segment.
Two years later, they're not the same person anymore. And we need to backfill to make sure we still have that audience represented.
Improve efficiency with automation
Operational efficiency is what turns panel management from a reactive administrative burden into a scalable resource. Practitioners focused on reducing time to recruit, automating repetitive tasks, and moving away from scattered, manual systems, using both built-in workflows and custom automations.
Productive teams integrate
According to User Interviews internal data, highly effective teams (running more than 100 sessions) were more likely to connect Zoom (54.5% vs 45.5%) and Microsoft (26.9% vs 17.8%). This doesn't establish causation, but it suggests more productive teams integrate tools into their workflows.
Make it easy for stakeholders to say yes
Orrin Ward launched "Project Easy Peasy" so B2B account managers could review participant contact requests with a single button press to approve or reject.
Long-term consent contracts
One ResearchOps lead at a biosciences organization replaced per-session consent forms with a one-year master consent agreement administered through DocuSign, lowering the barrier for every booking.
Database integrations
Agustina Di Clemente partnered with her data team to integrate Snowflake directly into Great Question, automatically syncing panelist attributes instead of manually pulling demographic lists.
Self-serve models
Jen Cardey's "Research Lite" at TripAdvisor let PMs and designers use the panel independently, reducing reliance on the Research Ops team for every request.
Measure success
Activity is easy to measure: sessions run, emails sent, participants recruited. But activity is not the same as success. A panel is successful when it solves the problem it was built to solve, and that problem is different from team to team. Before choosing a metric, go back to the reason you built the panel in the first place.
Were you trying to shorten time to recruitment? Improve the quality of your insights? Democratize who could run research? Reduce reliance on expensive external recruiters? A growing contact count can feel like progress even if half those contacts have gone cold. The right metric distinguishes a panel that is working from one that only looks busy.
| Metric area | Reason to measure it | What to track | Benchmark |
|---|---|---|---|
| Time to data | Your goal is to speed up recruitment | Time from approval to first session filled; time to all sessions completed | Compare against your pre-panel baseline |
| Source quality and incidence | Your goal is to improve participant quality | Recruitment incidence or eligibility rate; unusable-session rate; participant-source mix | Establish your own baseline and monitor trends |
| Project success rates | Projects used to stall or fail before completion | How often studies ran under quota; how often projects were delayed or cancelled for low incidence | Compare against baseline and investigate recurring misses |
| Panel size and health | You need a healthy standing bench, especially for niche populations | Churn rate, total contacts, active/inactive, % participated, % in cooldown | User Interviews puts median contacts among thriving teams at ~3,200 |
| Research access and utilization | Your goal is to increase access to research | Studies run by non-researchers; number or share of eligible teams using the panel | Compare against baseline or adoption target |
| Cost efficiency | Your goal is to reduce reliance on external recruiting | External recruiting spend; cost per recruited participant or study | Compare against your pre-panel baseline |
Metrics can't tell you exactly what to do next, but they give you a place to start forming hypotheses and looking for the story underneath. Choose the one or two measures that map most directly to why your panel exists, then use them consistently.
When to shut down a panel
Even after employing the tactics above, panels can still fail due to supply, demand, organizational, or strategic factors. Knowing when the underlying conditions have changed is just as important as knowing how to keep a panel going.
Lack of internal buy-in
Ted Kendall described an initiative at a previous company killed simply because "the VP of marketing didn't like panels, and she was very strong in her opinions."
Low engagement and wasted effort
Joanne Van Vranken's panel was disbanded after two years. "It really hasn't become what we had hoped it would become." Part of the problem: "We never were actually able to communicate to the firm as a whole what the panel was actually for."
Shifting priorities, no dedicated time
Weiyan Chee's panel "wittled away" because "all these different priorities took up most of my time." Mirjam De Klepper saw something similar when the broader project changed direction.
Layoffs and strategic pivots
Emily Wever's panel ended overnight when "the research team was eliminated at the company," with "maybe eighteen hours between the email and the layoff the next morning."
Planned ephemerality
Not every panel is meant to last forever. Rachel Wigen-Toccalino structures hers to wrap up after a defined period; her team hasn't "extended it beyond six months."
The panel is never finished
Deciding whether to build or buy, making the case for the investment, setting the panel up, and keeping it alive are not four separate projects. They're parts of one continuous commitment to the people who help shape your product.
So if you're staring down the maintenance phase and feeling the momentum slip, that's not necessarily a sign you've failed. It's the normal physics of a panel. Panels are subject to entropy. Keeping one healthy is the price of having a standing bench of real users ready to answer your hardest questions when you need them.
Very few research assets pay off like that. Almost none of them run themselves.
Back to the start
1The realities of panels