Framework

The Vitamin-to-Painkiller Pivot Diagnostic

Test whether your product is a nice-to-have or a must-have before investing in scale. Vitamins require constant education and pushing; painkillers generate inbound demand because buyers already feel the pain. When you find the painkiller version of your product, the sales motion changes completely.

How it works

  1. 1The diagnostic question: are your prospects searching for the pain your product solves, or do you have to explain the pain first? If the latter, you might be selling a vitamin
  2. 2Painkiller signals: inbound demand you did not generate, buyers who describe their problem using the exact words you use, deals that close faster than expected with less objection handling
  3. 3Dan's pivot test: Chargerfi (wireless charging) was a vitamin - offices continued normally without it. Desk booking during COVID was a painkiller - companies had immediate, urgent pain and nothing to solve it
  4. 4You can often find the painkiller version of your product by listening for the use cases customers apply your vitamin to in crisis moments - the crisis reveals the real pain
  5. 5The transition is not just product; it is sales motion. Vitamins require outbound education and long sales cycles. Painkillers attract inbound and compress sales cycles because buyers already understand the value
  6. 6After finding product-market fit with the painkiller, do not immediately add the vitamin features back - they slow you down and dilute the core message that is working

Hear it on the podcast

The $40,000 Desk: Why Offices Will Never Be the Same AgainListen to the episode

More from this episode

Get the next framework first

One email a week with the frameworks, tools, and founder stories from the podcast. Free.

More frameworks for Finding & Validating Ideas

ICP Discovery Before ScaleAfter initial traction, resist the urge to optimize the funnel. Watch for natural clustering in your user base and find 10 people who love the product as-is before shaping messaging, positioning, or the product roadmap.The 100-Hour Constraint LaunchSet a hard time budget and a binary success metric before you build. The constraint forces prioritization and eliminates bias by requiring public validation before you've invested enough to rationalize failure.IP-First Validation StackOphir's reframe of patent search from legal afterthought to day-zero product tool. Most founders talk to customers before checking IP — and those conversations happen before NDAs, which means they publicly disclose ideas they could have protected. Running a 10-minute SenseIP validation before any outreach costs almost nothing and returns competitive intelligence, prior art context, and guidance for making the idea more novel. The IP check is not a legal step. It is a product improvement step that happens to also protect you.The Perfect Use Case FilterFilip's test for which jobs robotics should touch first.The Government GapWhy invoice finance is huge everywhere except the US.Pre-MVP Concept ValidationBefore writing code, test the concept: a landing page, a waitlist, a single-function prototype, or direct customer questions. Confirm the problem is real and users want to interact with it the way you imagine before committing engineering resources. Most founders skip this step and build the wrong thing at full cost. Fake it until you make it is not a launch strategy — it is a validation strategy.