01
Debt is a budget, not a crime
Early SaaS products need speed. The mistake is treating all shortcuts as equal. Some debt compounds quietly; some is cheap to repay once you have customers.
Decide which areas must stay clean from day one — auth, billing boundaries, data ownership — and which can be temporary.
02
Invest in seams
Clear module boundaries matter more than perfect abstractions. If you can rewrite a feature without rewriting billing, you have enough architecture for the next year.
Prefer boring technology at the core. Novelty belongs at the edges, where it can be replaced.
03
Measure what will hurt later
Track the things that become expensive: query latency, deploy confidence, and how long a new engineer needs to ship a small change.
Those signals tell you when intentional simplicity has tipped into accidental complexity.
