It sounds like you don't know what you are doing. Don't be shocked, not knowing what you are doing and praying that a tech stack will do it for you is the norm

It sounds like you don't know what you are doing. Don't be shocked, not knowing what you are doing and praying that a tech stack will do it for you is the norm... by far. It can be done correctly and faster and cost less than alternative approaches. Here is how you do that: 1. Start with the end in mind. Know what you want from a product perspective and write that down. Most places are not capable of getting this correct. The more precisely you know what you want the less it will cost to build. 2. Know the platform. Most people have absolutely no idea how the front end works and are completely reliant upon some tool chain. A tool will allow setting up an application somewhat quickly in the absence of a plan, but again the costs will spiral up as you build it. This is why software is hard to estimate. If you don't know what you are doing then hire a temporary consultant to drive this bus. A framework or build tool is the most incorrect answer. 3. Automation. Supposedly software is written by software people and yet rarely are things well automated. You need centralized user-facing product documentation, test automation, code validation, accessibility, and such written in parallel to the actual product. If you know what you are doing this costs far less than you think. If you bolt it on later it will be extremely expensive and horribly incomplete. 4. Always remain focused on the product, the end state for the user. Most shops get this wrong too and instead think about their tools, code vanity, popular trends for hiring, and other irrelevant distractions. Focus. I hope this goes well for you.