Who Holds the Keys When the Founder Steps Back?
Photo: Unknown authorUnknown author, Public domain, via Wikimedia Commons
Every small co-op has a founder-shaped hole in its story. Maybe they started it around a kitchen table, got the first community share offer over the line, or simply know where the insurance certificate lives. Then one day they say they want to step back. Cue mild panic.
The good news is that a founder exit is not a betrayal, and it is not a farewell party with a card and a whip-round. It is a governance project. Like any governance project, the earlier you start, the less dramatic it is.
The keys are never just keys
Founders hold keys. Some are metal. Some are passwords, relationships, bank mandates, grant reports, the landlord's mobile number and the weird filing cabinet that nobody else has opened since 2019. If the founder leaves and those keys leave with them, the co-op does not have a handover. It has a hostage situation with a nice card.
So start with an inventory, not a goodbye speech. What does the founder actually hold?
Map the role before you map the person
Start with a plain list. What does the founder do? Include the formal stuff: director duties, signing bank mandates, payroll, grant reporting. Then the informal stuff: knowing the alarm code, being the person funders ring first, remembering why the co-op stopped using that one supplier. Then the relational stuff: calming the volunteers, holding the relationship with the local council, being the public face.
Put each item into one of four boxes: keep, hand over, automate, or stop doing. Some things should stop. A founder exiting is a good moment to ask whether the co-op really needs a weekly meeting that exists because it always has.
Be honest about the founder as a person. They may be a director, an employee, a member, a volunteer, a landlord, or all five at once. Each hat comes off differently. The director resigns. The employee retires or leaves. The member stays a member. The landlord renegotiates the lease. Do not try to solve all of that in one emotional meeting.
Decision rights: the bit people skip
Most co-ops have rules about the board and members. Fewer have written down who decides what day to day. That gap is where founder dependency lives.
Make a decision rights table. For each recurring decision, write who recommends, who decides, who is consulted, and who needs to know. Keep it short. Examples: spending over £500, hiring a new staff member, signing a grant agreement, speaking to the press, changing a supplier, approving a new project. If the founder currently decides by being the only person who knows, that is not a decision right. It is a single point of failure.
Do this with the founder, not about them. The point is not to strip them of power. It is to move power into the co-op where it belongs.
Ownership is not the same as control
This is the awkward bit. In a co-op, the members own the thing collectively. The founder may have shares, but co-op shares are usually not a controlling stake in the venture-capital sense. They are membership shares. In many societies they are withdrawable at par, not saleable at a premium. Check your rules.
Then separate the legal ownership questions from the practical control questions. Does the founder personally own the intellectual property? Is the lease in their name? Did they lend the co-op money? Is there an informal agreement that everyone remembers differently? These are not farewell-party problems. They are legal and governance problems, and they need fixing before the goodbye playlist.
If your co-op has an asset lock, a community benefit society structure, or a CIC, get the rules out and read them. This is not the moment for vibes. It is the moment for a solicitor and an accountant who understand community business.
Build a runway, not a cliff
A founder exit planned over two years is a handover. A founder exit planned over two weeks is an emergency.
Think in stages. Two years out: document the role, train a deputy, start sharing financial information more widely. One year out: hand over decisions, recruit or promote, change bank mandates, update Companies House and the FCA register, tell funders. Six months out: the founder takes a two-week break while the co-op runs without them. That fire drill will tell you more than any plan on paper. On exit: resign from formal roles, hand over the keys, review what broke.
Write the plan down and let the board own it. A succession plan that lives only in the founder's head is not a plan. It is a rumour.
The awkward conversation about keys
Here is a starter script. I want to step back by this date. I am not vanishing. Here is what I think I hold. Can we agree what I hand over, when, and to whom?
Then ask the board a harder question: are we replacing a role, or are we protecting a relationship? If the founder is the only person who can hold a difficult volunteer or a funder together, that is not a role. That is a dependency.
Make room for the founder to grieve the change. Founders often built the thing with their whole self. Stepping back is not just a diary change. But the co-op does not owe the founder a permanent veto. It owes them a fair handover, clear thanks, and a future that does not require them to be there.
What good looks like
You know the handover is working when someone else can sign the bank mandate, answer the funder's email, run payroll, find the insurance certificate, and open the building without ringing the founder.
Founder exit is successful when the co-op barely notices the farewell party because the work has already moved. That is not disloyalty. It is the whole point of collective ownership.
Plan it years before anyone leaves. Not because founders are untrustworthy, but because co-ops are shared. The goal is not to make the founder irreplaceable. The goal is to make the co-op not dependent on any one person. Shared futures need shared keys.