This sounds like a lack of "founder-product fit". Why should you be the one to build this thing if you have little domain knowledge? Maybe you should tackle a different domain where you have more knowledge (or could build knowledge quickly).
That something can be money, or connections, or prospective customers.
(2) There is still "finding investment"
You need to be asking yourself how you can make that happen. Sales is one way. Delivering investors is another. If you have your own money, spend it on the team. Because at the end of the day, you either deliver product or you deliver cash. If all you deliver is the idea, then expecting engineers to build it for free is unreasonable.
I don’t disagree with the premise. I think you're spot on actually.
Maybe the practical answer is what you’re implying: go work at a serious tech startup, build credibility, stack capital, earn trust, and come back stronger.
Thanks again.
Just say you've been talking to AI, if that's what you've done. It feels highly unlikely that you've studied developer tooling for 3 years and struggle to implement your own tools.
I mean I’ve been reading whitepapers and architecture docs, trying to understand how these systems actually fit together and why they’re designed the way they are.
For me it was more of a "top of the iceberg" approach so that when I talk to a true engineer, I’m not speaking in vague product language.
You're spot on though about using AI to help this learning curve.
Thanks for the comment.