What are the 7 stages of product development?
Written by
Passionate Designer & Founder
The 7 stages of product development are: ideation, research, planning, prototyping, testing, launch, and post-launch iteration. Most teams run this as a handoff chain. The smarter approach treats stages 6 and 7 as direct inputs into stage 1 for the next cycle, which changes how you resource each stage and what success looks like at each gate.
Stage 1, ideation, starts with a positioning question, not a features list. What gap does this product close, and for which specific buyer? Execution without strategy compounds nothing. Teams that skip positioning in ideation spend 18 months building a product that works perfectly and sells poorly.
Stage 2, research. Teams under pressure compress this to 2 weeks. For a product entering a competitive category, you need at minimum: 8 to 10 customer interviews, a competitive audit across 5 to 8 players, and a review of exit data from churned customers if the product already exists. Less than that and you're prototyping assumptions.
Stage 3, planning. The most common failure I see in vertical SaaS builds is a planning stage that produces a roadmap with no success criteria. What does a successful launch look like in numbers? Activation rate above 40%? Trial-to-paid conversion above 8%? Name it before you build.
Stage 4, prototyping. Build the lowest-fidelity artifact that tests your riskiest assumption. For a growth-stage company past €2M ARR, the riskiest assumption is usually not "can we build it" but "will paying customers change their workflow for it."
Stage 5, testing. Run this in parallel with late-stage prototyping, not after it. Five unmoderated sessions per round, two rounds minimum before any engineering investment.
Where launch and iteration go wrong
Stage 6, launch, is the first real data point. Track activation in the first 72 hours. If users aren't reaching the core value moment within 3 sessions, the onboarding has a structural problem, not a copy problem.
Stage 7, iteration. Most teams handle this operationally but not strategically. They iterate on what users ask for, not on what drives expansion revenue. The metric worth watching is which features cause accounts to upgrade, not overall feature usage. Those are rarely the same list, and confusing them is how you spend a quarter building things that feel productive and move nothing.
Across our 4x Awwwards-winning work, the pattern that separates products that compound from products that plateau is whether the design system from stages 4 and 5 holds through 12 months of sprints without drift. When it degrades, you get inconsistent UI, fragmented positioning, and onboarding flows that each feel like a different company built them. For scale-ups where marketing funnel design and product UI need to share one design language, the product design process can't run as a silo. It's genuinely one of the more avoidable problems I see, and it almost always traces back to a planning stage that never defined what "done" looks like at scale. When you're mapping your next development cycle, book a 20-min intro. For the full guide, read our product design process overview.
