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.
190 views
Replies
@maxitencent What's one thing you always prototype before committing?
@maxitencent Have coding agents changed how much planning you do upfront?
@maxitencent At what point do you finally stop researching and start building?
@maxitencent Which early shortcut has actually held up better than expected?
@maxitencent How much does your deployment strategy influence the rest of the stack?
@maxitencent How often do you end up replacing something you thought was permanent?
@maxitencent Has one previous mistake completely changed your starting checklist?
I used to spend days comparing stacks before writing any code. Looking back, the projects that succeeded were the ones where I picked familiar tools and started shipping. Most of my "perfect architecture" plans never ended up mattering.
Looking back, have you found that the biggest long team decisions were actually about architecture and data models rather than the specific framework or hosting platform?
@maxitencent Which technical choice gives you the most confidence early on?