What We Learned from Shipping 5 MVPs in 2 Months: Essential Lessons for New Founders
What We Learned from Shipping 5 MVPs in 2 Months: Essential Lessons for New Founders
As indie hackers and solo founders, we often find ourselves caught in the cycle of perfecting our ideas before actually launching. But what if I told you that shipping quickly can lead to better insights than months of planning? In early 2026, we took the plunge and shipped five MVPs in just two months. Here’s what we learned from that experience, including the tools we used, the costs involved, and the honest trade-offs we encountered along the way.
1. Start with a Problem, Not a Solution
Before diving into development, we spent time identifying real problems faced by our target audience. Each MVP was based on a specific pain point we validated through quick surveys and conversations.
Lesson: Validate Before You Build
- What We Did: We conducted 20 interviews with potential users to refine our ideas.
- Outcome: This saved us from building features nobody wanted.
2. Choose the Right Tools for Rapid Prototyping
The tools you choose can make or break your MVP shipping timeline. Here’s a breakdown of the tools we used, along with their pricing and limitations:
| Tool | What It Does | Pricing | Best For | Limitations | Our Take | |----------------|----------------------------------------|--------------------------|--------------------------------------|----------------------------------------|-----------------------------------| | Figma | UI/UX design and prototyping | Free + $12/mo pro tier | Designing interfaces quickly | Limited to design, not development | We use this for all UI designs. | | Bubble | No-code web app builder | Free tier + $29/mo pro | Building functional web apps | Performance can lag with complex apps | We built our first MVP here. | | Airtable | Database and project management | Free tier + $10/mo pro | Organizing data and project tracking | Not a full database solution | Great for quick data management. | | Zapier | Automation tool for workflows | Free tier + $19.99/mo | Connecting different apps | Can get pricey with many zaps | We automate repetitive tasks here. | | Stripe | Payment processing | $0-0.30 per transaction | Handling payments easily | Fees can stack up with volume | Essential for MVPs with payments. | | Notion | Note-taking and project management | Free tier + $8/mo pro | Documentation and collaboration | Not ideal for large teams | We use this for project tracking. |
What We Actually Use
- For design: Figma
- For web apps: Bubble
- For data: Airtable
- For automation: Zapier
- For payments: Stripe
- For documentation: Notion
3. Embrace the Minimum Viable Feature Set
When we built these MVPs, we focused on the absolute core features that solved the problem. This meant stripping away non-essential functionalities.
Lesson: Less is More
- What We Did: For our first MVP, we limited ourselves to just one feature that addressed the main pain point.
- Outcome: We shipped faster and gathered more useful feedback.
4. Launch Early, Iterate Often
We launched each MVP within two weeks of starting development. This quick turnaround allowed us to gather feedback and iterate in real-time.
Lesson: Feedback is Your Best Friend
- What We Did: After launch, we sent follow-up surveys to users within 48 hours.
- Outcome: We implemented user suggestions into the next iteration within a week.
5. Analyze Costs and Time Commitment
Shipping five MVPs in two months wasn’t without its costs. Here’s a breakdown of our investment:
- Total Time: Approximately 160 hours (32 hours per MVP).
- Total Cost: $400 (including tool subscriptions).
- Average Cost per MVP: $80.
Lesson: Budget Wisely
- What We Did: We kept a tight budget and used free tiers wherever possible.
- Outcome: This helped us stay lean and avoid unnecessary expenses.
Conclusion: Start Here
If you’re a new founder looking to break into product development, start by validating your idea, choose the right tools, and focus on core features. Remember, the goal is to ship quickly and iterate based on real user feedback.
You don’t need to be perfect; you just need to start.
Follow Our Building Journey
Weekly podcast episodes on tools we're testing, products we're shipping, and lessons from building in public.