The same problem. Two ways to fix it.
Most finance and operational problems share a root cause: unclear ownership and systems never designed for the pressure they're under. Engagements fall into two categories, but the diagnostic approach is the same for both.
Workflow and Execution Redesgin
Workflow and Execution Redesgin
Workflow and Execution Redesgin
Replacing Inbox-driven work with clear ownership and structured execution using MS365. For organizations where capable people are compensating for unclear systems.
Finance Function Transformation
Workflow and Execution Redesgin
Workflow and Execution Redesgin
ERP Remediation, post-acquisition restructuring, FP&A buildout, internal controls. For organizations where the finance function is broken or running on workarounds.
Workflow and Execution Redesign
Step 1 Assessment
Step 2 Redesign
Step 2 Redesign
I look at how work is actually moving, where decisions live, how information flows, and where accountability breaks down.
Where email volume is highest; which decisions are buried in threads; what has no owner.
Step 2 Redesign
Step 2 Redesign
Step 2 Redesign
Once pressure points are clear, I redesign how work flows and where accountability sits.
Replacing inbox dependency with MS365 structure so work is visible, owned and traceable without a meeting.
Step 3 alignement
Step 2 Redesign
step 4 Adoption
Systems fail when leadership behaviours don't change with them. The step ensures leaders know where to look, decisions are recorded consistently, and the finance team is no longer absorbing unspoken pressure.
Status is pulled from the system; it doesn't need to be asked for by email.
step 4 Adoption
Step 2 Redesign
step 4 Adoption
I don't hand over a new system and walk away.
I support early adoption, practical usage, and small course corrections until the change has taken hold and the team no longer needs me to maintain it.
Finance Function Transformation
Step 1 Assessment
Step 2 Redesign
Step 2 Redesign
I look at how work is actually moving, where decisions live, how information flows, and where accountability breaks down.
I look at how work is actually moving — where decisions live, how information flows, and where accountability breaks down. Finance: how the ERP is configured; where clearing accounts sit; whether AP can three-way match.
Step 2 Redesign
Step 2 Redesign
Step 2 Redesign
Once pressure points are clear, I redesign how work flows and where accountability sits.
Correcting ERP configurations; restructuring the finance team; activating dormant modules; introducing FP&A and proper reporting cadences.
Step 3 alignement
Step 2 Redesign
step 4 Adoption
Systems fail when leadership behaviours don't change with them. This step ensures leaders know where to look, decisions are recorded consistently, and the finance team is no longer absorbing unspoken pressure.
CPO and Controller aligned on new reporting structure; management comfortable relying on ERP numbers instead of Excel estimates.
step 4 Adoption
Step 2 Redesign
step 4 Adoption
I don't hand over a new system and walk away.
I support early adoption, practical usage, and small course corrections until the change has taken hold and the team no longer needs me to maintain it.
What This Looks Like In Practice
The best way to understand how an engagement works is to see one. Here's what a finance transformation engagement produced.
$20M Inventory discrepancy resolved; finance department rebuilt
Five years of compounding ERP errors, a Controller on medical leave, and financial statements management couldn't trust, resolve