Case study · Non-profit
The spreadsheet was not the problem. Keeping it up to date was.
MSF is a small non-profit running community services with a four-person team. Every contact, call and follow-up lived in spreadsheets, and keeping them current was somebody’s job every single day. They report that moving to Sahay cut that administrative load by roughly 70%.
The problem: admin scaling faster than the work
Small teams do not fail at record-keeping because they are careless. They fail because record-keeping is the one task with no deadline attached — it is always the thing that can wait until tomorrow.
MSF ran on spreadsheets. Contacts in one place, call notes in another, follow-ups remembered or not. With four people covering a service, the admin was not a small overhead on the real work. It competed with it.
And spreadsheets have a specific failure mode: they are only as good as the last person who remembered to update them. A row that nobody edited looks exactly like a row where nothing happened.
What changed
Two things, and the second matters more than it sounds.
The records write themselves. Calls are captured from the team’s own phones and logged automatically — contact, timing, what was discussed, what needs doing next. Nobody types a call note. In their case, every answered call was captured and transcribed, so the record is the conversation rather than somebody’s recollection of it.
Everyone sees the same thing. A shared dashboard replaced the spreadsheet, so the team stopped reconciling versions and asking each other who had spoken to whom.
MSF report roughly 70% less administrative work as a result. That figure is theirs — Sahay does not measure staff hours.
Why this one is worth reading if you are small
Most CRM case studies are about scale: more leads, more calls, more pipeline. This one is not. MSF is a four-person team and the volume is modest by design.
The value was never throughput. It was getting a group of people out of the business of maintaining a spreadsheet, so the hours went back into the service they actually run. That is a different argument, and for small teams it is usually the more honest one.