Use cases
Same evidence. Four very different Mondays.
A product manager needs proof for planning. A researcher needs a study that doesn’t fall apart. Customer success needs to be heard. A founder needs the pattern. Here’s how each of them works in Parley.
A week in the life
Pick a role. Compare the week before and with Parley.
Ana Ruiz, Fernhill
Product manager, payroll imports · Payroll for small businesses
Has to argue for an import rebuild in quarterly planning — against four other priorities.
Mon
Searches “import” across every study: 34 highlights from 11 people.
Tue
Embeds the live theme card in the Import v2 spec.
Wed
Cuts a two-minute clip reel from four different calls.
Thu
Planning agrees quickly. The theme is linked to issue FERN-412.
Fri
New import tickets land in the same theme, ready to confirm.
Illustrative scenario with fictional people and companies.
Product managers
Walk into planning with the evidence already attached.
Ana Ruiz · Product manager, payroll importsFernhill — Payroll for small businesses (fictional)
Has to argue for an import rebuild in quarterly planning — against four other priorities.
- 1
Search before writing
One search across interviews, tickets and surveys shows how big the import problem really is.
- 2
Rank by people, not noise
Each roadmap candidate carries the number of participants behind it.
- 3
Show, don’t summarise
A short clip reel plays in the meeting instead of a paraphrase.
What changedThe rebuild was agreed in one planning session, and the issue keeps collecting evidence as new tickets arrive.
| Candidate | People asking (of 14) | Issue |
|---|---|---|
| Import v2Import breaks on real-world spreadsheets | 11 | FERN-412Proposed |
| Clearer contractor pricingPlan limits are unclear | 6 | FERN-398Proposed |
| Change summary before approvalShow me what changed | 5 | FERN-421Discovery |
| Mobile approvalsMobile approvals beta | 4 | FERN-377In beta |
UX researchers
Run a whole study without losing a thread.
Sam Whitlock · Lead researcherNorthbay — Property-management software (fictional)
Running a 12-interview study on tenant maintenance requests in three weeks, alone.
Week 1
Recruit & schedule
Participants, segments and consent captured before the first call.
Week 2
Interview & highlight
Calls transcribed within the hour; highlights made the same day.
Week 3
Synthesise & publish
Theme board, report and clip reel — searchable by the whole company.
| Participant | Session | Consent | Status |
|---|---|---|---|
| Rosa P.Landlord · 14 units | Oct 6 | Recorded | Synthesised |
| Tom A.Tenant | Oct 7 | Recorded | Synthesised |
| Gwen L.Property manager · 220 units | Oct 8 | Recorded | Highlighted |
| Idris B.Maintenance contractor | Oct 9 | Recorded | Transcribed |
| Elena S.Tenant | Oct 13 | Recorded | Scheduled |
| Kofi D.Landlord · 3 units | Oct 14 | Pending | Awaiting consent |
What changedThe study finished on schedule, and six months later a designer found Rosa’s clip about repeat repair visits by searching “contractor”.
How highlighting works| Theme | Single clinic | 2–5 sites | 6+ sites |
|---|---|---|---|
| Calendars don’t sync across sites | 1 | 7 | 9 |
| Reminder texts sent twice | 5 | 4 | 2 |
| Reports can’t be exported | 2 | 3 | 6 |
| Hygienist shifts are rigid | 4 | 3 | 1 |
Darker cells mean more accounts raised it.
Customer success
Turn renewal calls into themes product can’t ignore.
Joel Mensah · Head of customer successBrightwater — Scheduling for dental clinics (fictional)
Hears the same complaint on renewal calls but can’t get it onto the product roadmap.
- 1
Collect without extra work
Renewal calls and tagged tickets go straight into a shared retention study.
- 2
Attach the account
CRM fields like plan and number of sites travel with every highlight.
- 3
Answer “how many?”
Filter a theme by segment to show exactly who is affected.
What changedThe sync problem turned out to be concentrated in clinics with six or more sites — enough to move it up the roadmap.
Founders
Find the pattern before you build the product.
Thirty discovery calls in, trying to tell a pattern from the loudest prospect.
Patterns after 30 calls
- Listing surplus stock takes too long18 / 30
- Buyers want invoices per lot, not per order12 / 30
- Payout timing decides whether sellers trust us9 / 30
- A native mobile app— the loudest request4 / 30
“The loudest prospect wanted an app. Eighteen of thirty wanted listing to be faster.”
Mira Chen · Co-founderOddlot — A marketplace for surplus stock, 9 people (fictional)
Starter is free for one editor. When a co-founder starts tagging too, the Team plan gives both of you editor seats and a shared taxonomy.
Whichever Monday is yours, start with one study.
Pick the role closest to yours, connect one source, and invite the people who make decisions as free viewers.