[fathermarz]

I do appreciate what’s being said here and I think there is a balance to strike. Is it a good idea to plan and design before jumping into code? Absolutely. Is it worth spending a month thinking of the perfect system when you don’t have customers actively using it or how they will use it? Probably not.

I also think it’s important to not get stuck in the sunk cost fallacy to avoid a rewrite. Take your lessons learned and bite the bullet.

I am in a position right now watching 3 years of tech debt get refactored into the same spaghetti garbage because leadership waited too long before calling a rewrite, and now they are under immense pressure to get it done but picked a warm body to rewrite it because everyone else is busy on other important things.

In another life, I was able to see the writing on the walls after initial implementation and spent two weeks rewriting the MVP to then be able to add new scalable features at a much higher velocity.

Needs analysis is crucial here, but I don’t disagree with OP.