Consider a network of NGOs working in adjacent missions across a region. Each is independently incorporated, each has its own board, and the network's combined administrative cost is high because every NGO runs its own back office. Funders are increasingly asking the network for a coherent strategy. Use this playbook to frame the work, sequence the analysis, and avoid the common traps in a brief like that.
The consulting question
NGO networks face a recurring tension. Funders want consolidation because it looks efficient. Local communities trust the NGOs precisely because they are local, with their own boards and their own faces. The refresh has to hold both at once — capture the genuine shared-services efficiency without flattening the local identity that the NGOs depend on.
How to approach it
Strategy first, structure second. The mission alignment across the network is the first conversation. NGOs that look adjacent on a funder pitch can be doing genuinely different work. Sequence: agree the shared mission strands, then decide what infrastructure to share.
Share the back office, not the front. Finance, HR, technology, fundraising operations — these are usually duplicated and can be shared. Programmatic delivery and community presence stay local.
Hub-and-spoke, not merger. A small central hub provides shared services on a service-level basis to each network NGO. The NGOs do not merge; they buy services from the hub.
Cost transparency, not cost cuts. The first job of shared services is to show each NGO what their administrative cost actually is. The cost reduction follows from clarity, not from imposed cuts.
Suggested workplan
Months 1–2: Mission diagnostic. Which strands of work are shared, which are distinct, which are accidentally divergent.
Months 3–4: Shared-services design. Hub mandate and governance. Initial service-level agreements.
Months 5–6: Hub launch on the most painful shared service — usually finance or technology.
Months 7–18: Sequenced expansion of shared services. Adoption tracked by NGO satisfaction, not just cost reduction.
Questions to pressure-test
- What does each NGO see as the network's shared mission?
- What share of administrative cost is duplicated genuinely versus structurally necessary?
- Where does local identity actually live — staff, board, brand, programme — and how should it be protected?
- What is the smallest NGO's tolerance for shared services that the largest NGO will accept?
- Who governs the hub, and how is the governance accountable to the network?
A strong answer includes
The administrative overhead falls — most visibly for the smaller NGOs that were carrying a disproportionate fixed-cost burden. The local face of each NGO is intact; communities still see their NGO, not a regional brand. Funders see a coherent strategy that explains how the network's parts add up. And the hub is small, focused, and accountable.
Common traps
Mission alignment is not assumed. NGOs in adjacent missions can be doing very different things. Get the mission conversation right or shared services becomes adversarial.
Local identity is the asset. Networks that consolidate too far lose the community trust that made the consolidation possible.
The smallest NGO matters most. Shared services that work for the largest NGO often crush the smallest. Design for the smaller end of the network.
Hub governance is the hard part. A hub accountable only to itself becomes a problem within a year. Pre-design the accountability mechanism.
Use this playbook to help an NGO network balance shared services, local autonomy, funder confidence, and governance before recommending consolidation.