Lesson 7 - Building and Deploying Your MVP

Use this template to plan your MVP: --- **Project Name:** [Your product name] **One-Sentence Pitch:** [Product name] helps [target user] to [do something] by [key differentiator]. **Example:** "02Ship helps non-programmers learn to build products by teaching them to use AI coding tools through hands-on courses." **The Problem:** - Who has this problem? [Be specific: 'non-technical founders', not 'everyone'] - How do they solve it today? [What's the alternative?] - Why is that solution insufficient? [The pain point] **The Solution (Your MVP):** - Core value proposition: [The ONE thing your MVP does really well] - How it works: [3-5 sentence explanation a 10-year-old could understand] **Key Features (3 Maximum):** 1. [Feature 1 - the absolute minimum to deliver value] 2. [Feature 2 - necessary for feature 1 to work] 3. [Feature 3 - nice to have if time permits] **NOT in the MVP (Save for V2):** - [Feature you want but don't strictly need] - [Polish that can wait] - [Integration that's not critical] **Success Criteria:** - Technical: [App runs, core flow works, no critical bugs] - User: [Can complete main task without confusion] - Metric: [Get X users to complete Y action] **Tech Stack:** - Frontend: [e.g., Next.js 14 + TypeScript + Tailwind] - Backend: [e.g., Supabase, or none (static site)] - Deployment: [e.g., Vercel] - Other: [Any critical integrations] **Timeline:** - Planning: [1 day] - Building: [3-5 days] - Testing & polish: [1-2 days] - Launch: [1 day] - **Total: 1 week maximum for first MVP** **Known Risks:** - [Technical challenge you're unsure about] - [Assumption that might be wrong] - [Resource you might not have] --- **After filling this out, ask yourself:** 1. Could I explain this to someone in 30 seconds? 2. Can I build this in a week without burning out? 3. Would even 10 people find this useful? If all yes → start building. If any no → simplify further.

**Best for Absolute Beginners:** **Option 1: Static Website** - HTML + CSS + vanilla JavaScript - Deployment: Netlify (drag & drop) - Best for: Landing pages, portfolios, simple tools - Pros: Simplest possible, no build process - Cons: Limited functionality, harder to scale **Option 2: Next.js + Vercel (Recommended)** - Next.js 14 (App Router) + TypeScript + Tailwind CSS - Deployment: Vercel (GitHub integration) - Best for: Most web apps, SaaS products, content sites - Pros: Claude knows it well, scales to complex apps, great docs - Cons: Steeper learning curve than plain HTML **Option 3: No-Code Tools** - Webflow, Framer, Carrd (for landing pages) - Bubble, FlutterFlow (for apps) - Best for: Maximum speed, no coding at all - Pros: Ship even faster, visual editing - Cons: Less control, harder to customize, costs add up **What NOT to Choose for First MVP:** ❌ Custom backend from scratch (use Supabase/Firebase instead) ❌ Mobile app (web first, mobile later) ❌ Blockchain/crypto integrations (complexity nightmare) ❌ Microservices architecture (you're not Netflix) ❌ Cutting-edge frameworks (stick to what Claude knows) **Our Recommendation:** Next.js + Vercel. Why? - Claude has excellent Next.js knowledge - Free hosting on Vercel - Scales from simple to complex - Huge community for help - Used by professionals (you're learning a real skill) **If Next.js feels too complex:** Start with plain HTML/CSS, ship that, then rebuild in Next.js for V2. Shipping imperfectly > not shipping perfectly.

**Day 1: Planning & Setup** 1. Fill out MVP Planning Template 2. Create a Project in Claude with your plan as custom instructions 3. Ask Claude: 'Review my MVP plan and suggest improvements' 4. Refine based on feedback 5. Create GitHub repo (optional but recommended) 6. Set up local dev environment (Lesson 4) **Day 2-3: Core Features** 1. Prompt Claude: 'Generate the initial project structure for [MVP]' 2. Run code locally, verify it works 3. For each core feature: - Prompt: 'Add [feature]: [specific requirements]' - Test the feature - Iterate if needed (simplify, expand, debug) 4. Commit working code after each feature **Day 4: Polish & Test** 1. Mobile responsiveness check (test on phone) 2. Add error handling ('what if user does X wrong?') 3. Basic loading states (spinners, skeletons) 4. Accessibility check (keyboard navigation, screen reader labels) 5. Copy/content review (fix typos, improve clarity) 6. Ask 1-2 people to test and give feedback **Day 5: Deployment Prep** 1. Add basic analytics (Vercel Analytics or Google Analytics) 2. Set up error tracking (optional: Sentry free tier) 3. Add meta tags for SEO and social sharing 4. Create README with setup instructions 5. Final test: does it work in production mode? (`npm run build && npm start`) **Day 6: Deploy & Launch** 1. Deploy to Vercel (connect GitHub repo) 2. Set up custom domain (optional) 3. Test live site on multiple devices 4. Fix any production bugs 5. Write launch post (Twitter, LinkedIn, relevant communities) 6. Share with 5-10 people directly for initial feedback **Day 7: Respond & Plan** 1. Respond to all feedback 2. Log bugs and feature requests 3. Prioritize what to fix vs. what to defer 4. Plan V1.1 improvements 5. Celebrate: you shipped! 🎉 **If You Get Stuck:** - Stuck <30 min: Debug with Claude - Stuck 30-60 min: Ask in Discord/community - Stuck 60+ min: Simplify the feature or skip it for V2 - Really stuck: Take a break, come back fresh Remember: Done is better than perfect.

