30-Day Micro-SaaS

--- ## Who this is for You are a technical or semi-technical founder who wants to build a micro-SaaS but is tired of 6-month builds that never launch. You are time-bound, willing to ship ugly, and expect AI tools to handle most of the work. You have shipped side projects before but never turned one into recurring revenue. If you are a non-technical founder with no code background, this book is too advanced. If you are running a 50-person SaaS, this book is too small. ## What you'll have after reading - [ ] A validated niche picked in 3 days (not 3 months) - [ ] A landing page that converts visitors to waitlist signups - [ ] An MVP built with Cursor + Claude Code in 14 days - [ ] A pricing ladder ($19/$49/$149) - [ ] A launch week content calendar - [ ] A growth loop that hits $1K MRR by day 30 - [ ] The decision framework: stay solo vs. hire a contractor --- # Chapter 1 — The 30-day micro-SaaS math Why 30 days? Because the Indie Hackers data shows that founders who ship within 30 days are 3-5x more likely to reach $1K MRR than founders who take 90+ days. Speed compounds. Every week you spend "perfecting" is a week you could have been learning from real users. ## What changed in 2025-2026 The shift is structural, not incremental: - **Base44 (Maor Shlomo)** — solo-built vibe-coding platform, 250K users in 6 months, sold to Wix for $80M cash + $90M earn-out. Source: https://greyjournal.net/hustle/grow/solo-founders-million-dollar-ai-businesses-2026 - **44% of profitable SaaS** are now solo-founded, per the Stripe 2024 Indie Founder Report. Source: https://appkodes.com/blog/one-person-indie-saas-projects-built-using-ai/ - **1 in 3 indie SaaS founders** use AI for more than 70% of their dev and marketing workflows. Source: https://appkodes.com/blog/one-person-indie-saas-projects-built-using-ai/ - **Median time to first revenue** for bootstrapped micro-SaaS is 3-4 months. Validate-before-build founders reach first revenue 40% faster. Source: https://superframeworks.com/articles/best-micro-saas-ideas-solopreneurs ## The math behind 30 days | Phase | Days | Output | |---|---|---| | Validate | 1-3 | Niche picked + waitlist page live | | Build | 4-14 | MVP shipped with 3-5 core features | | Launch | 15-18 | First 10 paying customers | | Grow | 19-30 | $1K MRR + first growth loop | 30 days is tight but realistic for an MVP that solves one problem for one ICP. It is NOT realistic for a full-featured platform. ## The 4-week sprint structure The sprint follows the standard Lean Startup methodology, accelerated: 1. **Week 1: Validate.** Pick the niche. Build the waitlist page. Get 50 email signups. 2. **Week 2: Build.** Ship the MVP. Use AI coding tools. Get 3-5 users to test. 3. **Week 3: Launch.** Public launch. First 10 paying customers. Iterate on feedback. 4. **Week 4: Grow.** Optimize pricing, run paid ads, build the referral loop. By day 30, you should have: a working product, 10+ paying customers, $1K MRR, and a clear next-90-day plan. ## What the 30-day sprint is NOT It is not: - A complete product with 20+ features - A polished UI that wins design awards - A scalable backend that handles 100K users - A team of 5 engineers shipping in parallel It is: - A working MVP that solves one problem - An ugly UI that gets the job done - A backend that handles 100 users (you scale later) - A solo founder shipping fast The discipline: ship the smallest thing that delivers value, then iterate. ## The MRR target $1K MRR by day 30 means: - 50 customers @ $20/mo, OR - 20 customers @ $50/mo, OR - 7 customers @ $149/mo The right mix depends on your ICP. SMB SaaS buyers ($20-$50/mo) hit 50 customers faster. Prosumer or B2B buyers ($149/mo) hit fewer customers but higher total. ## Do this in the next 48 hours 1. Open `templates/04-30-day-micro-saas-templates/01-niche-scorecard.md`. Fill in 5 candidate niches. 2. Score each on the 5-criteria framework. 3. Pick the top one. Build the waitlist page by Sunday. --- # Chapter 2 — Days 1-3: Pick the niche The biggest predictor of $1K MRR by day 30 is whether you picked the right niche. Most founders spend 6 months on the wrong niche, then 6 more months on the next one. The 30-day sprint forces you to pick fast and validate harder. ## The 5-criteria niche filter Score each candidate niche 1-5 on these 5 criteria. Total above 20 = ship it. Below 16 = skip it. | # | Criterion | What to ask | |---|---|---| | 1 | **Pain intensity** | How acute is the problem? Are people paying for bad solutions today? | | 2 | **Buyer clarity** | Can you name 10 specific people who have this problem right now? | | 3 | **Distribution access** | Do you have a channel to reach them (Twitter, Reddit, newsletter, community)? | | 4 | **Build feasibility** | Can you ship an MVP in 14 days with current AI tools? | | 5 | **Willingness to pay** | Have you seen people pay $20+/mo for adjacent solutions? | ## The niche sources Where to find candidate niches: 1. **Your day job.** What's the most painful recurring task? Build a tool for that. 2. **Reddit pain posts.** Search r/Entrepreneur, r/SaaS, r/IndieHackers, r/smallbusiness for "I wish there was a tool that..." posts. 3. **G2 / Capterra complaints.** Read 1-star reviews of competitors. Find what users complain about. 4. **IndieHackers "what to build" threads.** The community surfaces problems constantly. 5. **Your own workflows.** What do you do manually that could be automated? ## The 10-person outreach Before committing to a niche, reach out to 10 people who match your ICP: ``` "Hey [name] — quick question. I'm thinking about building [a specific tool]. Would you use it? If so, what would you pay? If not, why not? No pitch, just validating before I build. 2-min reply appreciated." ``` Send 10 of these. If 5+ say "yes, I'd use it," you have a real niche. If 3 or fewer say yes, pick a different one. ## Common niche mistakes 1. **Too broad.** "Tool for small businesses" is not a niche. "Tool for solo lawyers to track billable hours" is. 2. **Too trendy.** AI wrapper #247 is a niche only if you have a unique angle. 3. **No buyer.** "Tool for hobbyists" — hobbyists don't pay. B2B SMBs do. 4. **Saturated market.** If 10+ competitors already exist with $1M+ ARR, you need a wedge. 5. **Personal interest over market signal.** "I love X" is not a niche. "10 people told me they'd pay for X" is. ## Do this in the next 48 hours 1. List 5 candidate niches. 2. Score each on the 5 criteria. 3. Email 10 ICP-matched people about each top-2 niche. 4. Pick the winner by Sunday. --- # Chapter 3 — Days 4-7: Validate before you build The Lean Startup rule: 40% faster to first revenue when you validate before building. The 30-day sprint respects this — days 4-7 are pure validation, no code. ## The waitlist page Build a single-page site in 1 hour with Carrd ($19/yr), Framer free, or your own HTML. The page has: 1. **Headline** — What the tool does, in plain language. 2. **3 bullet points** — The 3 things it does. 3. **Screenshot or Loom** — Visual proof of concept. 4. **Email capture** — Single field, "Get early access." 5. **Footer** — Your name, contact email. That's it. No pricing, no features, no FAQ. ## The validation targets By day 7, you want: - 50+ email signups on the waitlist - 10+ survey responses confirming the pain - 3+ pre-orders at the launch price (or strong intent) If you hit these, build. If not, re-niche. ## The validation email sequence After signup, send 3 emails over 7 days: **Day 1 (immediately):** ``` Subject: You're on the [product] waitlist Hi [name] — Thanks for signing up. I'm building [product] to solve [specific pain]. Quick question: what's the most frustrating part of [problem] today? Reply with 1 sentence. [Your name] ``` **Day 4:** ``` Subject: Here's what [product] will do Hi [name] — Based on the responses so far, here's what [product] will do at launch: - [Feature 1] - [Feature 2] - [Feature 3] Anything missing? Reply with what you'd add. [Your name] ``` **Day 7:** ``` Subject: [name], want early access? Hi [name] — [Product] is launching next week. Want to be one of the first 10 users? I'll give you a 50% lifetime discount if you say yes now. [Calendly link] [Your name] ``` ## The manual fulfillment test Before building software, fulfill the service manually for 3-5 customers. If they pay and are happy, you've validated demand. If they don't pay or are unhappy, you've saved 14 days of building. The manual fulfillment can be: - Google Sheets + email for a "tool" - Zoom calls + summary docs for a "service" - Airtable + Zapier for a<p style="opacity:0.6;font-style:italic;margin-top:24px;">[Sample chapter — buy the book for the full 30-50 page edition]</p>