It is very rare that I upvote two comments that seem to be in opposition to each other. In this case, I think it's warranted because you're both likely correct.
In your favour, the strategy was successful and they grew to $5k MRR in four months with estimates suggesting they'll hit $100k in recurring annual revenue by the end of the year. It worked so it's hard to criticize it.
But, what if it hadn't, or what if the founders were in a different situation where they had a bigger team? Last minute "we have to do this now" decisions are often wrong. When they're not, they often result in some really ugly code that will be tough to maintain. Further, they can be hard on morale.
Chances are that the founders had this type of conversation and talked about the risks while they were brainstorming. It almost sounds like they had debated this in the past. Those kinds of debates are very valuable and I think that founders need to talk about how a new feature can go bad.
In your favour, the strategy was successful and they grew to $5k MRR in four months with estimates suggesting they'll hit $100k in recurring annual revenue by the end of the year. It worked so it's hard to criticize it.
But, what if it hadn't, or what if the founders were in a different situation where they had a bigger team? Last minute "we have to do this now" decisions are often wrong. When they're not, they often result in some really ugly code that will be tough to maintain. Further, they can be hard on morale.
Chances are that the founders had this type of conversation and talked about the risks while they were brainstorming. It almost sounds like they had debated this in the past. Those kinds of debates are very valuable and I think that founders need to talk about how a new feature can go bad.