0→1: Why Keeping Things Vague Is a Feature, Not a Bug
Founders who have everything figured out at week two are usually wrong by week eight. Intentional vagueness early on isn't a weakness — it's the posture that lets you learn.
Quick Answer
At 0→1, keeping things intentionally vague isn't laziness — it's strategy. You don't lock down positioning, pricing, or features early because you haven't yet learned what's true. The goal is to know what you're testing next, not to finalize what you can't yet prove.
Why Early Certainty Is a Red Flag
Founders who have everything figured out at week two are usually wrong by week eight. The early product map — the one that seems obvious before you talk to users — almost never survives contact with reality. Locking it down early doesn't make it right; it just makes it harder to update.
Keeping things vague on purpose means staying in a learning posture. It means your positioning, your ICP, and even your core feature set are hypotheses, not decisions. That's the right framing for 0→1, where almost everything is uncertain and speed of learning matters more than conviction.
What Should Stay Vague (and What Shouldn't)
The things that should stay flexible: exact pricing, long-term feature roadmap, channel strategy, target vertical. These need real data before they're worth fixing.
The things that should be clear: the problem you're solving, the person you're solving it for, and the one assumption you're testing right now. Vagueness in strategy is fine. Vagueness in the next experiment is what kills momentum.
The One Question That Replaces a Roadmap
Instead of asking “what are we building?” at 0→1, ask “what's the most important thing we don't know yet, and what's the cheapest way to find out?” That question keeps the team focused without pretending you have answers you don't have.
Frequently Asked Questions
What should be vague at 0→1 and what should be clear?
Keep vague: exact pricing, long-term feature roadmap, channel strategy, target vertical. Keep clear: the specific problem you're solving, who you're solving it for, and the one assumption you're testing right now. Vagueness in strategy is fine. Vagueness in the next experiment kills momentum.
How do you avoid directionlessness when keeping things vague?
Replace the roadmap question ("what are we building?") with the learning question ("what's the most important thing we don't know yet, and what's the cheapest way to find out?"). This gives direction without false certainty. The goal at each stage is to reduce the most dangerous uncertainty, not to finalize everything.
When should founders start locking things down?
Start locking things down when you have repeated, consistent evidence — not one data point. Pricing should be tested before it's fixed. ICP should be validated before it's committed to. A useful signal: if you've seen the same pattern in five to ten conversations, it's worth acting on. One or two is still a hypothesis.
Stop doing this manually
Land & Convert monitors it for you.
Real-time alerts when your ideal buyers post on Reddit, X, TikTok, or Threads. Join 127+ founders on the early access list.
Get Early Access