I was one of the first users of Scriptgun, and it helped our development team to save time.
Using Scriptgun I managed to get the most complete, custom and useful starter for my back-end in less than a few minutes. Hell, you can use it for V2 as well.
By looking at it from the presentation video it looks like an interesting idea but which doesn't work very well in reality nor does it scale.
I doubt there would be developers, who would rather click hundreds of times to generate some code. It seems like a tool which a PM would use or maybe a QE.
Developers like CLIs and in general things they could automate such as scripts, clicky interfaces not so much.
Just to give you an example, I'd rather write my own swagger file in yaml and put that through some tool to generate the code for an API, rather than click through a bunch of interfaces.
Also looking at the code generated presented, there seem to be some inconsistencies and also certain targeted frameworks such as Mongoose. The code style/formatting is assumed which may not necessarily follow the standards assumed by a team.
I think you need to start working backwards, what is exactly the problem you are trying to solve for your potential client and go from there.
I think scriptgun is a product any developer could use to gain more time on his hands for his projects.
