AI in Finance
Finance that runs itself.
Every build is bespoke to the systems you already run. There is no product to licence, nothing to migrate to, and no vendor relationship to protect. What follows is what I build most often, and what changes when it is in place.
01
Close the month faster
What the problem looks like
The close runs on spreadsheets and memory. Reconciliations are manual, journals arrive late, and the numbers reach the founder in week three of the following month, by which point they are history rather than management information.
What gets built
Automated bank and ledger reconciliation, rules-based accruals, exception queues for the items that genuinely need judgement, and a close calendar that tracks itself. Every automated step leaves an audit trail and a named reviewer.
What changes
The close moves from weeks to days, and the finance team spends the time it recovers on the variances rather than the arithmetic.
02
Release cash from working capital
What the problem looks like
Cash is managed from a spreadsheet updated when someone remembers. Overdue receivables are chased late, payment runs are timed by habit, and nobody can say what the position will be in six weeks.
What gets built
A rolling short-term cash model wired to the ledger and the bank, collections chasing that runs on its own, supplier terms modelled properly, and alerts when the forecast position moves beyond a threshold you set.
What changes
Cash stops being a monthly surprise. The number is current, and the actions that improve it are visible before they matter.
03
Board packs that build themselves
What the problem looks like
Two people lose a week each month to assembling the pack. Charts are rebuilt by hand, commentary is written under time pressure, and the version that reaches the board is the one that was finished, not the one that was best.
What gets built
Pack assembly from your actuals, consistent chart templates, first-draft commentary generated from the movements in the numbers, and a review gate so nothing is published without a person signing it off.
What changes
The pack takes hours instead of a week, and the board reads a consistent document each month.
How a build works
Diagnostic, build, handover.
01
Diagnostic
Two to three weeks inside the numbers, the systems and the calendar. You get a written view of where the time goes and what is worth building, ranked.
02
Build
Delivered in fortnightly increments against your existing systems. Nothing is switched on without a control, an audit trail and a named owner.
03
Handover
Documentation, training and a running function. The measure of the engagement is that it still works after I leave.
Book a call
Thirty minutes, no pitch. Tell me what the finance function looks like now and I will tell you what I would do first.