Startup MVP Checklist: 27 Things to Do Before Building

Most founders rush into building without validating their idea first. We've seen it happen dozens of times: months of development, thousands of dollars spent, and a product nobody wants. The difference between startups that succeed and those that don't? They follow a rigorous preparation process before writing code.

Phase 1: Market Validation (Weeks 1-2)

1. Define Your Target Customer

You can't build for "everyone." Get specific about who you're serving:

• Create detailed customer personas (age, income, location, pain points)
• Identify where they hang out online and offline
• Document their current solutions and why they're inadequate
• Understand their buying behavior and decision-making process

2. Conduct Customer Interviews

Talk to at least 20-30 potential customers before building anything. Ask:

• "Walk me through how you currently solve this problem"
• "What's the most frustrating part of your current process?"
• "How much time/money does this problem cost you weekly?"
• "Would you pay for a solution? If so, how much?"

Red flag: If they say "that would be great" but won't commit to paying, you have a nice-to-have, not a must-have.

3. Analyze Your Competition

Even if you think you have no competitors, you do. Map out:

• Direct competitors (same solution, same problem)
• Indirect competitors (different solution, same problem)
• Status quo (doing nothing, manual spreadsheets)

Document their pricing, features, reviews, and where they're falling short. This reveals your differentiation opportunities.

4. Validate Willingness to Pay

Don't assume people will pay. Test it:

