Building a #nocode platform is a lot of work. Especially for a #solofounder. Here's how I'm doing it.

1/6. I need to make some money on the project while the full nocode platform is being built. I've released "half" of the application as a #developer tool to auto generate a backend ( #nodejs #rest #api) without writing code.

2/6. Using developers as the user base for the initial product is not random. They're easier to teach nocode tools to because they already know about software development. Concepts like a database schema aren't foreign to them. This lowers the customer support burden

3/6. Since devs are already using the API generator and are interested in nocode. It's okay they have to write a little code, it just has to be easier than writing the whole project from scratch. (this is an assumption). This means I don't have to be % nocode out of the gates

4/6. Over time, I can slowly reduce the amount of code devs have to write while using the tool to achieve an outcome. It's the only iterative/incremental way I can see this happening.

5/6. If I can charge during this whole process, I can eventually hire developers to help speed up the process but I don't have to.

6/6. Being a solo founder with basically no overhead, this project can't be killed by external forces. Only I can kill it. Being unstoppable is an advantage.

Bonus. In 2 years I want to use this tool as the basis for launching a venture studio. We'll have our own team of nocoders testing and launching product after product, meticulously finding problems and delivering solutions.