Very disappointed is not one feeling: the Must-Have Test, run on ClickUp

01 · The question

One question that measures dependency, not satisfaction.

Satisfaction questions tell you whether people like a product. The Must-Have Test, from Sean Ellis and popularized in Hacking Growth, asks whether they would feel a loss without it.

The core questionApplied to ClickUp

How would you feel if you could no longer use [product]?

AVery disappointed

BSomewhat disappointed

CNot disappointed

DN/A, I no longer use it

40%

The benchmark

If 40% or more of qualified respondents answer very disappointed, you have likely reached product-market fit. Across the startups Ellis studied, those reaching this mark tended to go on to sustainable growth.

2 · 2

Who qualifies

Users who have experienced the core value, used the product at least twice, and used it within the last two weeks. Plan for 40 to 50 qualified responses.

→

What to do next

At or above 40%, invest in growth. Below it, iterate first: ask what the main benefit is, who else would benefit, and how to improve it. Refine, then retest every few months.

Where the test comes from

Hacking Growth

Sean Ellis & Morgan Brown · 2017

Sean Ellis, founder of GrowthHackers.com and the person who coined the term "growth hacking," created the Must-Have Test. Before a company invests in growth, he argues, it needs proof that its product is a must-have for a core group of users.

Ellis led early growth at companies including Dropbox and Eventbrite, and the 40% threshold comes from comparing the answers across hundreds of startups.

In Hacking Growth, Ellis and Brown treat a must-have product as the prerequisite for growth: confirm it first, then experiment to scale it. This study takes that gate and asks what sits underneath the answer.

02 · What the panel said

Two segments, one shared vocabulary.

Nobody in the panel was indifferent. The split ran between archetypes who said they rely on ClickUp and archetypes who said they could replace it. Read the reasons, though, and both groups reach for the same words: the scattered mess before, the effort invested, the pain of another transition.

Very disappointed

These archetypes describe ClickUp as where work lives. What they picture losing is operational progress: clarity, alignment, automation. But some of that loss is about the product and some is about the move.

Sounds like the product

Finding something with ClickUp's level of customization and all-in-one functionality wouldn't be easy.Carlos Mendoza · CEO · B2B software

Sounds like the job

If we lost that tomorrow, we'd be right back to the scattered mess we had before.Carlos Mendoza · CEO · B2B software

Sounds like the move

I'd basically be asking them to go through that learning curve all over again.Maria Rodriguez · Marketing Ops · E-commerce

See all six themes in this segment

The backbone of operations

ClickUp is described as the place where work lives: it consolidates tools, automates workflows, and gives cross-functional visibility.

ClickUp has become the backbone of how we operate now. If we lost that tomorrow, we'd be right back to the scattered mess we had before.Carlos Mendoza · CEO · B2B software

A high emotional cost of loss

Losing it would feel like a step backward in maturity, not an inconvenience.

Before ClickUp, I could tell myself our system was 'good enough' because I didn't know how much better things could be. Reverting would feel like torture.Jennifer Williams · Business Analyst · Manufacturing

Time and effort already invested

Months of setup, training, and stakeholder buy-in would be wasted and rebuilt from scratch.

I'd basically be asking them to go through that learning curve all over again.Maria Rodriguez · Marketing Ops · E-commerce

Strong team adoption

Dependence is collective. Whole teams are onboarded and aligned, so disruption would hit morale and pace.

The team has bought into this system. Switching tools again would hurt morale.Alex Kim · Design Lead · Media

No equal replacement in sight

Monday, Asana, and Jira exist, but none feel like a true like-for-like substitute for ClickUp's breadth.

Finding something with ClickUp's level of customization and all-in-one functionality wouldn't be easy.Carlos Mendoza · CEO · B2B software

→

The everything-in-one-place effect

For the individual contributors in this group, the loss is personal workflow, not just team process.

The thought of going back to juggling multiple tools and dealing with that scattered, chaotic system I had before makes me stressed just thinking about it.Rachel Foster · Product Designer · Consumer apps

