The painkiller vs. vitamin test: how to tell if your idea has real demand

One of the most useful frameworks in early-stage product thinking is the painkiller vs. vitamin distinction. Painkillers solve problems people are actively suffering from. Vitamins improve lives people are already fine with. Both can build businesses, but painkillers are far easier to sell, scale, and build early traction with.

The hard part is honestly categorising your own idea. Founders are prone to vitamin blindness: the tendency to see their productivity improvement or efficiency tool as a painkiller because they genuinely believe in it.

Community research removes the founder from the equation. It lets you look at real, unprompted demand and categorise it honestly.

The difference in community language

Painkiller demand and vitamin demand look different in community posts.

Painkiller language is urgent, frustrated, and specific:

• "I've been dealing with this for months and nothing works"
• "We lost a client because we couldn't do X"
• "This is costing us hours every week"
• "Does anyone know a way to fix this because it's killing our workflow"

Vitamin language is aspirational, mild, and vague:

• "It would be nice if there was a tool for this"
• "I've been meaning to set up a system for X"
• "Not urgent but curious if anyone has a solution"
• "Would be cool to automate this eventually"

The distinction in tone is visceral. Painkiller posts read like someone in pain. Vitamin posts read like wishlist items.

How to run the test with bing.ly

Open the bing.ly Ideas tool and search your problem space. Filter to Pain Points and read twenty posts.

Ask yourself: are these people suffering right now, or would they prefer a better world someday?

If the posts are filled with words like "constantly," "every day," "it breaks," "we can't ship because of this," "I've tried everything", you have painkiller demand.

If the posts are filled with words like "would be useful," "nice to have," "eventually," "thinking about this", you have vitamin demand.

Most ideas are somewhere between the two. The goal isn't to disqualify vitamins, it's to price, position, and build them differently.

Vitamins that become painkillers

Some vitamin problems cross a threshold and become painkillers at scale. A slow process is a mild annoyance at ten customers; it becomes a business-critical problem at ten thousand. An imprecise tool is fine for solo use; it becomes a compliance risk for enterprise teams.

Look for posts that describe the problem intensifying with scale, growth, or stakes. "This was fine when we were small but now..." is the marker of a vitamin becoming a painkiller. If you find those posts frequently, you're not building a vitamin, you're building a painkiller for a specific stage of growth.

What to do with a vitamin idea

If your idea clearly lands in vitamin territory, you have three options:

1. Find the painkiller layer, go deeper into the problem to find the specific use case or segment where it crosses into acute pain. The same feature that's a vitamin in one context is a painkiller in another.

2. Reframe the business model, vitamins work better as features of larger platforms, freemium top-of-funnel tools, or community-driven products. They're harder to charge $99/month for as standalone tools.

3. Validate at the other end of the funnel, instead of looking for pain signals, look for purchase signals in the vitamin category. Some vitamins have strong purchase intent even without acute pain, because the category has been successfully sold before.

The test isn't to kill vitamin ideas. It's to go in with accurate expectations, and build distribution that matches the type of demand you actually have.