How to check a micro SaaS idea before writing code
It is hard to tell whether a small tool idea solves a real painful problem or only gives a small convenience to a narrow group. Common advice says to check pain, how often the problem happens, and whether people will pay. In practice, those signals can be unclear.
Potential users may say they would pay, but a simple first version can still get no response. Before spending serious development time, lightweight tests can help filter ideas. Useful early checks include posting in niche forums to see whether people engage, making a simple with a , and doing the work manually for a few people before turning it into .
The open question is when to keep testing and when to commit to building a small version to learn from real use.
Key points
- Do not rely only on people saying they would pay.
- Early often looks at pain, , and willingness to pay.
- A with a can test basic interest before building.
- Doing the work manually can reveal whether the problem is real enough to .
- At some point, a small build may be needed because testing alone cannot prove .