Use case · Onboarding
Find out where new users get stuck, while they can still tell you.
ProductSignal interviews new users in their first week, while every step is still fresh. You get what they said on one page, tied to who said it.
ForProduct leadsGrowthProduct designers
Interview #41
05:18 · text · day 6 after signup
AI
You signed up six days ago. What were you hoping to have done by now?
Priya
Have my team in it. I invited them, but there was nothing to show them yet.
AI · follow-up
What would have made the first screen worth sharing?
Priya
One real board with our own feedback in it. Even half full, I’d have sent the link.
Evidence
212 interviews · 14 days
I didn’t know which template to pick, so I didn’t pick one.
We had to wait for IT to connect our data. That took the whole week.
The invite went to spam. My team thought I never sent it.
Nobody planned a question about templates. People brought it up anyway.
One onboarding study, two weeks in. One conversation on the left, the evidence from the other 211 on the right.Every quote links back to its interview
Runs on day six
Connect Segment or your own product events. ProductSignal reaches out when a new account goes quiet, or on the day you pick, by email or in-app.
Priya S. · Trial
signed up Mon 10:14
Account created · Segment
Mon 10:14
Invite sent · in-app
Sun 09:00
Interview started · text
Sun 11:26
Added to the topic
05:18 in
Day 6 after signup · first-week study
It asks if they got what they came for
The interview reads what a new user already told you in your other tools, and picks up from there instead of starting over.
Interview #41 · Priya
03:27
Context · welcome survey · day 1
“Mostly I want to see where our feedback piles up.”
AI
On your first day you said you wanted to see where your feedback piles up. Did you get that far?
Priya
Not really. The import needed our admin, and she was out all week.
Added to the topic · First week
The questions
Three openers. The rest is listening.
You can edit them, add your own, or leave them as they are. Most teams leave them.
- Opener 01What were you hoping to have done by now?Follows up on what got in the way, and where they stopped.
- Opener 02What did you do right after you signed up?Walks through the first session step by step. The sticking point is usually in the middle.
- Opener 03Who else needed to be in it for it to work?Finds the teammates, admins and approvals that slow a first week down.
- Add your own opener
Halcyon · first-week activation
“Half our new teams said the same sentence about the first screen. We rebuilt it around that sentence.”
212
interviews in the first two weeks
+23%
teams active by day seven, one quarter after the new first screen
Other use cases
Same loop, different question.
Why they left · evidence
128 interviews
Sarah K.· Team plan
“I opened it the next day and it was empty. I didn’t know what I was supposed to do next.”
Tomás R.· Starter
“My teammates never joined. I was the only one using it.”
Jonas W.· Team plan
“The price made sense once it worked. It just never got there for us.”
Every quote links to the person who said it
Churn
Why people leave, from the people who left. Interviews start the week they cancel.
See use case →Would you use it? · evidence
64 interviews
Elena M.· Ferro
“Only if it goes straight into Jira. The spreadsheet was only ever the middle step.”
Marcus K.· Tessel
“It would replace the spreadsheet we rebuild every quarter.”
Priya S.· Arbor
“Honestly, not a priority right now. We export twice a year.”
Jira was never in the spec
Discovery
Whether a thing is worth building, before you build it.
See use case →