What are the key decision factors in a single-org vs multi-org design for a global B2B enterprise?

Single-org advantages for B2B: Unified 360-degree account view across regions, no cross-org data synchronisation complexity, shared master data (Products, Price Books, Accounts), centralised reporting and analytics, consistent process enforcement.

Multi-org drivers:
- Data residency / compliance: GDPR, local data sovereignty laws may require European customer data to remain in EU infrastructure. Salesforce Hyperforce enables regional data residency within a single org — evaluate Hyperforce before defaulting to multi-org.
- Business unit autonomy: Acquired companies with distinct CRM processes, separate sales motions, or conflicting data models that would require excessive customisation to reconcile.
- Regulatory separation: Financial services or healthcare organisations where different business units have strict data separation requirements.
- Scale limits: Organisations approaching 800 custom objects, extreme API volumes, or storage limits may need to split workloads.

Multi-org costs: Master data management (Account deduplication across orgs), cross-org reporting requires external data warehouse, double licence costs for shared services, complex release management.

Recommendation: Start with single-org + Hyperforce for data residency. Only introduce multi-org when regulatory, security, or process conflicts are genuinely irreconcilable.