For PMs and product designers who own onboarding in a SaaS, and have no researcher to call on

You know where users quit your onboarding. Disco talks to them and asks why.

Describe what you want to learn, send one link to your recent sign-ups, and Disco runs a short voice interview with each of them: it asks your questions, follows up on what they say, and hands you the transcripts, a summary and the themes across interviews. No calls to book. English or French.

Create a discovery interviewTry an interview
Voice interview · scripted example
0:00 / 0:14

  1. Disco · question

    You mentioned you connected Slack and then stopped. What were you expecting to happen right after that?

  2. Participant · example answer

    That it would pull in our channels. It just sat there.

  3. Disco · follow-up

    So nothing showed it was working. What did you do next: wait, retry, or leave?

Scripted example in Disco's production voice. In a real interview the participant answers out loud and Disco chooses the next question from what they said.

Why studies don't happen

Nobody skips user research for lack of interest. They skip it because setting it up costs too much, in money or in calendar.

We read 81 G2 reviews across 14 interview, testing and research tools before writing this page. Two of them, both from people at small companies, put the problem plainly:

  • I've skipped running some studies because I couldn't justify the cost to my manager.

    Customer Insights Analyst, small business
    Reviewing Respondent on G2

  • The available templates sometimes feel at bit too opinionated, while a blank project obviously leaves me with all the power to mess it up on my own.

    Product Manager, small business
    Reviewing Dovetail on G2

  • A director of experience design describes research that simply stopped happening because the logistics got in the way.

    Director of Experience Design
    Reviewing Strella on G2

That is how studies die: a panel you can't justify, a blank page you don't have time for, calendars that never line up. Disco skips all three: your own users, a draft guide you edit, and an interview that happens whenever each user has a few minutes.

How it works

From a question to answers you can quote

Keep learning between live user calls, without adding more meetings to your week.

[1]

Say what you want to learn

“Why do people stop before their first import?” Disco drafts a short interview guide from that. Edit it. Then publish, open your own link and take the interview yourself before you share it.

[2]

Send one link

Email, Slack, in-app. Your users see who is asking, how long it takes, and that it is recorded. They talk when it suits them, in English or French.

[3]

Disco runs the conversation

It asks your questions out loud and follows up on what people actually say, within the time limit you set, from 5 to 30 minutes.

[4]

Read them in their own words

Full transcript per interview, a summary, and the themes across interviews. Check any theme against the transcripts before you act on it.

Create a discovery interview

Who it's for

Built for one job: the activation study you don't have a researcher for

For you if

  • You're a PM or product designer who owns onboarding or activation in a SaaS.
  • You have a list of recent sign-ups you're allowed to contact.
  • A decision is coming: a drop in activation, a step people abandon, a feature nobody adopts, an A/B test you can't explain.
  • Your current plan is “send a survey” or “book a few calls when things calm down.”

Not for you (yet)

  • You have no users to interview. Disco doesn't recruit participants.
  • You need panels, screen recording, quotas or a research repository. Keep that tooling; Disco doesn't replace it.
  • You're interviewing people for a job opening. Different job, different tool.

Two questions it answers well

Two studies you can run this month

One question, one link, one set of answers. Each card shows the kind of output you get back, labelled as an example.

Onboarding drop-off

Understand onboarding dropoff

Ask the people who signed up last month and never came back where they stopped and what they expected.

Create a discovery interview

Key themes

Example output

  • The import felt like a restart, not a resume

    I thought it would pick up where it stopped. It started over and I had to map the channels again.

  • No signal that the import had finished

    I waited for something to tell me it was done. Nothing came.

  • Wanted to involve the team before configuring

    I did not want to set the rules alone and then redo them with my team.
Example output. Each theme is a starting point; the transcripts hold the evidence.

Unused feature

Learn why features go unused

Talk to users who tried it once. Find out what they thought it was for.

Create a discovery interview

Key themes

Example output

  • The feature disappeared after first use

    I used it once, then never found my way back to it.

  • Assumed it was meant for admins

    It looked like a setting, not something I should use every day.

  • No reason to come back to it

    Nothing brought it back at the moment I actually needed it.
Example output. Talk to the users who tried once and stopped, the ones you would not have booked a call with.

What Disco is not

Not a replacement for your live interviews.
Use it between them. You bring the context and decide what to dig into next.
Not proof that voice beats a form.
We think talking gets you the “why”; we haven't measured it. If your users prefer typing, tell us.
Not free of review.
Read the transcripts. Themes are a starting point, not a verdict.

FAQ

How Disco fits into your product discovery practice.

Still have questions?

Reach out anytime.

Contact us

Your next onboarding decision, with the users' own words behind it.

Start with one question. Send one link. Read what they said.

Create a discovery interviewTry an interview