Impact Measurement: The Data Silo Killing Your Funding

Executive Summary

---

The problem: A last-minute scramble for numbers

It’s a situation I’ve seen in quite a few scaling non-profits. The quarterly board meeting is two weeks away, and a key trustee asks the one question that causes a certain sense of unease: “What’s our cost per outcome? I want to see our impact per pound.”

What usually follows is a week of hurried, manual work. The finance team exports a CSV from Sage or Xero. The operations team pulls data from a separate CRM or a web of interconnected Google Sheets where programme delivery is tracked. For the next week, a talented analyst, who should be finding useful insights, is instead tied up in the tedious task of stitching these two worlds together. The final number is produced, but nobody, least of all yourself, has complete confidence in it. You know it’s a fragile snapshot, not a repeatable process.

This isn't a failure of your people. It's a failure of the system.

The cause: Systems that don't talk to each other

You've probably invested in good cloud-based tools and hired smart, dedicated people. The trouble is, this can sometimes just mean you're making the same mistakes, only faster. Automating a broken process just generates bad data more quickly. The root cause is that your financial system and your operational system were never designed to speak to one another.

In my experience, this is a classic case of an organisation's growth outpacing its data systems. The systems that worked for your first grant are now a liability. The problem isn't the dashboard tool; it's that the business logic connecting a 'financial cost' to a 'programme intervention' lives in a spreadsheet formula instead of a governed, central system. These Data Silos create a constant state of ambiguity, forcing you to defend your numbers instead of championing your impact.

I tend to see this pattern in every non-profit that successfully scales beyond its initial founding team. It's an uncomfortable, but fairly predictable, consequence of success.

How to fix this: Creating a single source of truth

The only lasting solution is to stop patching the reports and fix the underlying structure. This doesn't mean a costly and disruptive migration of your core systems. It means building a unified reporting layer that sits on top of them, creating a Single Source of Truth for all impact-related questions.

Map the flow of work, not just the data: We begin by sitting with your finance and operations teams to map their real-world processes. How is a grant allocated? How is a field worker's time logged against a specific project? We work to understand how people do their jobs before we touch any data. This is the foundation of all effective Financial Reporting.

Agree on the definitions: This is a crucial step. We work with you to create a clear, agreed Metric Definition for every component of your 'impact per pound' calculation. What constitutes an 'intervention'? Who qualifies as a 'beneficiary'? What overheads are allocated to which project? These definitions are agreed once, with both finance and operations teams signing off, and then they are built into the system. This settles the debate.

Automate the connection: With the logic defined, we build the connections that automatically pull data from your different systems into a unified model. The weekly scramble becomes a daily, automated report. Your 'impact per pound' isn't a number you calculate; it's a number you monitor.

A note on the human side of this work

I should be honest: putting a single source of truth in place isn't always straightforward. The hard part isn't the technology; it's the human element. You are asking teams who have worked independently to agree on a shared set of facts. You might be taking away the 'master spreadsheet' that a department head has spent years perfecting. It's reasonable to expect some resistance.

This kind of work needs clear support from leadership and a willingness to have some careful conversations about ownership and definitions. It will feel slower for a few weeks as you establish the rules, but it's the necessary work to let you move faster, and with more confidence, for the next five years.

What this looks like when it's working

Imagine the next board meeting. The 'impact per pound' question is asked. Instead of a hesitant answer based on a spreadsheet, you show a live dashboard. You can filter it by programme, by region, by quarter. You can drill down from the headline metric to the individual cost and outcome components.

The conversation changes almost immediately. The board stops questioning the validity of your data and starts engaging in strategic discussions about how to improve the impact itself. You're no longer defending your numbers; you are discussing how to improve them. That is the relief of trusted data.