Painkiller vs Vitamin

Whether your product solves an urgent pain or is merely nice to have.

Also known as: painkiller vs vitamin, painkiller, must-have vs nice-to-have

A painkiller relieves an urgent, expensive problem — customers buy fast, tolerate rough edges and churn rarely. A vitamin is nice to have — pleasant, healthy, and the first thing cut when budgets tighten. Startups selling vitamins to people with headaches wonder why nobody buys; the product can be excellent and still optional.

painkiller:  payroll that must run, outage that must end, audit that must pass (bought urgently)
vitamin:     nicer reports, tidier workflows, interesting insights (bought "someday")

Pain is measurable: what does the problem cost monthly? What breaks without a fix? Who gets fired if it persists? If the answers are vague, small or far-future, you have a vitamin — either find the pain inside it or pick a different problem.

The classic mistakes:

Marketing a vitamin with painkiller urgency. Aggressive sales for a nice-to-have burns trust and invites churn the moment novelty fades. Match the motion to the medicine.
Assuming pain from complaints. Users complain about everything; budgets reveal pain. Complaints plus workaround spending equals painkiller territory — complaints alone equal vitamin.
Building vitamins for enterprises. Enterprise buying needs budget justification; “nice dashboards” dies in procurement while “failed audit risk” flies. Sell pain or sell to consumers.
Never checking which you are. Ask churned users what they replaced you with: “nothing, we’re fine” is the vitamin verdict. Ask before the next roadmap, not after.

If you have a vitamin: either attach it to a painkiller (analytics inside a must-have workflow), find the segment for whom it is pain, or accept slow organic growth funded by patience (see indie hacking).