13 posts
Building and launching alone
Choosing, building, charging for and launching a small software product on your own.
- How do you handle support for a SaaS on your own?
Answer in a slot, not all day, and read the questions for the feature they're asking for. Repeated questions are the best product research you'll get.
- How do you pre-sell software before you build it?
Ask named people for money for a thing that doesn't exist yet, with a date and a full refund if you miss it. Then open the payment account first, not last.
- How do you validate a micro SaaS idea before building it?
Run it through 7 questions in an hour, then ask 10 named people for money before you write any code. If nobody pays, you've saved a month.
- How does a developer find a niche they can sell to?
Look for a room you've already been sitting in. The best niche is a group whose problems you've watched for years and who'd notice if you stopped posting.
- How long should a solo MVP take to build?
7 days. If the smallest version that someone would pay for takes longer than a week, the idea is too big for one person to test.
- Should a new SaaS charge from the first day?
Yes. Free users prove that people like free things. A price on day one tells you in a week what a free tier hides for a year.
- What can AI agents do in a one-person business?
Labour you can check, such as reading, sorting and drafting. Not judgement. Hand an agent the decisions and it returns the average of everybody else's.
- What does a weekly routine for a solo SaaS look like?
One named slot per product, the same pages in the same order, and a line in the file each time. Mine is 2 hours on a Sunday for the biggest product.
- What is a kill rule for a side project?
A metric, a number, a date and an action, written before launch while you're still hopeful. It lets you stop a product calmly instead of watching it fade.
- What is the right order to launch a small product?
Warm to cold. The room where people know your name goes first, on day one, with your best post. Strangers come after, once they can see somebody cared.
- What should you ask before building a software product?
7 questions, in an hour, before any code. They came out of 25 dead products, and most of those deaths needed no new question.
- What should you do in the quiet month after a launch?
Talk to the people who signed up. Rewriting the landing page, adding features and relaunching are what everybody does instead, and none of them works.
- What tech stack should a solo founder use?
The dullest one you already know, written on one card and changed only in January. A new product should never also be a new stack.
Questions
- What does "Building and launching alone" cover?
- Choosing, building, charging for and launching a small software product on your own.
- Which book goes deeper?
- Ship Alone: The method: choose, build, charge for and launch a small product on your own, and know when to stop.
- How long are the posts?
- A few minutes each. Every one answers its question in the first two sentences, then gives the decision and what it costs.