Getting Started
Run async user tests and get actionable feedback in hours, not weeks.
What This App Does
This app helps you run asynchronous user tests. Instead of scheduling live calls with testers, you:
- Create a test with tasks for users to complete
- Share a link with testers
- Testers record themselves completing tasks on their own time
- Review recordings and transcripts when they're ready
Why async testing works:
- Natural environment — Testers participate from their usual context
- No scheduling conflicts — Works across any time zone
- More honest feedback — No facilitator watching live
- Faster turnaround — No coordinating live sessions
Your First Test in 5 Minutes
1Create Your Test
Click “New Test” from your dashboard. You'll need a test name, product URL, and a brief context (1-2 sentences about what you're testing).
2Add Tasks
Tasks are specific things you want testers to attempt. Good tasks start with an action verb, have a clear endpoint, and take 1-3 minutes each.
Example tasks:
- “Find the pricing page and tell us what tier fits your needs”
- “Sign up for a free account and complete your profile”
- “Try to export your data as a CSV file”
Aim for 3-5 tasks per test. More than 7 leads to fatigue.
3Share Your Link
Each test gets a unique share link. Send it to:
- • Friends and family (for quick informal feedback)
- • Beta users from your waitlist
- • Potential customers from your target audience
- • People from relevant communities
4Review Results
As testers complete sessions, you'll see video recordings, audio transcripts, and timestamps for each task. Watch recordings to see what they did. Read transcripts to understand what they thought.
Quick Tips for Better Results
Finding Testers
- • Start with 5 people — You'll find 80% of major issues
- • Match your audience — Someone's neighbor isn't always the right tester
- • Offer small incentives — $10-20 gift cards or free product access
Setting Context
Include a short intro that tells testers what the product does, that they should think aloud as they go, and that there are no wrong answers — you're testing the product, not them.
Avoiding Bias
- • Don't hint at the “right” answer in your task descriptions
- • Use neutral language (“Try to...” not “You should be able to...”)
- • Don't apologize for bugs before they find them
How Many Testers Do You Need?
| Goal | Testers Needed |
|---|---|
| Find obvious usability issues | 3-5 |
| Validate a major change | 5-7 |
| Statistical confidence | 15-20+ |
For most indie builders and early-stage teams, 5 testers is the sweet spot. You'll uncover the majority of problems without spending weeks on recruitment.
What's Next?
After completing your first test:
- Analyze with AI — Use our prompts to extract insights from transcripts
- Prioritize fixes — Focus on issues multiple testers hit
- Iterate — Run another test after making changes