Manual Demand Stress Test
Simulate the service cheaply before funding or building the product
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 99%
The Manual Demand Stress Test replaces expensive product development with a fast concierge-style simulation. Begin by identifying the behavior the proposed product needs customers to adopt. Then reproduce the product's intended outcome manually, even if the experience is rough or incomplete. Put that proxy in front of real target users and observe whether they engage, change behavior, or reveal that an existing habit already solves the problem. The test focuses on demonstrated demand rather than verbal enthusiasm. If users do not want the manual outcome, a polished automated version is unlikely to justify a year of work and major funding. If they do, the team gains concrete execution ideas and can build with less uncertainty. The goal is the cheapest credible test, not a miniature finished product.
Origin
James Altucher contrasted raising $2 million to build restaurant-ordering AI with manually helping diners choose orders for one night.
Core principles
- 01Execution has good and bad ideas of its own
- 02A manual simulation can test demand before software exists
- 03Speed and low cost preserve time and capital
- 04Most people resist adding new behavior to an already full day
How to run it
- 1
Name the behavior change
Specify what customers must do differently and which existing activity the product would displace.
Pro tip Frame demand as a claim about behavior, not stated interest.
Watch out People already have routines filling their day, so novelty faces real resistance.
- 2
Build a manual proxy
Deliver the promised result by hand without building the full technology or operation.
Pro tip Approximate the outcome even when the proxy does not resemble the final interface.
Watch out Do not spend heavily to make a demand test look polished.
- 3
Test with real users
Run the proxy in the target setting and invite actual prospective users to engage with it.
Watch out Friends praising the concept is weaker evidence than target users changing behavior.
- 4
Observe the friction
Look for whether users already have a preferred solution, refuse the new behavior, or value the intervention enough to continue.
Pro tip Record actions and objections immediately after the test.
- 5
Make the investment decision
Kill, revise, or build the idea based on the observed demand and the execution lessons from the proxy.
Watch out Do not rationalize a failed test merely because the original idea feels exciting.
In the wild
Before funding an AI system that recommends restaurant orders, the founders ask a restaurant-owning friend for permission to help diners choose manually for one night. They discover that customers already arrive with preferences and do not want the intervention.
→ The founders avoid a year of development and a $2 million raise for weak demand.
Common mistakes
Building before observing
A polished product can consume time and capital without resolving whether customers want the underlying behavior change.
Testing opinions instead of actions
Positive reactions do not equal demand; watch whether target users actually accept the manual outcome.
Is it for you?
Best for
Founders testing a service or software idea whose outcome can be approximated manually.
Not ideal for
Products where no safe or meaningful manual proxy can reproduce the core customer behavior.
From the transcript
“execution doesn't mean one thing you have to have execution ideas on how to execute there are good execution ideas and bad execution ideas”
“when you try to break things down and do things manually as quick as as maybe it might not be the exact product but you…”
“it's good to execute as cheaply and quickly as possible”
From the episode
Unlock Your Potential and Thrive as a Content Creator