1. your video demo's music is way too loud. blasted my apartment in the early morning and added nothing to the demo. i'd take a shitty loom video with your narration saying whats happening over this.
2. you'll have to overcome quite a lot of skepticism that this works beyond an initial demo. your video shows a very standard greenfield setup that doesnt really need AI to do. how does it handle more interesting change requests of an existing app? how does it handle fullstack changes? how does it handle design? if you could include sample output (or links to generated diffs) on your landing page you might start to deal with that cynicism.
3. how are you thinking about defensibility? if this works it can be easily copied.
4. beyond this, the business model challenge i would fear for you is this is really a use-once-and-done tool. 299/mo is not really high enough to sustain a biz for that. i guess you're very focused on making it a recurring need but you have your work cut out for you. good luck.
1. LOL! Sorry! Volume is tricky to get right. I'll fix this with my next video.
2. Agree 100%! Second bots are becoming more sophisticated, but the truth is I am still pretty early. The video on this post, and on the website, is actually about a month old. I had planned on making an updated video with more interesting scenarios, but I ran out of time! I will have an updated video within the next two weeks. I also need to show screenshots of sample outputs, agree 100%
3. Defensibility - I wouldn't say this can be too easily copied. I am building custom compilers at the feature level (the high level plan), compilers for individual files, and piecing this together with GPT-3 queries on the code base, and using GPT-3 to generate new files, and modify files. Other than that, that's all I got!
4. You are 100% right. If Second becomes just a really fancy starter kit, it won't be a great business. However, I have found that my early customers do not know all of the features that they need up front, and tend to configure features in second, and then do a lot of BE work and some tweaks, and then do another feature a few days later. So I think Second can be integrated into a normal product delivery workflow. Also, I plan to add other capabilities like AI code reviews, and auto upgrades and maintenance via bots
Lol you're not wrong. BUT I do want to take my time with the video. I might be slower than you – it would probably take me an hour+ to tweak it, and find a better song.
1. your video demo's music is way too loud. blasted my apartment in the early morning and added nothing to the demo. i'd take a shitty loom video with your narration saying whats happening over this.
2. you'll have to overcome quite a lot of skepticism that this works beyond an initial demo. your video shows a very standard greenfield setup that doesnt really need AI to do. how does it handle more interesting change requests of an existing app? how does it handle fullstack changes? how does it handle design? if you could include sample output (or links to generated diffs) on your landing page you might start to deal with that cynicism.
3. how are you thinking about defensibility? if this works it can be easily copied.
4. beyond this, the business model challenge i would fear for you is this is really a use-once-and-done tool. 299/mo is not really high enough to sustain a biz for that. i guess you're very focused on making it a recurring need but you have your work cut out for you. good luck.