Micro-SaaS

Two things have made micro-SaaS more reachable. Cloud tools handle hosting, payments and email without a team. AI coding tools, often called vibe coding, let a non-engineer build a working first version in weeks. That makes the hard part not the building but choosing a problem that people will pay to solve and reaching them cheaply.

The same smallness is the risk. A narrow market has a ceiling. One platform change, such as an API the product depends on being closed, can end it. Support lands on the same person who builds and sells.

• Pick a problem you can see customers having today, ideally one they already pay to solve badly.
• Ship a small MVP and charge from the start.
• Keep support cheap with clear onboarding, documentation and automated emails.
• Watch churn closely. Small products are sensitive to losing a few customers.
• Say no to features aimed at a different customer.

SaaS means software sold as a subscription over the internet. A micro-SaaS is the same model at a deliberately small size. One person or a handful of people serve a narrow niche with a product that solves one problem well. Typical examples are a reporting add-on for one accounting tool, an invoice reminder tool for freelancers, or a scheduling widget for a single type of clinic.

Most micro-SaaS products are bootstrapped. They do not raise outside money and are not trying to become a large company. The aim is a profitable product that fits around the owner's life.

• Building before checking demand. Months of work go into a tool that nobody pays for. Ask ten likely users for a commitment first.
• Choosing a niche that is too small. If the whole market is a few hundred people, the ceiling arrives quickly.
• Depending on one platform. A product that lives inside someone else's API can be ended by a change to that API.
• Pricing too low. A low price means many customers are needed to cover support time. Test a higher price early.
• Ignoring support. Support is the owner's time. Without documentation and automated emails, it takes over the week.
• Adding features for a different customer. Each one widens the product and slows the work that matters.