Founder dependence in a nonprofit is a risk nobody names

Aug 29
3 min read

Updated: 2 days ago

Introduction

The founder started it, knows every funder personally, holds the relationships, makes the decisions, and works far more hours than anyone pays for. The organisation exists because of them and everybody knows it.

It is also entirely dependent on them, and nobody wants to say so. If that person becomes ill, burns out, or simply wants a different life, the charity faces a crisis it has never discussed. This is one of the most common risks in small nonprofits and one of the least addressed, because raising it feels like criticism.

1. Founder dependence in a nonprofit is a governance risk

Name it neutrally so it can be discussed.

It is not a judgement on the founder, whose commitment is usually the reason anything exists. It is a structural fact that the board is responsible for managing, and framing it that way makes the conversation possible.

2. Establish what only one person knows

Start by mapping the dependency.

Funder relationships, passwords, bank access, the history behind decisions, which volunteer to call, what was promised to whom. Writing this list is uncomfortable and it is usually longer than anyone expected.

3. Document as you go rather than as a project

Comprehensive documentation projects do not finish.

Write down the process the next time you do it, record the funder conversation the day it happens, note the reasoning behind a decision in the minutes. Accumulated over a year this produces something usable at almost no cost.

4. Introduce funders and partners to somebody else

Relationships are the hardest thing to transfer.

Bring another person to meetings, copy them into correspondence, and let them lead sometimes. Funders back organisations they know, and if they only know one individual their support leaves with that individual.

5. Sort out access and authority formally

The practical problem that becomes urgent overnight.

Bank signatories, system administration, domain and email ownership, and who can authorise spending. If the answer to any of these is one person, the organisation cannot function during an unexpected absence.

6. Build a board that can actually govern

Founder dependence and a passive board occur together.

Trustees recruited as supporters rather than as governors will not hold the founder to account or step in when needed. Strengthening the board is usually the first move that makes everything else possible.

7. Let the founder step back gradually

Sudden withdrawal is not the alternative.

Hand over one area at a time, with the founder available to advise, over a period long enough for the successor to build their own relationships. Abrupt transitions are what damage organisations, not the transition itself.

8. Talk about succession before it is urgent

The conversation everyone postpones.

A short discussion at board level about what happens in the event of long absence or departure, and a written outline of who covers what. It takes an hour and it is the difference between a plan and a scramble.

9. Look after the founder

Dependence is exhausting for the person depended upon.

Founders in this position often work unsustainable hours and cannot take leave. Reducing dependence is protective for them as well as for the organisation, and framing it that way makes it far easier to raise.

Test the arrangements by taking a genuine break. A founder taking two consecutive weeks away with no contact reveals exactly where the organisation depends on them, at far lower cost than discovering it in an emergency.

Conclusion

Name founder dependence as a structural risk rather than a criticism, because the board is responsible for managing it.

Map what only one person knows or can access, document routinely as work happens rather than as a project, introduce funders and partners to a second person, formalise bank and system access so nothing halts during an absence, strengthen the board so it can genuinely govern, plan a gradual handover rather than a sudden one, discuss succession before it becomes urgent, and recognise that reducing the dependence protects the founder as much as the organisation.