Somewhat disappointed

These archetypes do not dislike ClickUp; they expected more. It is useful but has not earned irreplaceable status, and their disappointment reads as unrealized potential and change fatigue rather than deep reliance.

The value is in the job

The real value has been in consolidating our scattered processes, not necessarily in ClickUp itself.David Chen · VP Engineering · Fintech

The loss is the move

The disappointment would be more about going through another transition.Sarah Mitchell · Director of Operations · Fintech

Open to alternatives

Part of me would almost see it as an opportunity to find something that might actually work better for our team.Alex Thompson · Scrum Master · Enterprise software

See all six themes in this segment

Valuable, but not transformative

It improved some workflows but did not fully solve the problems it was hired for: adoption, complexity, reporting.

It hasn't really delivered on the transformational productivity gains I was expecting.Marcus Chen · VP Engineering · SaaS

Disappointment tied to sunk cost

The loss they imagine is the effort of implementation, not a business disruption.

The disappointment would be more about going through another transition.Sarah Mitchell · Director of Operations · Fintech

Adoption challenges remain

Usage is uneven. Some people rely on it, others bypass it, which caps its perceived impact.

Some people use it religiously, others treat it like a checkbox.Sarah Mitchell · Director of Operations · Fintech

Still open to alternatives

Switching is seen as painful but viable, and some would welcome the excuse.

Part of me would almost see it as an opportunity to find something that might actually work better for our team.Alex Thompson · Scrum Master · Enterprise software

Solved some problems, created others

Centralization was welcome, but ongoing complexity and admin effort remained, alongside other tools still in use.

We're still using Slack heavily, and Google Docs for anything substantial.Sarah Mitchell · Director of Operations · Fintech

→

The value sits in the job, not the tool

The most revealing answer in the study came from this segment.

The real value has been in consolidating our scattered processes, not necessarily in ClickUp itself.David Chen · VP Engineering · Fintech

03 · The analysis

Three reasons to say "I'd be disappointed."

Coded from the ClickUp

panel

The checkbox a respondent ticks does not tell you which kind of dependency sits underneath it. The "why" does, and each kind calls for a different probe.

Source 1

Dependency on the product

Something only this product delivers. Here, the breadth and customization respondents could not find elsewhere.

Finding something with ClickUp's level of customization and all-in-one functionality wouldn't be easy.Carlos Mendoza

ProbeIf it disappeared tomorrow, what would you use instead, and what would get worse?

What to listen forNo ready substitute, and a specific capability they would lose. A strong signal, not proof on its own.

What they value · specific to you, for now

Source 2

Dependency on the job

They depend on the progress the product made possible, consolidating scattered work, but any tool that does that job might do.

The real value has been in consolidating our scattered processes, not necessarily in ClickUp itself.David Chen

ProbeWhat is the main benefit you receive, and could another tool give you the same thing?

What to listen forThe benefit described as an outcome, with a competitor named quickly.

What they value · shared by the category

Source 3

Dread of switching again

The loss imagined is the migration: retraining, lost setup, team morale. In forces terms, this is Habits and Allegiances, not Pull.

The disappointment would be more about going through another transition.Sarah Mitchell

ProbeWhat made you choose that answer? Is the pain about losing the product, or about the move?

What to listen forTalk of setup, training, and disruption rather than anything the product does.

What makes leaving hard · switching cost

A very disappointed score built on switching dread can clear 40% and still leave you exposed the day a competitor offers a painless migration.

This is why the Ellis follow-ups matter more than the headline number. The percentage tells you how many people would feel a loss. The follow-up separates what customers value from what makes leaving difficult. Neither settles defensibility on its own: switching costs do slow churn, and product-specific capability can be copied.

These sources can coexist in the same account. Carlos Mendoza describes all three. The research asks which matters most, and what would change the decision to stay.

04 · What it could mean for growth

The somewhat disappointed answers point to adoption.

