I think the easiest thing is build what you need. So that if it failed to make money, you still have the tool you want. I build https://noty.im https://noty.im

I think the easiest thing is build what you need. So that if it failed to make money, you still have the tool you want. I build https://noty.im https://noty.im that way, an monitoring tool that call me when my site is down. Then I realized more thing is needed and I started to add more features and plan to publish launch soon. I will say not to worry about scale and technical first. I learned it the hardway, Just get it out. No one will really care if it's broken or something doesn't owrk when you doesn't have lots of customer. So to answer your questions: 1. Can you provide some ideas on where to start? Pick a technology stack you familiar with. Apply to Microsft BizSpark to take advantage of $150/monthly credit. Learn FE, it isn't that hard. 2. What are some simple things I can build by myself? Any idea? I build `https://kolor.ml` https://kolor.ml` in a sunday. It's very simple but I need it. So you can try to build some simple/small utility that helps people with their daily live such as: a tool to call people up in morning. A tool to check if my site has expose some particular header such as `nginx`, `php version` etc and if found an old one or vulnerable one, alert. Of course, lots of people already build those, but the point is just get started, along the way you will realize what you really want to build