multi-tenant-ready-schema-pattern-org-id-from-day-one
When building an internal tool that may later expand to multi-tenant SaaS, the lowest-cost future-proofing strategy is adding an organizations table and scoping every query by org_id from day one. This adds minimal schema cost upfront but avoids a full data-model rewrite if a second tenant ever onboards. The pattern preserves option value without committing to full SaaS complexity.