Five hard lessons from building a $200 MRR micro SaaS side project

Executive overview

Building a B2C micro SaaS after years of B2B SaaS experience exposes blind spots that don't surface in enterprise products. The instincts that work for platform companies — broad transformations, daily use cases, scalable infrastructure — actively hurt micro SaaS products.

Five lessons emerged from building Sunday, a weekly planning app that reached $200 MRR: focus ruthlessly on one outcome, write emotion-first value props for B2C, identify the tightest possible product loop, avoid premature tech upgrades, and instrument a product-led flywheel from day one.

B2C buyers decide with emotion; B2B buyers rationalise with ROI — getting this wrong kills conversion.

Focus on one outcome, not a transformation

• B2B instinct pushes toward platform thinking — multiple features, daily logins, workflow takeover
• Micro SaaS converts better when it promises exactly one thing
• Sunday's single outcome: plan your week in 15 minutes, go into Monday with certainty
• Adding Pomodoro timers, monthly reviews, and extra resources confused users and diluted conversions
• The sales page, emails, and landing page should all point to that one outcome only

Craft an emotion-first value proposition for B2C

• B2B value props are ROI-driven: growth, risk reduction, cost savings
• B2C purchases are emotional — buyers decide on how they expect to feel
• "Unlock your best goals" underperformed; "feel certainty and clarity going into Monday" converted better
• Feelings — not features — are the hook: peace, certainty, having a plan
• Emotions are present in B2B too, but logic dominates; in B2C, emotion leads

Build the tightest possible core product loop

• B2B products need daily use cases and deep workflow integration
• B2C users want the emotional payoff, then move on — that's fine
• Sunday's core loop: make a weekly plan → Wednesday reminder of the plan → Sunday prompt to plan again
• Weekly cadence, not daily, was sufficient to create habit and retention
• Resist adding features until the core loop is proven

Avoid time wasters in the early stage

• Spent 48 hours trying to upgrade from Rails 6 to Rails 8 (gem updates, moving from Webpacker to JS bundling) — none of it mattered
• Tech stack is fine until you hit real scale or a security issue; migrate cleanly then, not before
• Infrastructure does not need to be infinitely scalable for a product designed for hundreds of users, not millions
• Separating the sales page into its own repo from the application enables fast iteration: A/B tests, analytics, no deployment risk
• Slow iteration cycles are a direct time cost — optimise for speed of experiment, not engineering elegance

Instrument a product-led flywheel from the start

• Micro SaaS price points ($9–$49/month) make sales-led growth uneconomical — the product must sell itself
• Sunday is priced at $29/month with a 30-day free trial; higher price enables ad spend if growth picks up
• The flywheel has five stages: acquisition → activation → revenue → retention → referral
• With a free trial, swap revenue and retention: users must be retained before they convert to paid
• Instrument all stages in a tool like Mixpanel; pick one metric to improve each week
• Current focus: increase trial sign-up rate, since activation and retention are already working adequately