It's about two months since I launched AI Finance Office. Long enough now to have had a lot of conversations, and short enough that I still remember exactly how it felt to start. I thought I'd use this post to do something simple: share what I've learned, and what I'm hearing from finance leaders across the charity and not-for-profit sector.

The headline is this. Almost none of it has been about the technology.

When I started, I assumed the hard conversations would be the technical ones — is the AI accurate, is it safe, will it work with our system. Those questions do come up, they matter, and they have good answers. But they are rarely the thing that actually holds a finance team back. Two other things do, and I've come to think of them as the two challenges.

The first challenge is time

This is the one I underestimated. Finance teams in our sector are stretched thin, and there is a quiet irony in it: the teams who would gain the most from automating their month-end are the very ones with no spare hours to look into automating their month-end. The close eats the month, and there is nothing left over to step back and change how the close actually works.

So "we should really look at AI" becomes a line in the notebook that never quite gets actioned. Not from a lack of interest — from a lack of capacity. I have a lot of sympathy for that, because I have lived it.

The second challenge is imagination

This one is harder to talk about, but just as real. Even when there is a little time, it is genuinely difficult to picture what's possible. If you have spent fifteen years doing the payroll journal a certain way, it takes a real leap to imagine it any other way.

The question I hear most often isn't "can AI do this?" — it's "I wouldn't even know where to start." That isn't a failing. Nobody can be expected to imagine a tool they have never seen working on their own data. Which is exactly why I spend less time explaining and more time showing.

A few things I've learned in between

Start with the boring one. The instinct is to point AI at something clever. The better first target is the dull, repetitive task that quietly drains the month — the bank reconciliation, the payroll posting, the credit card coding. Win there, and the team starts asking what else is possible. The imagination problem tends to solve itself the moment someone sees one real thing work on their own numbers.

Lead with the pain, not the tool. The finance leaders who engage are not the ones most excited about AI. They are the ones most tired of a particular task. Start there and the conversation is easy.

The governance gap is real, and we don't talk about it enough. Across the sector, plenty of finance teams are already using AI day to day while their boards have very little visibility of it. That is a conversation finance directors will want to get ahead of, rather than have for the first time after something has gone wrong.

And what the time is actually for

It would be easy to read all this as a story about speed — close faster, post the journal quicker, get the month-end done in fewer days. That's the visible bit, but it isn't really the point.

Automating the repetitive layer doesn't replace the work that needs a finance brain. It is what finally makes room for it.

The point is what the hours are for once you have them back. The work that genuinely needs a finance brain — anticipating a problem while there is still time to act on it, sitting in the room when the spending decision is actually made rather than explaining it a month later, helping colleagues understand what the numbers are really telling them — is the work that always gets squeezed last and suffers first. Automating the repetitive layer doesn't replace that work. It is what finally makes room for it.

So when I talk about winning time back, I don't mean a faster version of the same job. I mean the chance to do the part of the job that drew most of us to finance in the first place.

Where this goes next

I'm still learning, genuinely. Every conversation teaches me something about how finance teams really work, and the product of all of it is that I am more convinced than ever that the barrier was never the capability of the tools. It was always time and imagination.

So if any of this feels familiar — the no-time, the not-sure-where-to-start — I'd gently say that's the normal starting point, not a sign you are behind. It is exactly where almost everyone begins. And the first step is smaller than you think: pick the most tedious task in your month, and let me show you what it looks like handled differently.

Here's to the next two months.