Must-Have Benefit Excavation
A three-question survey sequence that turns 'they like it' into the exact hook that acquires customers
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 92%
After the Sean Ellis Test isolates your very-disappointed users, run a follow-up survey sequence to extract the specific benefit they get and the emotional context behind why it matters. That context becomes the messaging hook, the onboarding focus, and the acquisition-targeting logic for sustainable growth.
Origin
Developed by Sean Ellis, refined while working with early YC company Xobni (Inbox spelled backwards). The 'why is that benefit important to you' question surfaced 'I'm drowning in email,' which he turned directly into a high-converting acquisition hook.
Core principles
- 01Filter feedback to only your must-have users before mining it
- 02Open-ended first to discover the language, then multiple-choice to quantify
- 03The 'why' behind the benefit is the acquisition hook, not the benefit itself
- 04Run filters by use-case bucket to see which segments are most loyal vs most numerous — a strategic choice, not just a data point
How to run it
- 1
Ask the primary benefit — open-ended
Ask the very-disappointed cohort 'what is the primary benefit that you get?' as free text to crowdsource the real benefit statements in customers' own words.
Pro tip Capture the exact phrasing users write — it becomes your marketing copy.
- 2
Force a choice — multiple-choice on a fresh group
Turn the crowdsourced benefits into four distinctive benefit statements and make a different group pick one. This quantifies which benefit dominates.
Pro tip Use a different sample group than step 1 so you're not priming the same people.
- 3
Ask why that benefit matters
Follow the multiple-choice with 'why is that benefit important to you?' to surface the emotional context — the situation the user is living in.
Pro tip At Xobni the answer was 'I'm drowning in email' — tested as an acquisition hook, it converted far better than the feature description alone.
- 4
Bucket and filter by use case
Segment respondents by how they use the product and compute very-disappointed rates per bucket to reveal a small intensely-loyal segment vs a larger lukewarm one, then decide strategically which to serve.
Pro tip Sean prefers the more passionate customer base — your biggest competitor when innovating is irrelevance, so deep relevance to someone beats mild appeal to many.
In the wild
Very-disappointed users said Xobni helped them find things faster in email. Asked why that mattered, they said they were drowning in email. Tested as the hook 'drowning in email?', it set a strong context that made people receptive to the find-things-faster message.
→ Became the acquisition message; the 'why' question became a permanent part of Sean's survey toolkit.
Common mistakes
Stopping at the benefit
Knowing the benefit ('find things faster') without the emotional why ('drowning in email') leaves the strongest hook on the table.
Listening to somewhat-disappointed users here
Mining nice-to-have users dilutes the signal; this excavation is only meaningful on the must-have segment.
Is it for you?
Best for
Founders/marketers who have a passable Sean Ellis Test score and need to convert that fit into positioning, onboarding focus, and acquisition messaging
Not ideal for
Products with no identifiable must-have segment yet — there's nothing to excavate until some users say very disappointed
From the transcript
“what is the primary benefit that you get and then um I use that initially as an open-ended question to to kind of crowdsource different…”
“then then I run another survey where I turn it into a multiple choice question forc them to pick one of four kind of distinctive…”
“I'm drowning an email like I just I kept seeing that statement as as a written statement”
“people who use it this way are like 60% likely to be very disappointed without the product but people who use it this way are…”
From the episode
The original growth hacker reveals his secrets
Sean Ellis (author of “Hacking Growth”)