None of the somewhat disappointed reasons are about ClickUp losing a head-to-head comparison. They describe what happened after the purchase: uneven use across the team and expected gains that never showed up. Other tools staying in use does not establish failed adoption on its own. The sharper question is whether the behavior ClickUp was hired to replace still persists. In a synthetic panel that is a lead, not a finding, and it points to a different customer decision than the one the Must-Have Test is usually read against.

03 · Adopt

Did the old behavior stop?

Not whether other tools are still open, but whether the work ClickUp was hired to replace still happens the old way. Explore the Adoption Reality Check.

04 · Renew

Which dependency holds at renewal?

Switching dread delays churn. It does not prevent it. Explore the Churn Decision Study.

01 to 04

See all four decisions

Act, Buy, Adopt, Renew: where new growth survives or is lost.

05 · The questions to field with real users

Questions that separate the three sources.

The original four questions, plus three probes that tell product dependency, job dependency, and switching dread apart.

#	Question	What it reveals
Q1	How would you feel if you could no longer use [product]?	The headline split. Score it only with real, qualified respondents.
Q1b	What made you choose that answer?	Which of the three sources sits under the checkbox.
Q2	What is the main benefit you receive from [product]?	The job it was hired for, in the customer's own words.
Q2b	If it disappeared tomorrow, what would you use instead, and what would get worse?	Names the substitute. A quick answer points to job dependency; no ready answer points to product dependency worth testing further.
Q3	Who do you think would benefit most from [product]?	How the must-have segment describes itself, useful for targeting.
Q4	How could we improve it for you?	What stands between somewhat and very disappointed.
Q5	When did it shift from something you were trying to something you would miss?	Very disappointed only. The moment dependency formed, and what triggered it.

06 · Running it on your product

Three modes. Choose by the question you need answered.

This study is Mode 1, synthetic. Each mode answers a different question, and you do not have to start at the first. If you already have access to qualified users, Mode 2 may be the right place to begin.

Mode 1 · Synthetic

Generate the hypotheses

AI archetypes built to your firmographics, jobs, and buyer roles. What you saw on this page.

Participants: AI-generated
12 to 24 archetypes across roles and usage states
Answers: Who the must-have segment might be, which source of dependency drives them, which follow-ups earn their place
Must-Have score: No. The mix reflects the panel design.
Speed: Days

You walk away withHypotheses and a pressure-tested interview guide

Mode 2 · AI-moderated

Measure it at scale

Your real users, interviewed by an AI moderator that asks the Must-Have question and follows every answer with "why."

Participants: Your real users
40 to 200+, qualified on the 2 · 2 rule
Answers: Your actual very disappointed rate, with the reasons behind every answer coded into the three sources of dependency
Must-Have score: Yes. This is where the 40% benchmark applies.
Precision around a 40% result: ±15n = 40
±10n = 100
±7n = 200

You walk away withA real score and survey scale, with interview depth

Mode 3 · 1:1 expert

Reconstruct the story

Expert-led interviews using Timeline Reconstruction, for the buyers an AI moderator cannot easily reach.

Participants: Hand-picked
6 to 12 economic buyers, champions, and churned accounts
Answers: When dependency formed and what triggered it, what held the somewhat disappointed back, and why the ones who left fired you
Must-Have score: No. Too few to score, built for causation.
Speed: One to two weeks

You walk away withThe deepest causal story, in the buyer's own words

Faster and broaderDeeper and more causal

A recommended sequence, when you need all three

When you need both sharper hypotheses and a real score, this order keeps each step cheaper than the one after it. Skip any step you already have the answer to.

Mode 1: define the archetypes and run the panel

Specify firmographics, job to be done, and role in the buying decision, with more than one role per account. Use the conversations to form hypotheses and sharpen the follow-up questions.

Mode 2: field the instrument with real users

Run the refined guide as AI-moderated interviews with 40 to 200 qualified users. You get the very disappointed rate and the reason behind every answer, so you can see how much of your score is product dependency, job dependency, or switching dread.

