Stop Validating. Start Provoking.
Most startup ideas die because they're boring, not broken. Here's how to provoke reactions, get real users, and find out if your startup has a pulse — in 7 days.
Most startup ideas don't die because they're broken. They die because they're boring.
You spend weeks polishing, validating, tweaking... searching for permission. But permission doesn't build momentum. Provocation does. You need to find out if your idea has a pulse, if it can actually spark a reaction in the real world.
Forget the endless validation cycle. Here's how to provoke reactions, get real users, and find out if your startup has a pulse — all in 7 days. The indie hacker way.

Day 1: Test the Spark in Public
First things first: does the core idea even *resonate*? Go to lovable.dev. Plug in your startup concept. It spits out an instant landing page. No design headaches, no lines of code. Just pure vibes. Now, share that page. Everywhere. Watch the clicks, the comments, the *reactions*. If it's crickets? You have your answer. Move on. Next idea.
Day 2: Drop the Bait
Head to where your potential users hang out – X, Reddit, Discord. But don't pitch. *Provoke*. Share your idea with an edge. Try something like:
"I built this because every single tool in this space is fundamentally flawed."
"Is anyone else incredibly frustrated by X? I'm building Y to fix it."
See who bites. The replies, the arguments, the discussions – that's your goldmine. It tells you who cares, what resonates, and where the real pain points are.
Day 3–4: Code with Chaos in Mind
Okay, you've got a flicker of interest. Time to build. Fire up Cursor. Now, build the absolute *roughest* thing possible that demonstrates the core spark. The minimum viable provocation. Forget login forms. Forget polished UI. Forget edge cases. Ship the raw *idea*, not a finished product. If you're not slightly embarrassed by what you're releasing, you waited too long.
Day 5–6: Release to a Brutal Audience
This is where the real test begins. Drop your raw, chaotic creation onto IndieCrush. The beta testers and fellow developers here won't coddle you. They'll push it, break it, critique it, ignore it... or maybe, just maybe, they'll *love* it. They won't spare your feelings, and that's exactly what you need. Brutal honesty is the fastest path to learning.
Day 7: Survive or Restart
Time for the gut check. Look back at the week. Ask yourself:
- Did anyone *actually* get excited? Beyond polite nods?
- Did your provocation start a real conversation, or just fizzle out?
- Did you feel any genuine *momentum*?
Be honest. If the answer to these is 'no', don't cling to a dead idea. Kill it quickly and start over. You weren't looking for validation or permission.
You were looking for fire. Go find it.
Posted by
Related reading
Launching on Product Hunt: How Beta Feedback Makes or Breaks Your Day
Why your Product Hunt launch is won or lost in the beta phase before it, and how to use tester feedback to arrive ready.
From Feedback to Roadmap: How to Prioritize What Testers Tell You
A simple framework for turning a pile of beta feedback into a clear roadmap, including which feedback to ignore and why.
How Much Does Beta Testing Cost? Free vs. Paid Options Compared
A breakdown of what beta testing actually costs indie hackers, from free community recruiting to paid platforms and professional reviews.