AI products keep racing from launch to launch. The version numbers climb, but real adoption rarely follows the hype. My take: version 3.0 is the first honest exam a product ever sits. If you pass there, you earn growth. If you fail, the hype train was just noise.
On Marketing Against the Grain, Kipp Bodnar and Kieran Flanagan laid out a clean, useful model for how products find their market. It’s simple, sharp, and right. Their versioning lens explains why so many launches burn bright and fade. As someone who’s built and marketed digital products for decades, I see their frame as a practical checklist for discipline and patience.
The Three Stops On The Road To Product-Market Fit
They described three phases that every serious product navigates. The names aren’t cute. They’re a mirror.
I often times think about like 1.0. This is for the AI tourists. They’re going to come, many are going to leave.
You get to your like 2.0 launch and this is for your true sort of early adopter… this is where they start pulling product out of you.
…you finally get to the point where you feel like you can launch a 3.0 and 3.0 is the first time you’re actually going really after the mass market.
That last part is the kicker. 3.0 is not a feature drop. It’s a demand test. Can your tool win with people who hate change? If the answer is no, your numbering does not matter.
My Take: Ship 3.0 When The Market Pulls, Not When Your Roadmap Pushes
I agree with their thesis, with one push: too many teams slap “3.0” on a roadmap milestone instead of a market milestone. A new UI, a faster model, a fresh integration—none of that means you are ready for the mainstream. The only signal that counts is behavior from users who are not already fans.
Here’s how I test that, informed by years in crypto, social, and SaaS:
- Are non-technical users completing real tasks without hand-holding?
- Do support tickets drop and satisfaction rise during growth, not after it?
- Is onboarding so obvious that instructions feel optional?
- Can a skeptic see value in one session?
If those answers are weak, you’re still in 2.0—and that’s fine. Stay there and let early adopters keep pulling features out of you. That pressure shapes the right product. Jumping ahead only creates churn you cannot win back.
Evidence That Backs The Model
Kipp and Kieran’s framing works because it respects user segments:
1.0 = Curiosity. The “tourists” poke, try, and leave. They reveal what’s interesting, not what’s durable. That signal is useful, but it’s noisy.
2.0 = Tension. Early adopters tolerate flaws and demand progress. Their asks feel relentless. Good. That grind builds the product’s spine.
3.0 = Friction. The masses do not care about your roadmap. They care about time saved, results gained, and zero headaches. If you can win here, you have a business.
Some will argue that speed to market matters more. I respect speed. But speed without sequence leads to waste. Shipping 3.0 before earning it gives you more users to disappoint. It expands the blast radius of your mistakes.
Practical Moves Before You Claim 3.0
Before you declare mass-market readiness, run a short, ruthless checklist.
- Strip features until the core job is the obvious path.
- Replace jargon with plain language everywhere.
- Cut clicks, steps, and choices by half.
- Instrument first-session success and track it weekly.
- Have a default template or workflow that works out of the box.
These steps force clarity. They lower friction for the people who do not want to learn your tool. That is the only audience that defines 3.0.
The Bottom Line
Version numbers are marketing. Adoption is reality. The Marketing Against the Grain crew is right: 1.0 and 2.0 are for learning. 3.0 is for proving you belong on the desktop of someone who does not care about your product’s story. Ship that only when behavior says you’re ready.
If you’re building right now, hold your fire. Tune your product with the users who demand more and forgive less. Earn the leap. When you finally hit 3.0, you will not need to say it. The market will.
Go test with skeptics this week. Cut friction. Watch the data. Then decide if your next release is a number—or a real step forward.