• Create a landing page with pricing and measure sign-ups
• Run a pre-order campaign (even if you're not ready to build)
• Offer beta access in exchange for committed payment
• Get letters of intent from potential enterprise customers

Phase 2: Product Strategy (Week 2-3)

5. Define Your Core Value Proposition

Complete this sentence in one clear statement:

"[Product] helps [target customer] solve [problem] by [unique solution], resulting in [specific benefit]."

If you can't articulate this simply, you're not ready to build.

6. Identify Your One Killer Feature

Your MVP has one core feature that delivers your primary value. Everything else is secondary. Ask:

• "If users could only have one feature, which would make them keep paying?"
• "What problem does this feature solve that nothing else does?"
• "Can we build and test this in 4-6 weeks?"

7. Create a Feature Priority Matrix

Categorize every potential feature:

MUST HAVE (MVP only)
├── Core value delivery
├── Essential user flow
└── Basic analytics

SHOULD HAVE (V2+)
├── Nice-to-have improvements
├── Secondary user segments
└── Integration requests

COULD HAVE (Maybe someday)
├── "Would be cool" features
├── Advanced customization
└── Gamification

DON'T HAVE (Not now)
├── Enterprise features
├── Multi-language support
└── White-label options

8. Define Success Metrics

What does success look like? Define your North Star metric and supporting KPIs:

• North Star: One metric that captures core value (e.g., "active users completing core action")
• Activation rate: % of users who experience the "aha" moment
• Retention: Day 1, Day 7, Day 30 retention rates
• Conversion: Free-to-paid conversion rate
• Unit economics: CAC, LTV, payback period

Phase 3: Technical Planning (Week 3-4)

9. Choose Your Tech Stack

Don't over-engineer. For most MVPs, we recommend:

10. Design Your Database Schema

Even for simple apps, think through your data model:

• Core entities and their relationships
• Required fields for MVP vs. future features
• Indexing strategy for performance
• Data retention and cleanup policies

11. Map User Flows

Document every user journey from signup to core value delivery:

• Onboarding flow (keep it under 3 steps)
• Core action flow (the thing they came to do)
• Edge cases (what happens when things go wrong?)
• Error states and recovery paths

12. Plan Your API Architecture

Even if you're using a backend-as-a-service, think about your API:

• REST vs. GraphQL (REST is simpler for MVPs)
• Authentication strategy (JWT, OAuth, session-based)
• Rate limiting and security considerations
• Webhook requirements for payments/events

Phase 4: Business Foundation (Week 4-5)

13. Choose Your Business Model

How will you make money? Common models:

• Subscription: Monthly/annual recurring revenue
• Usage-based: Pay per transaction, API call, or feature
• Freemium: Free tier with paid upgrades
• One-time purchase: Traditional software licensing
• Marketplace: Take a cut of transactions

14. Set Your Pricing Strategy

Price based on value, not cost. Test different price points:

• Anchor with a premium tier to make mid-tier attractive
• Consider annual discounts (15-20% off drives cash flow)
• Factor in your target CAC and LTV
• Plan for price increases as you add features

15. Legal and Compliance Basics

Don't skip these:

• Business entity formation (LLC vs. C-Corp)
• Terms of Service and Privacy Policy
• GDPR/CCPA compliance if handling EU/California data
• PCI compliance for payment processing (Stripe handles this)
• Industry-specific regulations (HIPAA for health, etc.)

16. Set Up Essential Tools

You'll need these from day one:

• Analytics (Google Analytics, Mixpanel, or PostHog)
• Error tracking (Sentry)
• Support (Intercom, Zendesk, or simple email)
• Email marketing (Resend, Mailchimp, or ConvertKit)
• Project management (Linear, Notion, or Trello)

Phase 5: Go-to-Market Planning (Week 5-6)

17. Define Your Distribution Channels

How will users find you? Most successful startups use 2-3 channels:

• Content marketing: Blog, SEO, video content
• Social media: Where your audience hangs out
• Community building: Reddit, Discord, Slack communities
• Partnerships: Complementary products, influencers
• Paid acquisition: Ads (only after organic works)

18. Build a Pre-Launch List

Don't launch to zero people. Build momentum:

• Create a landing page with email capture
• Offer early-bird pricing or exclusive features
• Reach out to your network and ask for referrals
• Post in relevant communities (without spamming)
• Aim for 100+ emails before launch

19. Plan Your Launch Sequence

Launch is a week, not a day. Plan:

• Week 1: Soft launch to beta users
• Week 2: Public launch on Product Hunt, Hacker News
• Week 3: Follow-up content, case studies, testimonials
• Week 4: Paid campaigns, partnership announcements

20. Prepare Your Marketing Assets

Have these ready before launch:

• Social media posts (Twitter, LinkedIn, Instagram)
• Email sequences (welcome, onboarding, nurture)
• Press kit (logos, screenshots, description)
• Demo video (2-3 minutes max)
• FAQ document

Phase 6: Operational Readiness (Week 6-7)

21. Document Your Processes

Write down how things work:

• Customer support workflows
• Onboarding and activation processes
• Escalation paths for critical issues
• Content creation and publishing schedule
• Feature request and prioritization process

22. Create Your Support System

Be ready for user questions:

• FAQ page with common questions
• Onboarding tutorials or tooltips
• Support email or chat widget
• Knowledge base or help center
• Response time expectations (be realistic!)

23. Plan Your Feedback Loop

Collect and act on user feedback:

• In-app feedback widget (Typeform, Tally, or custom)
• Regular user interviews (schedule 2-3 per week)
• SMS/NPS surveys at key moments
• Feature voting system for roadmap transparency
• Weekly team review of all feedback

Phase 7: Team and Resources (Week 7-8)

24. Assess Your Team Skills

Be honest about what you can build:

• What can you build yourself?
• What requires a specialist (design, DevOps, etc.)?
• What should you outsource or use a service for?
• Where do you need a co-founder or advisor?

25. Budget Your Resources

Calculate your runway:

• Development costs (your time or contractor fees)
• Infrastructure costs (hosting, databases, APIs)
• Marketing budget (content, ads, events)
• Legal and administrative costs
• 3-6 months of operating expenses as buffer

26. Set Your Timeline (With Buffers)

Everything takes longer than you think:

• Estimate each feature's development time
• Add 50% buffer to your estimates
• Build in testing and bug-fixing time
• Account for marketing and launch preparation
• Plan for post-launch iteration and improvements

27. Define Your Next Milestones

What happens after launch?

• Week 1-4: Stabilize, fix bugs, improve onboarding
• Month 2-3: Add first major feature based on feedback
• Month 4-6: Scale marketing, optimize conversion
• Month 6-12: Expand to new segments or features

The Cost of Skipping This Checklist

Founders who skip this preparation typically experience:

• Feature creep: Building 3x more than needed, missing deadlines
• Wrong priorities: Spending months on features users don't care about
• Pricing mistakes: Underpricing because they focused on costs, not value
• Launch failures: Zero traction because they had no distribution plan
• Runway exhaustion: Running out of money before finding product-market fit

At Axiosware, we've seen founders who spent 6 months building without validation try to pivot after launch. Those who followed a rigorous prep process typically ship in 4-8 weeks and get traction immediately.

Ready to Build Your MVP?

This checklist is comprehensive, but you don't have to do it alone. At Axiosware, we've helped founders navigate this exact process for 24+ products, from pre-seed startups to established companies launching new platforms.

Our Launchpad package includes everything in this checklist plus expert guidance through validation, strategy, and build. Most clients ship their MVP in 4-6 weeks with a product that's ready for market from day one.

Want a printable version of this checklist? Download our free MVP Checklist PDF and track your progress as you prepare to build.