Build a Mini-SaaS With One Real User
Maps to: Founder · Software Engineer, Product Manager, Marketer
You're going to build a single-feature web product, give it a landing page, and get one real person to actually use it. The skill is building for a real user: watching someone use your thing, then cutting everything that isn't what they needed. That's the founder instinct, finding someone with a problem and making them exactly what solves it, and doing one tells you fast whether building something people want is your kind of work.
The plan
0/5 doneYou're 17% in just for starting, the hardest part. Mark your first step done to keep the momentum.
Pick a niche problem you understand and the single feature that solves it. Name who has this problem. Write it down: this one-feature spec is what stops you from building a bloated thing nobody asked for.
Objective: A niche problem, a single feature that solves it, and a named user who has it.
- 1
Pick the problem: a pain you have / a tool for a community you're in / a 'replace one annoying spreadsheet' / a paid version of something free-but-clunky.
- 2
Write the single feature that solves it and who specifically has the problem.
Your call
Choose the niche problem and the single feature that solves it, and name who has it, yourself.
The pain, and the one feature that solves it.
What good looks like: Your spec is one feature for one named person with a real problem, tight enough that you'd notice if you started building something they didn't ask for.
- One feature. SaaS dies of feature bloat; yours survives by doing one thing.
- 1
The bar to look back against
A deployed single-feature product with a landing page and at least one real, active user you onboarded and watched, and you cut the product to the one thing they actually needed. The user is the work: not 'I built software,' but 'a real person used it, and I cut it to what they needed.'
Finish the final step, then submit what you built. Your progress is saved.
Tools you'll use
Steps 2–5 · Build the product
Step 7 · Find one real user, and cut to what they needed
How this shows up on a resume or college app
I built and launched a micro-SaaS: a single-feature product with a landing page and one real user I onboarded and watched, then cut the product to exactly what they needed. I learned the difference between building software and building a product: it's one real user, and the discipline to cut everything else.