Business & Strategy
Section 1
Core Idea
The first version ships the idea; the real value is built in every iteration that follows. V1 proves the concept works; V1.1 through V100 prove the team can learn and compound. Most founders overestimate V1 and underestimate the long grind of refinement. Amazon's early website, the first iPhone, the original Shopify storefront — all functional, all far from what they became. The lesson: shipping V1 is necessary but not sufficient. The compounding value comes from feedback loops, bug fixes, UX improvements, and feature refinement done week after week. The best companies treat V1 as the starting gun, not the finish line.
Free playbook
Get The Business Model Playbook
58 business models, one visual page each: how the money flows, the metrics that matter, and who runs it. Free when you join the Faster Than Normal email.
Free. No spam. Unsubscribe anytime.
Section 2
How to See It
Building & Scaling
You're seeing Most Value Created After V1 when a product looks mediocre at launch but improves relentlessly — weekly releases, responsive bug fixes, feature refinements based on user feedback. The V50 product barely resembles V1.
Strategy
You're seeing it when competitors launch a flashy V1 and stall, while the winner keeps iterating. The gap widens not from a better launch but from a faster learning loop.
Section 3
How to Use It
Ship V1 fast to get real feedback. Then treat every week as a build cycle: prioritise by user signal, ship improvements, measure. Resist the urge to plan a big "V2" rewrite. Instead, compound small improvements. The team that ships 100 small improvements beats the team waiting to ship one big update.
Decision filter
"Are we treating V1 as the starting line or the finish line? Is our iteration cadence fast enough that value compounds weekly?"
As a founder
After V1, set a weekly ship cadence. Prioritise by customer feedback and usage data. Resist "big rewrite" projects; most value comes from hundreds of small improvements. Track iteration velocity as a core metric — the team that learns fastest wins.
Section 5
Founders & Leaders
Jeff BezosFounder & Executive Chairman, Amazon
Amazon's V1 was a bare-bones bookstore — ugly, limited, functional. Bezos treated launch as the starting line. What followed was relentless iteration: reviews, recommendations, 1-Click, Prime, AWS. Each cycle compounded value on the one before. Bezos institutionalised the practice with mechanisms like the weekly business review. Founders can adopt the same frame: ship V1 to learn, then build the company through thousands of post-launch iterations. The moat isn't the launch — it's the velocity of improvement after it.
Section 7
Connected Models
Reinforces
MVP
MVP gets V1 out the door fast. Most Value Created After V1 is the sequel: once the MVP ships, the real work — and real value — is in every iteration that follows.
Tension
Version Two is Lie
Version Two is Lie warns against promising a big future rewrite. Most Value Created After V1 agrees: don't wait for V2 — iterate continuously on V1. The tension is between incremental improvement and the temptation of a clean-sheet restart.
Leads-to
Iteration Velocity
If most value is created after V1, then iteration velocity — how fast you ship improvements — is the core lever. Faster cycles mean faster compounding. Measure and protect it.
Section 8
One Key Quote
— Jeff Bezos, 1997 Letter to Shareholders"This is Day 1 for the Internet and, if we execute well, for Amazon.com. Today, online commerce saves customers money and precious time. Tomorrow, through personalisation, online commerce will accelerate the very process of discovery."
Section 11
Summary & Further Reading
V1 ships the idea; the real value compounds through every iteration after launch. Ship fast, then improve relentlessly. Resist big rewrites; favour small, frequent improvements that compound over time.
01
Book
Build-measure-learn loops and the case for continuous iteration over big releases.
02
Book
Amazon's iteration culture: mechanisms, metrics, and the discipline of post-launch improvement.
03
Book
The engineering practices that enable fast, safe iteration after V1.