Method · URSUS

Diagnosis

I understand how your numbers are built today, where time is lost and where trust breaks down.

What happens: I review data sources, the close process, reporting and how the ERP is used. I talk to the people who prepare the numbers and to those who use them.
What you bring: Access to the data and to key people in focused sessions.
What you receive: A written diagnosis: what works, what doesn’t, and a prioritised plan with scope and dates.

Design

I define the control model, the KPIs and the architecture across ERP, BI and automation.

What happens: I design the control model, the KPIs and the architecture across ERP, BI and automation.
What you bring: Leadership sign-off: which decisions the system must support.
What you receive: The design, documented and approved before anything is built.

Implementation

I build it with your team, not around it.

What happens: I configure, migrate, connect and automate alongside your team, who learn by doing.
What you bring: Your team’s time to build alongside me.
What you receive: The system up and running, tested with real closes.

Handover

You receive a working system and a team that knows how to run it. No unnecessary dependencies.

What happens: Training, documentation and support through the first closes.
What you bring: One person inside your team who owns the system.
What you receive: A working system and a team that knows how to run it.

How I work with collaborators.

When a project needs more capacity or a specific expertise, I bring in professionals from my trusted network. Always under my direction, with a single point of contact: me.

Ways of working together.

Fixed-scope projectScope, dates and milestones set after the diagnosis. It ends when the system works and your team runs it.
Ongoing supportPart-time management control leadership: close, forecast and reporting with a senior counterpart every month.

Let’s talk about your next decision.

Book a conversation