I build the reporting, then I build the machine that produces it

I'm an accountant and financial analyst with over four years across microfinance, consumer lending, multi-branch healthcare and digital assets. I started inside regulated institutions where the process was rigid and the deadlines were absolute, and I now work in a company that had no accounting structure at all when I arrived.

That second kind of work is where I do my best. At my current employer, a digital asset and gift card exchange, I built the finance function from a blank page — the chart of accounts, the reporting framework, the internal controls, the statutory tax processes. Then I automated the month-end close, cutting the reporting pack from a full working day of manual assembly to under an hour with Power Query.

Building a chart of accounts from nothing teaches you why every control exists. It also teaches you that most reporting problems are not reporting problems — they are capture problems that only become visible at month end. So I tend to work backwards from the report to the point where the data is created, and fix it there.

What I'm most useful for: a finance function that has outgrown its spreadsheets, a month-end that takes too long, a reconciliation nobody trusts, or a management pack that reports the wrong number because a formula points at the wrong cell. I've found and corrected exactly that — a ₦13.8m misstatement sitting in a summary block nobody had reconciled to source.

I'm completing the ICAN (ACA) qualification, expected 2027, and I'm open to remote roles and consulting engagements.