I love starter templates like this. But I have yet to use them in real products, because they are inherently opinionated. And I like my tech choices to be driven by product needs, not the ease of launch. I'm not philosophically opposed to using something like this, but my process is more along the lines of:<p>1) Define the product<p>2) Determine what features and functions are needed, and how it will influence architecture decisions.<p>3) Pick a stack to start with.<p>Normally, from node up to the front-end, I'm flexible, but these kits typically also are tied to specific databases, with specific auth solutions, and assumptions about the type of dev environment and flow that people want to see. If you are adding in billing and subscriptions, there are even more places we might end up on different pages.<p>Now, if the stack I choose ends up matching a solution like yours, terrific. I'll use it and be happy. But the more complete the solution, the less likely it is to be a match.