The short answer
To judge product-market fit, look for a defined group that tries to start, gets a meaningful benefit and chooses the product again when the job returns. Record those signals together before deciding to expand or revise.
Separate enthusiasm from evidence of fit
- Signal you observe
Someone tries to start
What it tells youInterest became an action
What to check nextRecord trials, access requests or purchases where relevant. Keep compliments in a separate column.
2 sources behind this suggestion
Stauch described Serval conversations changing from general interest to questions about cost, trials and proof-of-concept processes. Frederick James tested demand differently: he gave his SDK to existing apps, then reported additional revenue and reviews for those apps. A buying question and a product test provide different evidence of intent.13
- Signal you observe
They receive a benefit
What it tells youThe product helped with a job
What to check nextAsk what changed and inspect available evidence. Time spent or completed setup is not enough.
2 sources behind this suggestion
In Dalton + Michael's discussion, a speaker urged founders to measure the customer's actual benefit rather than only time spent with the product. De Sousa recommends tracking onboarding, retention and feature adoption, while separating paying from free users before deciding which features deserve attention.45
Behind this tip2 sources · Select to explore - Signal you observe
They choose it again
What it tells youThe benefit may be repeatable
What to check nextFollow the same group when the job returns. Check whether they choose you or their old alternative.
1 source behind this suggestion
Hiten Shah revised his early-access playbook to ask whether someone who succeeded once would choose the product again or return to their old method. That question separates an initial success from a customer's later choice.2
Behind this tip1 source · Select to explore
Your fit-signal record
Customer group and job: [who needs what] Current alternative: [what they use today] Starting action: [what they actually did] Observed benefit: [what improved] Next-time choice: [what they chose when the job returned] Decision: [expand, investigate or change]
Expand carefully
Starting actions, benefit and repeat choice recur in the group you intend to serve. Test whether that pattern extends.
Investigate
A signal is missing or the customers are unusually narrow. Learn what blocks the pattern.
Change
Use does not create the expected benefit. Reconsider the product, offer or customer group.
Detailed reasoning and examplesThe full playbook, source comparisons and related questions
Use this when
Use this playbook if people can try your product and you need to assess demand beyond initial interest.
You’ll leave with
Leave with a fit-signal worksheet for a defined customer group and an expand, investigate or change decision.
Your playbook
Define whose fit you are judging
- Do
Choose the customer group showing the clearest interest. Write down its recurring job, current alternative and expected benefit. Keep other groups separate so their behavior cannot mask a weak signal.
- Make
Start a fit-signal worksheet with the group, job, alternative and expected benefit.
- Check
If you cannot describe a shared job and alternative, narrow the group before judging fit.
Preview the template
Customer group: [who] Recurring job: [what they need done] Current alternative: [what they use now] Expected benefit: [what would improve] Starting action: [what they did] Observed benefit: [what changed] Return behavior: [what they chose next time] Decision: [expand, investigate or change]
Why this step is in the plan
Jake Stauch said fans of his previous product had given him a mistaken sense of fit. Mat De Sousa learned through agency conversations that some agencies valued his bundle app chiefly for its data and tests, rather than its bundles. Both accounts show why the customer's job matters alongside their enthusiasm.15
Distinguish praise from an attempt to start
- Do
For the chosen group, record what interested people did next: asked how to start, requested access, tried the product or purchased it, where purchasing applies. Record praise separately.
- Make
Add starting actions, each tied to a customer and job, to the worksheet.
- Check
If interest never becomes an attempt to start, investigate what blocks the decision before calling it fit.
Why this step is in the plan
Stauch described Serval conversations changing from general interest to questions about cost, trials and proof-of-concept processes. Frederick James tested demand differently: he gave his SDK to existing apps, then reported additional revenue and reviews for those apps. A buying question and a product test provide different evidence of intent.13
Check the benefit, not just the activity
- Do
Ask users what changed after use and inspect available evidence of that change. Record the benefit for their job, including cases where setup finished but no useful result followed.
- Make
Add observed benefit and unresolved gaps to the worksheet.
- Check
If use is visible but the expected benefit is not, revisit the product or the job before expanding.
Why this step is in the plan
In Dalton + Michael's discussion, a speaker urged founders to measure the customer's actual benefit rather than only time spent with the product. De Sousa recommends tracking onboarding, retention and feature adoption, while separating paying from free users before deciding which features deserve attention.45
See what happens when the job returns
- Do
Follow the same users when the job recurs. Record whether they choose your product again, what they use instead if they do not and whether returning users belong to your defined group.
- Make
Add return behavior by customer group to the worksheet.
- Check
If users return and receive the benefit again, examine whether that pattern repeats; if they revert, investigate why.
Why this step is in the plan
Hiten Shah revised his early-access playbook to ask whether someone who succeeded once would choose the product again or return to their old method. That question separates an initial success from a customer's later choice.2
Decide whether the pattern can extend
- Do
Review the worksheet across customers with the same job. Choose whether to serve more people like the repeat users, investigate a missing signal or change the group or offer. Note what observation would change your decision.
- Make
Complete the worksheet with an expand, investigate or change decision and its supporting observations.
- Check
Expand only if attempts to start, delivered benefit and repeat choice recur in the group you intend to serve.
Why this step is in the plan
Stauch said unusually distinctive early customers can be a warning when there is no clear path to the wider market. During Serval's customer discovery, he also avoided letting any single conversation weigh too heavily. The strength of an early signal and the breadth of its customer group are separate questions.1
When this works
- Use this assessment when you can observe a customer's decision to start, the benefit received and what happens when the need returns.
When to avoid
- Do not declare fit from enthusiastic conversations, sign-ups or initial use alone; treat them as signals to investigate.
Compare the real examples
What 3 sources did and reported Explore examples ↓
- YouTube
Jake Stauch
He said the earlier enthusiasm had misled him about fit and described a later shift toward concrete buying questions for Serval.
Had enthusiastic customers for his previous product, NeuroPlus; later watched Serval conversations shift toward questions about cost and how to start.
- X
Frederick James
He reported additional revenue and reviews for those apps and called the test validation of product-market fit.
Gave his SDK to existing apps to test it.
- X
Mat De Sousa
He said some agencies used WideBundle more for its data and tests than for its bundles.
Asked agencies about bundles and the tools they used.