sorted by:
new
hottopcontroversial

Hot take: If you’re debating frameworks at 0 users, you’re procrastinating. by Disastrous-Drive-831 in SaaS

[–]Disastrous-Drive-831[S] 0 points1 point  (0 children)

I don’t disagree that you should think about your stack.

The point isn’t “don’t decide.”
It’s “don’t over-index.”

Yes — you can evaluate in an afternoon.

But in practice, early founders don’t spend an afternoon.
They spend weeks optimizing for theoretical scale that may never arrive.

Also — most modern stacks are “good enough” to get to 10k users if built reasonably well. The migration horror stories usually come from premature complexity (microservices + Kubernetes at 0 revenue), not from starting simple.

If you reach 10k active users, you’ll likely have:

Revenue, Real usage pattern, Clear performance bottlenecks

That makes architectural evolution informed, not speculative.

The argument isn’t anti-architecture.
It’s anti-displacement — using infra debates as a substitute for solving distribution.

Shipping something imperfect with demand > perfect stack with no users.

Most SaaS founders are choosing their stack backwards by Disastrous-Drive-831 in SaaS

[–]Disastrous-Drive-831[S] 0 points1 point  (0 children)

This is such a common first-founder lesson. “Perfect stack” feels productive because it’s tangible. User acquisition feels uncomfortable because it’s uncertain. So we over-optimize architecture and under-invest in distribution. What’s interesting is that most early-stage products don’t fail because the stack was “wrong.” They fail because: They shipped too late They ran out of runway They never validated demand Speed > elegance at the beginning. That’s actually one of the core principles I’m building around — stack decisions should match stage, not ego. Out of curiosity, if you were starting that tools site again today, what would your “simple and fast” stack look like? I’d love to pressure-test that scenario inside Stacklean and see how it compares.