Days 1-3: post the concept as a raw idea with no landing page or waitlist. Days 4-7: track which posts get engagement, who says they need it, and who DMs asking when it launches. If fewer than 10 people reach out unprompted, drop it.
When it applies: week 1, founder with some social presence
After two weeks ask: are people signing up without chasing, coming back on their own, paying without heavy convincing, and giving feedback? Yes to all four: continue. No to any: kill it unless the fix is obvious.
When it applies: early validation of each new product
He weighs signups that arrive while he is not tweeting or posting on Reddit far above launch spikes; organic inflow without promotion indicates real pull.
Spin up a landing page with V0 or Lovable containing a single email input and a 'Request Access' button, share it via DMs, tweets and Reddit, and count emails. No emails means skip to the next idea.
Tweet ideas, build MVPs, put them in real hands, and compare attention across them; the one that clearly beats your usual baseline (people chasing you in DMs) gets the focus.
Post that you're going to do something even if you haven't started or don't know how; it creates accountability and the reaction is a cheap validation test. With no audience, post it as a reply in an existing thread on the topic instead of on your own timeline.
When it applies: Zero or small audience; idea stage
He tweeted 'who would like this' for a directory of indie hackers, read 50 likes as validation, spent four months building it, and never monetized it. Put payment in from day one.
Instead of ongoing marketing he launches and watches how people react; a product with strong launch feedback and traction gets his full attention, while one that makes a couple of hundred dollars with no excitement just keeps running.
Build one core workflow (no dashboard, settings or polish) in weeks 1-2, give interested people free access in weeks 3-4 asking them to break it, then fix and ignore off-core requests in weeks 5-8. If they don't return a second time, keep iterating; target 5-20 paying users.
He argues that asking if someone likes an idea is pointless unless you ask if they'll pay; waitlist signups and liked tweets don't count. Learned after five products that earned nothing.
He posted a 27-word tease with no link and no product, then followed with a 'domain available' post, an 'I did it' post and the launch. His argument: a finished post gives people something to judge, an unfinished one gives them something to do (reply, guess, follow along).
When it applies: Pre-build or early projects; works best if you can ship quickly after the tease
He streams 2-8 hours of coding each morning; viewers debug his code, suggest headlines and request features, giving feedback before launch and keeping him shipping.
Pick a niche and positioning, recycle code, databases and components across products, and launch weekly; judge each by paid revenue, not downloads or active users.
When it applies: pre-PMF founders with reusable stack
Romàn ran an agency selling lead packages manually before writing software; it validated demand, funded him, and those same clients became Gojiberry's first users at launch.
When it applies: B2B ideas where the outcome can be delivered by hand
He never spends more than about a month on an unproven product; if the launch brings a little revenue but no excitement he keeps it live (no shutdown) but stops investing time.