Candy vs Vitamin vs Painkiller: Startup Ideabase Classification

Introduction

Practical bias for Candy vs Vitamin vs Painkiller: Startup Ideabase Classification: fewer adjectives, more calendar holds with people who feel the problem.

Original insight: checklists without kill criteria become diaries. Add dates for when you will stop.

Real-world example: Slack’s seating expansion worked because daily utility created pull—not because the landing page had more adjectives.

Introduction Practical bias for Candy vs Vitamin vs Painkiller: Startup Ideabase Classification: fewer adjectives, more calendar holds with people who feel the problem. Original insight: checklists without kill criteria become diaries. Add dates for when you will stop. Real-world example: Slack’s seating expansion worked because daily utility created pull—not because the landing page had more adjectives. ## Learn the system

Read How we classify and the value proposition axis, then browse the Idea Database with those labels in mind.

Explore free on Startup Ideabase

• How we classify ideas
• Value proposition axis
• Idea Database (free)
• How to get startup ideas
• Tech & software ideas

On Startup Ideabase, every idea is tagged with a value proposition: `painkiller`, `vitamin`, `hybrid`, or `candy`. Use that tag (and industry filters) to find projects that match this article.

• Browse the Idea Database and open ideas marked as painkillers or vitamins.
• Use Find your match to filter by skills, then prefer painkiller problems.
• For deep evidence-backed products, open Market research.
• Students: start with Student projects; researchers: PhD catalog.
• If you see Roadmap Available, unlock a step-by-step build plan on the idea page.

What to do this week

1. Decide whether your current idea is a painkiller, vitamin, hybrid, or candy. 2. Open three related ideas on this site and compare problem urgency. 3. Copy Ask your AI about this project on an idea page and pressure-test the plan. 4. Revisit “Candy vs Vitamin vs Painkiller: Startup Ideabase Classification” after user interviews. ## Field notes (read these before you build) Unexpected challenge: calendar reality. If you cannot book real users this week, your plan is fiction regardless of how polished the strategy doc looks. Counter-intuitive advice: kill your favorite feature if it does not show up in the story of a real user’s worst week. Distribution bottleneck: warm intros dry up. Build a cold motion that still sounds human—specific problem, specific proof, short ask. Hidden cost: context switching. Founders lose more to tab chaos and half-built side quests than to lack of ideas. One caution: if metrics only move when you post on social, you have an audience project, not necessarily a company. One recommendation: if a concept has a build plan, skim Roadmaps—then validate demand before phase two of engineering. Straight take: 2026 is not special enough to justify skipping fundamentals. Models got better; buyers did not start loving vague tools. ## FAQ

It is tied to actions inside Startup Ideabase—filtering ideas, matching skills, and checking research—not abstract slogans about hustle.

Pick one idea path, talk to three humans who feel the problem, and write a kill criterion with a date. Skip new tooling until that is done.