You've sketched your SaaS idea on a whiteboard — users, accounts, billing, some core feature. Now you need a database schema. The temptation is to over-design: normalize everything to 5NF, plan for millions of users, add every index you can think of. The reality is that 80% of schema decisions made in week one get rewritten by month six as product direction shifts.
This framework isn't about academic database design principles. It's about making the minimum set of structural decisions that won't block your development velocity or require painful migrations later.
Quick Answer
Start with a single Postgres database, a users table (using UUIDs, not auto-increment IDs), an accounts/organizations table if you have multi-tenant users, and a subscriptions table that references your payment provider's IDs. Use JSONB columns for flexible attribute storage (pricing plans, user preferences, feature flags) — you can normalize them into proper tables once the data model stabilizes.…