Case Study: Multi-Org on a shoestring budget

Multi-Org setups can be as varied as our clients. Recently I worked on an implementation that was different from any multi-org situation I’ve ever heard of.
For legal and security reasons the local organization needed each to have a completely separated Salesforce Org.
The central organization is not allowed to have any access to the unit’s clear data.

Most units don’t have more than a handful of Users.
The central Salesforce team is very small, supported by a consultancy.

Nr. of Units: 15
Process overlap: None
People overlap: None
Data Overlap: None

The central organization creates and maintains a managed package, making up a base implementation. 
Each unit installs the package independently and adopts it with the help of the central team to their needs.

Central Reporting:
There’s a need to do central reporting on anonymized, data. No ESB, ETL, or other advanced integration platform is available.
Solution: Monthly, manual export by the local teams using Reports are sent to a central PowerBI installation via a secure channel.

Local teams support their Orgs as much as possible and reach out to the central team as necessary.

– Upskilling local teams
– Local Back-Ups
– Technical support of local teams 
– Non-upgradable components like page-layouts

I found the chosen architecture fascinating because it treats the units more like clients in an ISV environment.
While usually, the central team has full control, in this setup the central team has to convince each unit to upgrade, adapt and use Salesforce.