Launch a Micro-SaaS
8 weeks · 3 milestones
Build and ship a focused tool that solves one problem for one audience.
Milestone map
Milestone map
3 milestones
Identify the specific, narrow problem your micro-SaaS will solve and begin building in public. Micro-SaaS is defined by a specific constraint: the entire product should be buildable by 1–2 people, serve a clearly bounded audience, and charge a recurring subscription. The 'build in public' requirement exists because the feedback loop before launch is the most valuable phase of a micro-SaaS: people who are interested in the problem will comment, pre-register, or challenge your assumptions — which is better signal than private development. Building in public means publishing at least one update about the product (on Twitter/X, LinkedIn, an indie-maker community, or a newsletter) before the product ships.
Proof required
Share a written description of the problem you are solving: the specific audience (not 'small businesses' but 'solo email marketing consultants who use Mailchimp but don't have time to A/B test their own campaigns'), the specific friction they experience, and why existing solutions don't solve it. Share a link to or screenshot of at least one public build update you have published — a tweet, a post on IndieHackers, a LinkedIn post, or a newsletter update.
What gets checked
- The audience is specific enough that a stranger could name whether they are in it.
- The friction is named precisely — 'they don't have time to X' is weaker than 'they can't do X without Y, which takes Z hours, and the cost of that time exceeds the cost they're willing to pay for a tool'.
- At least one public build update is shared — the link or screenshot must be from a real public post.