Painkiller-versus-Vitamin Test
Prioritize products that remove deep pain over products that are merely nice
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 98%
The Painkiller-versus-Vitamin Test classifies a proposed product by the urgency of the customer problem it resolves. A vitamin may provide benefit, but the customer can treat it as optional. A painkiller addresses a deep, felt problem that the customer actively wants removed, much like seeking medicine for a headache. Begin with a precise customer and articulate the pain in their language. Examine the cost of leaving it unresolved, the alternatives already used, and the direct mechanism by which the product creates relief. If the value remains a general improvement rather than a necessary outcome, either strengthen the problem-solution fit or deprioritize the idea. The test is a prioritization lens, not permission to exaggerate pain that customers do not actually feel.
Origin
Nathan identifies this as a common Silicon Valley concept rather than his invention and uses Foundr Plus as his example of a product intended to solve a deep entrepreneurial pain.
Core principles
- 01Urgent pain creates stronger demand than optional benefit
- 02A painkiller removes a specific costly problem
- 03A vitamin is useful but easy to postpone
- 04The customer's felt need matters more than the maker's enthusiasm
How to run it
- 1
Define the customer
Choose the specific person and situation for which the product is being evaluated.
Pro tip Different segments may classify the same product differently.
Watch out A product for everyone hides whose pain matters.
- 2
Name the pain
State the concrete problem the customer wants removed, using observed customer language where possible.
Pro tip Look for urgency, repeated complaints, or active workarounds.
Watch out Do not manufacture anxiety to make the problem sound deeper.
- 3
Measure the unresolved cost
Identify what the customer loses in money, time, risk, or opportunity while the problem remains.
Pro tip Specific consequences are stronger than broad inconvenience.
- 4
Explain the relief mechanism
Show exactly how the product removes or materially reduces the pain.
Pro tip Connect each major feature to the relief it creates.
Watch out A feature list is not a painkiller mechanism.
- 5
Classify and act
Classify the offer as a painkiller or vitamin, then prioritize, reposition, or reject it accordingly.
Pro tip Validate the classification through customer behavior, not internal opinion.
Watch out Preventive products may be valuable even when customers perceive them as vitamins.
In the wild
Nathan describes Foundr Plus as a painkiller for people trying to start or grow a business because it gives them proven frameworks, shortcuts, and lessons from experienced operators.
→ The offer is positioned around reducing the confusion and delay of figuring out business building alone.
A team proposes a dashboard with attractive charts but cannot identify a costly decision it improves. Customer interviews show users appreciate the visuals but would not change their current workflow or pay for them.
→ The team classifies the idea as a vitamin and redirects effort toward a reporting problem customers urgently need solved.
Common mistakes
Calling every benefit a pain
Broad claims weaken the test and encourage building around imagined urgency.
Confusing features with relief
Customers buy the resolved problem, not the existence of functionality.
Is it for you?
Best for
Prioritizing startup ideas, product features, and positioning before substantial investment.
Not ideal for
Products whose value is primarily long-term prevention and cannot honestly be framed as immediate relief.
From the transcript
“what vitamins are something that people take as a nice to have they don't really need it”
“the best products and services are pain killers they solve a deep pain”
“you've really got to think about does your product or service solve a deep pain”
From the episode
Nathan Chan: The Founders Blueprint
Nathan Chan