What are the key factors in a multi-org vs single-org design decision?

Single-org advantages: Unified data model, no cross-org integration overhead, single source of truth, simpler reporting and analytics, shared configuration (profiles, workflows, flows). Best for organisations with relatively uniform processes.

Multi-org drivers:
- Data residency / compliance: Different regions (EU, US, APAC) may require data to reside in specific geographic locations (GDPR, data sovereignty).
- Business unit isolation: Separate acquisitions or subsidiaries with distinct processes, data models, and security requirements that would conflict in a shared org.
- Org size limits: Very large orgs approaching platform limits (800 objects, storage, API call volumes) may benefit from segmentation.
- Release management: Separate orgs allow independent release cycles.

Multi-org costs: Integration complexity, duplicate master data management, higher licensing overhead, separate user management, reporting across orgs requires external data warehouse.

Recommendation: Start with single-org. Introduce multi-org only when driven by genuine compliance, security, or scalability requirements — not organisational politics.