Capabilities
No templates, no juniors, no off-the-shelf anything. Three disciplines, each delivered to the same standard: numbers that reconcile, logic you can trace, and outputs built for the people who carry the decision.
If it goes in front of a board, it should look — and behave — like it belongs there.
Six ways we engage
Most clients start with one of these and end up needing two or three. They are priced as consulting engagements — day rate or fixed scope, agreed before we begin.
The core work. Financial models, group consolidation logic, management and statutory reporting — designed from the outputs backwards. Master data, entity hierarchies, FS items, eliminations, currency translation. Built by hand, documented, and handed over working.
For: groups whose consolidation is fragile, manual, or held together by one person.
Before the system comes the process. We map how the close actually runs — who submits, who reviews, where it breaks — then redesign it: the close calendar, submission gates, review controls, ownership. The system is then configured to serve the process, not the other way round.
For: finance functions where the close is late, chaotic, or undocumented.
Hands-on delivery across SAP S/4HANA Group Reporting, BPC, BW/4HANA and SAC — plus Anaplan, Infor SunSystems and Xero. Configuration, data structures, consolidation units, validation rules. Twenty years across landscapes at up to 600 legal entities.
For: programmes needing a practitioner, not a slide deck.
An independent review of a model you already have — before it goes to a board, a lender, an auditor or an acquirer. Logic tested, figures traced to source, assumptions surfaced, errors found. You get a written opinion, not a colour-coded spreadsheet.
For: anyone about to stake a decision on a number they did not build.
The deliverable everyone skips and every auditor asks for. Process documentation, model logic, data lineage, configuration records, close procedures — written so that a reviewer who has never seen your system can follow it. Delivered as a standalone engagement, or with any build.
For: functions carrying key-person risk, or facing audit, due diligence or handover.
Your system, your data structures, your team — taught by the practitioner who built it. Not generic courseware. Programmes are scoped to your landscape and delivered so the capability stays after we leave. See the training programmes →
For: teams inheriting a system nobody has explained to them.
Most engagements begin with a conversation and a look at what you already have. There is no charge for that, and no obligation to proceed.
Speak to the principal