Blog
5 signs your nonprofit has outgrown spreadsheets
Spreadsheets stop carrying their weight long before a nonprofit notices. Five concrete signs the operating layer is overdue — board reporting, version chaos, donor handoffs, audit pain — and the small moves that put a real surface back underneath the ED.
Sign 1 — Board reporting takes longer than it should
Every month, the executive director spends two or three days rebuilding the board packet from the same five scattered sources: a finance spreadsheet emailed by the bookkeeper, a program report copied out of a shared doc, a development pipeline tracked on someone’s personal laptop, and a stack of carryover action items living in last month’s meeting minutes. The packet is the same shape every month, but it is rebuilt from scratch every month because nothing connects.
The real cost is not the three days of ED time. It is the quiet loss of trust: the packet arrives late, it has minor inconsistencies, the board chair asks the same clarifying question three meetings in a row, and the ED starts to dread a meeting that exists to give the board confidence in the operation. The ED is doing analyst work that should be doing itself, and the ED is also the only person who can fix it because nothing is owned anywhere else.
If the ED is also the person who copies last month’s numbers into this month’s deck by hand, the operating layer is already overdue. The fix is not “a better spreadsheet.” The fix is a single surface — a dashboard, a weekly briefing, a decision log — that pulls the same five sources into one picture without the ED stitching them together every cycle.
Sign 2 — Two people are editing the same file and no one knows which version is current
The grants calendar lives in a Google Sheet. The donor pipeline lives in another Google Sheet. The volunteer roster lives in a third. Each of them is correct in the moment it was last edited by whoever edited it, and each of them is wrong the moment anyone else edits it. Version history becomes the operating record: the ED scrolls back to find who changed what, and the wrong row is sometimes the row that goes into the board report.
The pattern is recognizable in any small nonprofit that has been running for more than three years. The sheets worked when the team was two people and the ED was the only editor. They worked less well at four people. They did not work at six, and they will not survive eight. At that point every function has its own spreadsheet and the ED has become the integration layer the spreadsheets cannot provide — not because the ED is good at integration, but because nothing else is doing it.
The fix is to pick one source of truth per question — a grants calendar, a donor pipeline, a volunteer roster — and own it in one place that the team reads from instead of editing into. The spreadsheet can stay if it is genuinely the right shape. The spreadsheet has to stop being the system of record that six people are silently overwriting each other on.
Sign 3 — Donor handoffs happen by email and the follow-up lives in someone’s inbox
A donor email comes in. The ED forwards it to the development lead, who forwards it to the program director, who drafts a response, who sends it back to the ED, who edits it, who sends it back to the development lead, who sends it to the donor. The cycle takes a week. By the time the donor replies, the original ask has been waiting four days in an inbox that the next person does not check every day. The follow-up step is in the development lead’s head, which means it is nowhere.
This is what a spreadsheet-based operating layer looks like at the boundary where relationships actually matter. The relationship is real, the ask is real, and the absence of a system means the relationship survives only on the discipline of the people involved. When the development lead goes on vacation, the donor follow-ups do not happen. When the program director transitions, half the open donor conversations become invisible. The donor experience is downstream of whichever staff member most recently touched the inbox.
The fix is a handoff surface — a donor pipeline with a stage, an owner, a last-touch date, and a next-step ask. Not a CRM with twenty fields nobody fills out. A single list of open donor conversations with one owner per row, one next step per row, and a weekly Monday review that chases anything that has been waiting more than a week. The right shape is small enough that the team will actually use it.
Sign 4 — You compare versions of the same file by hand and the audit trail is “whoever saved last”
The annual audit arrives. The auditor asks for the grant ledger, the donor-restriction report, and the program-outcome summary. The ED pulls the latest version of each file, then pulls the version from three months ago, then pulls the version from six months ago, and reconciles them by hand because nobody tracked what changed in between. The reconciliation takes a week. The auditor tolerates it. The ED quietly resents it.
Spreadsheets do not fail an audit because the numbers are wrong. They fail an audit because there is no changelog, no field-level ownership, and no version pinning. A cell that was overwritten in March by someone who did not realize they were touching the wrong row does not appear in the file’s history as a mistake — it appears as the current value. The auditor’s question “what was this number in Q2” gets the answer “whatever it was when we last saved it.” That answer does not pass the audit standard most funders and boards now expect.
The fix is a system where edits have an owner, a timestamp, and a reason. A change log that says “Sarah changed the grant total from $25,000 to $28,000 on March 14 because the amended award letter arrived” is auditable. A change log that says “the cell says $28,000 because that is what it says now” is not. The audit-trail problem is the spreadsheet’s deepest structural limit, and the moment a funder or a board starts asking for it, the operating layer is no longer optional.
Sign 5 — The ED is the integration layer and the week cannot survive the ED taking a real week off
Every one of these signs is the same sign from a different angle: the spreadsheets were the right operating layer when the team was two people and the ED was the only editor. They stop being the right layer when the team grows, when the ED’s week becomes more integration than the ED can carry, and when the absence of one person — the ED, the development lead, whoever used to hold the picture — turns the rest of the week into guesswork. The fix is not a better spreadsheet. The fix is a single surface the team runs against — a weekly briefing, a decision log, a donor pipeline with owners and next steps, a dashboard that opens every morning — so the ED is no longer the only person who knows what is happening this week. Ship the surface before the next board cycle. The ED’s first real week off in three years is downstream of that move.
Frequently Asked Questions
Frequently asked questions
How do I tell the difference between “we have outgrown our spreadsheets” and “we just need to be more disciplined about the spreadsheets”?
The discipline question and the system question are usually the same question wearing different hats. If the spreadsheet breaks the moment one person goes on vacation, that is not a discipline problem — it is an integration problem, and discipline will not fix it. If the ED is also the only person who can rebuild the board packet, that is not a discipline problem either. The right move is to ask: which of the five sources of friction is the spreadsheet actually the right shape for, and which is the spreadsheet pretending to be the operating layer because nothing else exists.
Is the answer always a dedicated platform like Salesforce or Airtable, or can the nonprofit just clean up the spreadsheet stack?
Sometimes the answer is to clean up the spreadsheet stack — when the team is small, the data is genuinely small, and the questions the team is asking are questions spreadsheets answer well. More often the answer is a small operating surface — a weekly briefing, a decision log, a donor pipeline with an owner per row — that pulls the spreadsheets together without replacing them. Salesforce and Airtable work for some nonprofits; they are usually overkill for a 2–10 person team and the team will not adopt them if the maintenance cost is higher than the ED’s current pain. The right test is whether the team will actually use the new surface on Monday.
We have been told to “get a CRM” for two years. Why has nobody done it?
Because a CRM is the wrong shape of fix for the actual problem. The nonprofit does not have a CRM problem — it has an integration problem. The donor pipeline lives in someone’s inbox, the volunteer roster lives in a sheet, and the grants calendar lives in another sheet. A CRM that imports all three without changing how the team uses them makes the integration worse, not better. The first move is a small operating surface — one pipeline, one decision log, one weekly cadence — that the team owns. The CRM becomes the right move six months later, when the surface has earned its keep.
How much does it cost to fix this at a 2–10 person nonprofit?
Most of the cost is not the tool — most of the cost is the ED time it takes to design the surface and to onboard the team onto it. A chief-of-staff engagement that ships a weekly briefing, a decision log, and a donor pipeline typically runs six to ten weeks of build time plus a recurring operating handoff; the dollar cost depends on the engagement shape and the team size. The cost of not fixing it is also real: every board cycle rebuilt from scratch, every donor handoff that lives in an inbox, every audit reconciliation done by hand. The math usually closes inside the first six months after the surface is running.
Can the executive director drive this fix themselves, or does it need an outside operator?
Sometimes the ED can drive the fix themselves — usually with a half-day of protected operating time per week for four to six weeks. More often the ED is the bottleneck precisely because the ED is the integration layer the surface is supposed to replace. The honest pattern is: the ED designs the surface, but a chief of staff, an operations lead, or an outside operator builds it with the team and hands it back to the ED once it is running. The first move does not have to be a hire — it can be a six-week engagement that ships the artifacts and hands them off.
What is the first thing to ship if we can only ship one thing?
The weekly briefing. Pick the next Monday, design a one-page template (last week’s carries, this week’s commitments, open decisions, blocked items, anything older than forty-eight hours waiting on the ED), assign one person to own it, and run it for four Mondays in a row. If the briefing has survived four Mondays the rest of the surface gets easier, because the team has seen the cadence work and the ED has a measurable time-back number for the next move.
Ready to operationalize this?
Book a 20-minute discovery call.
We will look at your week, your team shape, and how a chief-of-staff role — human or AI — fits your operating reality.