Mode 3: go deep where it matters

Interview the economic buyers, champions, and churned accounts 1:1. Reconstruct how the very disappointed reached dependency and what held everyone else back. See our interview methods and the Switching Interview field guide.

Retest after changes

Repeat Mode 2 every few months or after major updates, and avoid resurveying the same people too soon.

07 · How this study was run

The panel, the answers, and their limits.

Every participant in this study is an AI-generated synthetic archetype built on the Synthetic Users platform. The names are invented, but the answers are not made up out of thin air.

Where the answers come from

The language models behind synthetic interviews learn from an enormous body of real, public writing: customer stories, product reviews, case studies, forum threads, and the ways buyers in each role describe their tools, their struggles, and their reasons for switching. Each archetype's answers are grounded in those patterns, which is why they sound like real buyers. They are a synthesis of many voices, not a quote from any one person.

Archetype, not persona

A persona is a fictional individual, one imagined person with a backstory, often built to make a team feel empathy. An archetype is a recurring pattern of buyer: a role, a company context, a job to be done, and a way of deciding that shows up across many real people. The names below are labels for those patterns. What carries the meaning is the combination of role, industry, decision authority, and adoption style, not the individual.

So treat them as evidence of patterns, not as statements from actual ClickUp customers. This study is independent and is not affiliated with or endorsed by ClickUp. We use it to show how the method works, not to make claims about ClickUp's actual product-market fit.

Panel design

Twelve archetypes, four roles, one question asked the long way.

Panel generated on Synthetic Users

Instead of sending the question as a survey, we asked it inside a synthetic interview, then followed every answer with "why." Each archetype was defined by firmographics, role, decision authority, and adoption style, the pattern a buyer represents rather than an individual biography, and spread across the four B2B buyer types.

Economic buyer

Approves the budget and owns the business case.

Technical buyer

Evaluates fit with existing systems, security, and workflows.

User buyer

Lives in the tool every day and feels its friction first.

Champion

Advocates for the tool internally and carries it through the decision.

Alongside the core question we asked the three Ellis follow-ups: the main benefit received, who would benefit most, and how it could be improved.

See all 12 archetypes

Carlos Mendoza

CEO

31 · Denver · B2B software · team of 35 · high authority

Sarah Martinez

COO

42 · Austin · SaaS · team of 150 · high authority

James Wilson

VP Product

40 · Seattle · SaaS · team of 45 · high authority

David Chen

VP Engineering

38 · Toronto · Fintech · team of 25 · high authority

Marcus Chen

VP Engineering

42 · San Francisco · SaaS · early adopter

Jennifer Kim

Chief of Staff

45 · Seattle · Healthcare tech · pragmatic adopter

Sarah Mitchell

Director of Operations

38 · Toronto · Fintech · cautious adopter

Alex Thompson

Scrum Master

40 · Denver · Enterprise software · facilitative

Maria Rodriguez

Marketing Ops Manager

35 · Mexico City · E-commerce · team of 8

Alex Kim

Design Lead

29 · Vancouver · Media · team of 6

Jennifer Williams

Business Analyst

37 · Chicago · Manufacturing · low authority

Rachel Foster

Product Designer

28 · New York · Consumer apps · team of 1

Why run it as a conversation

A typical study gives you a number. This one gives you the reasons.

The Must-Have Test is usually run as a survey. You get a percentage and a handful of one-line open-text answers that most respondents skip. The data is mostly quantitative. Running it as a synthetic conversation flips that balance.

Typical Must-Have survey

Mostly quantitative

FormatMultiple-choice survey sent to users
What comes backA distribution across four answers, plus short optional comments
The whyInferred from a few words, or left as a follow-up project
Time to insightWeeks of recruiting and waiting for 40 to 50 responses

Quantitative

Qualitative

What you walk away with (illustrative)

38%

very disappointed. "It's useful." "Good tool." "N/A."

This approach Synthetic Users

Abundantly qualitative

