Prospect-Market-Fit Gate
Use limited real-world interaction to decide whether an MVP deserves deeper investment.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 96%
The Prospect-Market-Fit Gate is a staged investment rule for early applications. Instead of treating a completed build as the first milestone, the business creates a lightweight version that is just credible enough for interaction. It then exposes the prototype to the founder, a small group of customers, or temporary website traffic and asks two separate questions: do people actually use it, and does it create enough value to matter? Observed behavior and experience gaps reveal what should be iterated and which technology is genuinely necessary. A positive signal permits a deeper build, production infrastructure, or professional development support. A weak signal calls for revision or abandonment before substantial resources are committed. The gate therefore converts prototype evidence into a disciplined build, iterate, or stop decision.
Origin
Extracted from Marketing Against The Grain as the host explains using inexpensive AI-built prototypes to seek “prospect market fit” before funding a deeper application.
Core principles
- 01Test customer interaction before committing substantial time or money.
- 02Validate usefulness and demand separately from technical completeness.
- 03Expose the smallest credible version to real prospects.
- 04Use observed friction to identify the technology and features that actually matter.
- 05Escalate investment only after the prototype demonstrates value.
How to run it
- 1
Define the prospect hypothesis
State who should use the application, what problem it should solve, and what valuable interaction you expect. Make the hypothesis observable rather than relying on stated enthusiasm.
Pro tip Define both an engagement signal and a value signal.
Watch out Do not use technical completion as evidence of customer demand.
- 2
Build the minimum credible test
Create a basic version that allows prospects to experience the central interaction and outcome. Defer high-scale engineering and nonessential depth.
Pro tip Use a hosted prototype link when it is sufficient for the test.
Watch out A prototype that cannot demonstrate the core promise will produce misleading evidence.
- 3
Expose it narrowly
Share the application with a small number of target customers or place it on a website temporarily. Keep the test limited while accuracy and usability remain provisional.
Pro tip Begin with 10 to 20 relevant customers when direct access is available.
Watch out Do not distribute an unverified prototype broadly.
- 4
Measure interaction and value
Observe whether people start, complete, and reuse the experience, and whether the result helps them make progress. Gather the points where the flow fails or feels unconvincing.
Pro tip Watch behavior in addition to collecting verbal feedback.
Watch out Compliments without meaningful usage are weak validation.
- 5
Diagnose required improvements
Separate cosmetic requests from changes necessary for a genuinely useful experience. Identify the specific APIs, data, logic, or workflow improvements supported by evidence.
Pro tip Prioritize changes that improve the core outcome or remove measured abandonment.
Watch out Do not expand scope merely because AI makes additional features easy to generate.
- 6
Pass or fail the investment gate
If prospects interact and receive value, invest in a deeper version or hire specialists for a robust, scalable build. If they do not, iterate the hypothesis or stop before committing major resources.
Pro tip Write the pass criteria before interpreting the test.
Watch out Do not rationalize weak evidence because the prototype was inexpensive or enjoyable to build.
In the wild
A landscaper publishes the estimator on one website page for a week and shares it with 10 to 20 customers. The business monitors starts, completed estimates, captured emails, and requests for a consultation before deciding whether to build a dedicated hosted version with accurate pricing and CRM automation.
→ Investment in the production version depends on demonstrated prospect use and value rather than enthusiasm for the concept.
The curb appeal prototype produces unsupported claims about visible debris. Instead of treating the prototype as finished, the business recognizes that credible automated image analysis would require the right external API and tests whether users value the broader assessment enough to justify that integration.
→ A visible prototype flaw becomes evidence about the technology required for a good experience.
Common mistakes
Confusing deployment with validation
Publishing a link proves that an application can be accessed, not that prospective customers want or value it.
Scaling before observing behavior
Production hosting and a deep backend are premature when no one has demonstrated meaningful interaction with the lightweight version.
Validating with praise alone
Positive comments are weaker than evidence that prospects complete the flow, value the output, and move toward a customer relationship.
Is it for you?
Best for
It is best for uncertain product, tool, or lead-magnet ideas that can be represented by a credible lightweight prototype.
Not ideal for
It is not ideal when a prototype cannot safely or honestly approximate the core value proposition.
From the transcript
“And so this is like, can I get to prospect market fit?”
“Does a prospective customer really like and want to interact with this?”
“And as a marketer or as a founder, one of the things you're looking for is to validate an idea really quickly with your audience.”
From the episode
How To Create A Lead Magnet With AI (Full Tutorial)