**Technical Must-Haves:** - [ ] App runs without errors in production mode - [ ] Core user flow works end-to-end - [ ] Works on mobile (at least readable/usable) - [ ] No sensitive data (API keys) hardcoded - [ ] Basic error handling (not crashing on bad input) **Content Must-Haves:** - [ ] Clear value proposition on landing page - [ ] How-to instructions or onboarding - [ ] Contact or support info - [ ] About page or footer with context **SEO Basics:** - [ ] Title tags on all pages - [ ] Meta descriptions - [ ] Open Graph tags (for social sharing) - [ ] Favicon **Analytics:** - [ ] Basic analytics set up (Vercel Analytics or GA4) - [ ] Can track key user action (signup, usage, etc.) **Nice-to-Haves (Not Blockers):** - [ ] Custom domain (vs. yourapp.vercel.app) - [ ] Email capture for updates - [ ] Pricing page (if applicable) - [ ] Testimonials or social proof - [ ] Privacy policy (required if collecting data) **Launch Day:** - [ ] Announce on Twitter/LinkedIn with screenshot - [ ] Share in relevant communities (Reddit, Discord, forums) - [ ] Tell friends and ask for feedback - [ ] Post on Product Hunt (optional, can wait for V1.1) - [ ] Respond to every comment/message within 24 hours **Post-Launch (Week 1):** - [ ] Fix critical bugs immediately - [ ] Thank early users publicly - [ ] Document feedback (bugs, features, questions) - [ ] Prioritize what to build next - [ ] Plan V1.1 for 1-2 weeks out **Mental Checklist:** - [ ] I'm OK with this being imperfect - [ ] I'm shipping to learn, not to impress - [ ] Feedback is a gift, even when harsh - [ ] I can always improve it after launch - [ ] Today I'm a builder who ships

**Goal:** Get 10-50 people to try your MVP in the first week. **Where to Share:** **Twitter/X:** - Post with screenshot - Tell the story: 'Built this in X days using Claude' - Use hashtags: #BuildInPublic #IndieHacker #AI - Tag relevant accounts (but don't spam) **LinkedIn:** - Professional angle: 'Learning to build products with AI' - Share lessons learned - Ask your network for feedback **Reddit:** - r/SideProject (feedback focus) - r/IMadeThis (show and tell) - Niche subreddits related to your product - Follow sub rules (some ban self-promotion) **Discord/Slack Communities:** - Share in relevant channels - Ask for feedback, not just promotion - Offer to help others in return **Product Hunt:** - Wait until V1.1 (not bare MVP) - Or launch immediately for early feedback - Prepare: good description, screenshots, first comment **Indie Hackers:** - Post in 'Show IH' section - Share your build story - Engaged community, constructive feedback **Direct Outreach:** - Message 5-10 people who fit your target user - Ask for specific feedback: 'Does this solve [problem] for you?' - Offer beta access or free use **Launch Post Template:** 🚀 I just shipped [Product Name]! [One-sentence value prop] Built in [X days] using Claude + [tech stack]. Zero coding experience before this course. ✨ What it does: - [Key feature 1] - [Key feature 2] - [Key feature 3] 🔗 Try it: [yourproduct.com] I'd love your feedback! What works? What's confusing? What's missing? #BuildInPublic [other relevant hashtags] **What NOT to Do:** - Don't spam multiple subreddits in one hour - Don't claim it's 'perfect' or 'revolutionary' - Don't ignore negative feedback - Don't pay for fake upvotes/traffic - Don't compare yourself to others' launches **Success Metrics (Week 1):** - 10+ people tried it - 5+ pieces of feedback received - 1+ bug fixed based on real usage - Learned something that will inform V1.1 **Remember:** Your first launch won't go viral. That's not the goal. The goal is: ship, learn, iterate.

**MVP (Minimum Viable Product):** Smallest version of your product that delivers core value and can be tested with real users **Deployment:** Publishing your app so others can access it via the internet **Production:** The live environment where real users interact with your app (vs. development/testing) **Launch:** Making your product public and announcing it to get initial users **Iteration:** Cycle of shipping → learning → improving → shipping again **V1 / V2:** Version numbers (V1 = first launch, V2 = major update) **Analytics:** Tools that track how users interact with your product **Feedback Loop:** Process of collecting user feedback and using it to improve