What’s the first technical decision you lock in when starting a new SaaS product?
by•
For me, I feel like the hardest part isn't choosing between tools like React, Firebase, Railway, etc, it's really deciding which parts of the stack I should commit most of my time and tokens early and which ones may become painful to replace later.
Do you stick with a familiar stack and avoid overthinking it, design around expected scale from day one, let your coding agent influence the architecture, or start with the cheapest setup and migrate later? Also, curious which early technical choice has saved you the most time, and which one you wish you probably shouldn't have overthinked on.
245 views
Replies
I’m not technical enough to recommend one universal stack, but I’d prioritize reversibility. The earliest architecture should make it easy to test demand and change direction without creating obvious security or data problems.
I’m not technical enough to comment on this, but I’d prioritize reversibility. The earliest architecture should make it easy to test demand and change direction without creating obvious security or data problems.