Do not over complicate your stack. It will happen on its own. Building product is part product and part distribution (customer acquisition). The more establi

Do not over complicate your stack. It will happen on its own. Building product is part product and part distribution (customer acquisition). The more established or boring tech you use, the more time you have to understand the problem and needs and iterate more often and quicker. Often just using what you know isn’t as bad idea. It will shed a light on where you wanna be with your final tech stack anyways. Customers generally don’t care what you have coded their solution in. Your goal is more to build a flexible feature testing system / experimentation engine that can bill for money (presume the billing part). The context of what problem you’re solving is secondary because it will change and evolve. Today I would consider starting with: - TryCelery - no presales, no demand - Tailwind UI wireframe or PoC in HTML. Meant to be disposable. Shuffle.dev is a handy tool. - Flutter to recreate and build the prototype, aloha and mvp to have one code hit to hit all platforms including web. Forget is generally newer and next green collated to it’s contemporaries. Don’t work with tailwind or flutter? Hire a product designer and dev to not build it for you but teach you both via screen shares from UPWork, etc. If they can teach you how they can probably build it vs saying they can.