Every product I’ve ever built, including all twelve at Vulpine Creations, went through the same progression. And the biggest mistakes I’ve seen — in my own work and in the 44+ startups I advised at the Startup Burgenland accelerator — always involved the same error: trying to be at Level 4 when the business needed to be at Level 2.
Understanding where your product is and where it should be prevents two costly errors: under-building (shipping something so rough it damages your reputation) and over-building (polishing something nobody has validated yet).
Here are the five levels and when to be at each one.
Level 1: Concept
What it looks like: A description, a sketch, a slide, a conversation. No working product exists. The concept lives in words and images, not in anything a customer can use.
Purpose: Communicate the idea well enough to test whether anyone cares.
What you need at this level:
- A clear one-sentence problem statement
- A description of the proposed solution
- A rough price point
- A way to present this to potential customers (a landing page, a pitch document, a conversation)
Key activity: Talking to potential customers. At Level 1, the only goal is to determine whether the problem is real and whether people would pay for a solution. You’re not building anything. You’re validating the problem.
Mistake to avoid: Staying at Level 1 too long. If you’ve had 10+ positive conversations confirming the problem, move to Level 2. More conversations without building is preparation as procrastination.
When to be here: The first 1-4 weeks of any new idea.
Level 2: Prototype
What it looks like: A working version that delivers the core value in the simplest possible way. Manual processes behind the scenes. Minimal interface. No edge case handling. It works for the main use case and nothing else.
Purpose: Test whether your solution actually solves the problem.
What you need at this level:
- The core function working reliably
- A way for customers to access and use it
- A payment mechanism
- A way to collect feedback
Key activity: Getting 5-10 real customers to use the product and watching what happens. At Level 2, you learn whether the solution you envisioned actually matches what customers need. This is where the concierge MVP and Wizard of Oz approaches live.
Mistake to avoid: Over-building. At Level 2, your product should take 1-3 weeks to create. If it’s taking longer, you’re including too much. Cut until it fits the timeline.
When to be here: Weeks 2-8 after the concept is validated.
Level 3: MVP (Minimum Viable Product)
What it looks like: A focused product that delivers the core value with sufficient quality that customers would recommend it. Still limited in scope, but reliable and usable within that scope.
Purpose: Test product-market fit. Do customers use it, pay for it, and tell others about it?
What you need at this level:
- The core function working excellently (not just reliably — excellently)
- Basic onboarding so new users can start without hand-holding
- Professional-enough presentation that it doesn’t undermine trust
- A feedback collection system
- Functional unit economics
Key activity: Scaling from 10 to 50-100 customers. Iterating based on feedback. Identifying whether product-market fit exists.
Mistake to avoid: Confusing “minimum” with “low quality.” The MVP mistake everyone makes is shipping something too rough. At Level 3, the core experience should be genuinely good.
When to be here: Months 2-6 of a validated product.
Level 4: Complete Product
What it looks like: A product that handles the main use case and the most common edge cases. Good design. Solid documentation. Multiple features that support the core value. It feels like a “real” product.
Purpose: Retain and grow the customer base. Enable word-of-mouth. Justify premium pricing.
What you need at this level:
- All major use cases supported
- Good-to-excellent design
- Comprehensive documentation or help system
- Customer support processes
- Marketing materials and social proof
Key activity: Growth, retention, and optimization. At Level 4, the product is proven. The focus shifts from “does this work?” to “how do we reach more people and keep them?”
Mistake to avoid: Reaching for Level 4 before Level 3 confirms product-market fit. If you build a complete product without confirming demand, you’ve invested months in something the market might not want. All that completeness is wasted.
When to be here: After product-market fit is confirmed, typically 6-18 months in.
Level 5: Polished Product
What it looks like: Best-in-class experience. Every detail refined. The product delights users. It’s the thing you’d be proud to show your most demanding critic.
Purpose: Competitive differentiation. Premium positioning. High retention and strong word-of-mouth.
What you need at this level:
- Exceptional design and UX
- Comprehensive feature set for your target market
- Robust infrastructure (speed, reliability, security)
- Brand alignment across every touchpoint
- Systems for quality control at scale
Key activity: Optimization and refinement. At Level 5, you’re squeezing performance out of an already-working machine. Incremental improvements compound into a significant competitive advantage.
Mistake to avoid: Spending forever at Level 5 at the expense of entering new markets or launching new products. Polish has diminishing returns. Know when good enough is good enough.
When to be here: After 100+ customers and strong product-market fit, typically 12-24 months in.
The Over-Building Trap
The most common mistake across all levels is being at a higher level than your business stage requires. This manifests as:
- Building a Level 4 product before Level 2 validation is done (months wasted on features nobody wanted)
- Designing Level 5 visuals for a Level 1 concept (polishing something that might get killed)
- Adding Level 4 documentation to a Level 3 MVP (premature investment in support infrastructure)
At Vulpine Creations, we were disciplined about this. Our first product was a strong Level 3 — excellent core function, minimal extras. Our later products reached Level 5 — every detail refined, packaging beautiful, instructions exceptional. But the later products earned that investment because the earlier products had proved the market.
Trying to skip levels doesn’t save time. It wastes time, because the learning that happens at each level informs the decisions at the next level. Level 2 teaches you what to build at Level 3. Level 3 teaches you what to refine at Level 4. Skipping means guessing.
The Under-Building Trap
Less common but equally dangerous: shipping at a lower level than the situation requires.
If you’re selling to enterprise customers, a Level 2 prototype won’t cut it. Enterprise buyers expect Level 3 or 4 quality. If you’re in a market with established competitors, a Level 1 concept pitch isn’t going to win business from someone using a Level 4 product.
Match the level to the context: your customer’s expectations, your competitive environment, and the maturity of your market.
How to Know Which Level You’re At
Run this diagnostic:
- Do you have paying customers? No -> You should be at Level 1 or 2. Yes -> Continue.
- Do customers recommend you without being asked? No -> You should be at Level 3. Yes -> Continue.
- Is your retention rate above 70%? No -> You should be at Level 3 or 4 (focus on why customers leave). Yes -> Continue.
- Are you the preferred choice in your category? No -> You should be at Level 4 or early Level 5. Yes -> You’re at Level 5.
This diagnostic prevents over-building by tying your development level to real business outcomes rather than your personal desire for perfection.
Takeaways
- Know your level. Concept, Prototype, MVP, Complete, Polished. Each has a specific purpose and a specific set of requirements.
- Don’t skip levels. Each level’s learning informs the next level’s decisions. Skipping means building on guesses instead of evidence.
- The most common mistake is over-building. Level 4 quality for a Level 2 stage wastes months. Match your investment to your validation stage.
- Use the diagnostic. Paying customers? Referrals? Retention? Category leadership? These questions tell you where you should be investing effort.
- The goal is to reach Level 3 as quickly as possible. That’s where product-market fit is proven. Everything before it is testing. Everything after it is scaling.