FormatThe same question asked inside a conversation, followed by "why"
What comes backParagraphs of reasoning per participant: what they fear losing, what they would switch to, what held them back
The whyThe center of the output, coded into themes and sources of dependency
Time to insightDays, before a single real user is recruited

Quantitative

Qualitative

What you walk away with

"The real value has been in consolidating our scattered processes, not necessarily in ClickUp itself."

"Part of me would almost see it as an opportunity to find something that might actually work better for our team."

Synthetic participants are generated by language models trained on a vast body of public writing, including the ways professionals talk about their work, their tools, and their frustrations across the web: forums, reviews, community threads, and posts. That is what makes the conversations so rich. Each archetype reasons through its answer in the language real buyers in that role tend to use, so a 12-person panel produces more explanation than a survey of hundreds.

The trade-off is that this richness is a map of patterns, not a measurement of your market, which is why this study reports no score. Use the qualitative depth to decide what to ask, then let real users give you the number through AI-moderated interviews, and go deepest with 1:1 expert interviews. See the three modes.

Questions founders ask

Before you run the test.

What is the Must-Have Test?

The Must-Have Test, also called the Sean Ellis test or product-market fit (PMF) survey, asks users how they would feel if they could no longer use a product: very disappointed, somewhat disappointed, not disappointed, or no longer using it. A result of at least 40% “very disappointed” is a commonly used signal of product-market fit, rather than proof of retention or defensibility. It was created by Sean Ellis and is described in Hacking Growth (Sean Ellis and Morgan Brown, 2017). More on where the test comes from.

Who should take the Sean Ellis Must-Have Test?

Users who have experienced the core value of the product, used it at least twice, and used it within the past two weeks. Plan for 40 to 50 qualified responses. In B2B research, distinguish users from purchasing decision-makers, and include more than one role so the result is not driven only by the person who chose the tool. If you interview several people from one account, report that explicitly; their responses are not independent customer accounts.

What should you ask after the Sean Ellis product-market fit question?

Start with why: ask what made the respondent choose their answer. Then ask the standard follow-ups: the main benefit they receive, who they think would benefit most, and how the product could be improved. Two further probes add depth: what they would use instead if the product disappeared and what would get worse, and, for very disappointed respondents, when the product shifted from something they were trying to something they would miss.

Does a high Must-Have score mean customers will stay?

A high Must-Have score does not guarantee retention. Customers may fear losing a product-specific benefit, progress another product could provide, or the time invested in setup and training. These reasons can coexist. Follow-up interviews help distinguish what customers value from what makes leaving difficult. In this report we group those reasons into three sources of dependency, the product, the job, and the move; that is our analytical framework, not part of Ellis’s original test.

What can “somewhat disappointed” answers reveal about product adoption?

Somewhat disappointed answers often describe what happened after the purchase rather than a lost comparison with a competitor: uneven use across a team, expected gains that never arrived, or a sense that the product is useful but replaceable. That points to adoption worth investigating. The sharper question is whether the behavior the product was hired to replace still persists; other tools staying in use does not establish failed adoption on its own. See the Adoption Reality Check.

Can a synthetic user study tell me if I have product-market fit?

No. A synthetic panel’s percentage reflects how the panel was built, not your market. A synthetic study is useful for generating hypotheses about who your must-have segment is, what drives dependency, and which follow-up questions to field with real users. The 40% benchmark needs 40 to 50 real, qualified respondents.

What is the difference between synthetic, AI-moderated, and 1:1 expert interviews?

Synthetic interviews use AI-generated archetypes to form hypotheses and refine the instrument in days. AI-moderated interviews put that instrument in front of 40 to 200 of your real users, to measure the very disappointed rate among participating users and investigate the reasons behind it; recruitment and sampling still determine how far the result generalizes. 1:1 expert interviews go deepest with a handful of hard-to-reach buyers to reconstruct how dependency formed or why they left.

Three things "very disappointed" can mean.

Something only you deliver

Progress another product could give them

A migration they dread repeating