access / buying guide

Testing with your own users: what the software fee leaves out

Bringing your own participants can remove a panel-recruitment purchase. It does not remove the need to define the task, arrange access, make a fair invitation and interpret the evidence. Keep those responsibilities visible when comparing free and paid software routes.

Documentation checked 2026-09-19 · Vendor claims are not hands-on results.

Vendor links in this edition are direct links. No paid placements are included. Comparisons describe published documentation, not hands-on test results. Commercial disclosure

Count sessions and responses—not customer-list size

The size of your customer list does not equal completed research participation. Start with the number of sessions your team intends to run and the output it needs. Keep invited, started, completed and usable sessions separate in your internal notes. Those distinctions prevent an invitation campaign from looking like a completed research study.

Useberry’s cited response limit applies to its own-audience share-link collection rather than its paid pool. Userbrain documents a renewing own-user session allowance with no own-user rollover. Neither rule means you can collect unlimited own-user evidence just because a shareable link exists. [S33] [S11]

Write an honest, low-pressure invitation

Name the purpose, expected activity and time, any recording, the offered incentive, and a practical way to decline. Avoid implying that participation affects support, employment or access to something a person already purchased. This is our operational recommendation, not a complete legal template for every country.

Use a demo environment when the task does not require actual account data. Do not place customer passwords, card numbers or sensitive records into a general usability exercise. The separate software and recruitment supplier terms still apply to the session.

Useberry documents a share-link route for paid-plan interviews. Userbrain documents inviting participants to a task-based Figma test. Those links do not produce identical evidence, and an interview scheduling route should not be counted as an unattended response allowance. [S07] [S10]

Preview the invitation and task outside the author’s account. A link that works for a team member may require a login or expose material that the intended participant should not see. The setup check is about the actual participant route, not just whether a button exists in the study editor.

Do not confuse familiar people with the target audience

An existing user can be ideal for a repeat-use or account-management question. They may be unsuitable for a first-impression question intended for people unfamiliar with the product. Write the relevant experience requirement before recruiting. Do not describe friends, colleagues or current users as representative of a wider population without evidence.

The same restraint applies to sample size. This site does not promise that five, ten or twenty people establish a universal result. A small qualitative study and a quantitative comparison require different reasoning; the number alone does not determine what can be concluded.

Budget the work that remains

In the budget calculator, put independently paid incentives in their own field and add planned coordination/review time separately. A zero software charge can coexist with meaningful research cost. Conversely, a quoted panel fee may already include incentives, so do not use the own-user budget unchanged for a recruited audience.

For a small included software route, read the free-plan comparison. For live sessions versus recordings, use the method guide. The next action should follow the evidence you need, not the attractiveness of a free-account headline.

Sources for this page

  1. S07 · Useberry: own participants for interviews
  2. S10 · Userbrain: Figma testing
  3. S11 · Userbrain: subscription operation
  4. S33 · Useberry: response limits