ERP · EPM · CRM · HCM · Integrations · Advisory

The decision has your name on it. So does ours.

Choosing a finance system is one of the few decisions a CFO cannot quietly reverse. We start with your process, argue the recommendation against the alternatives, and keep the same people on the work through go-live.

Talk to a person
Exploded technical drawing of a finance system DECISION / OPTIONSEXPERIENCE LAYERAPPLICATION LAYERDATA LAYERINTEGRATION LAYERGOVERNANCEPROCESS INPUTBOARD OUTPUT

From disconnected and manual to one governed architecture.

The current homepage’s systems story becomes a technical section in its own right—one drawing, one transformation, no floating widgets.

Today / fragmentedFragmented systems and manual handoffsERPSHEETSCRMLOCALEPM
Decided / governedGoverned system architecturePROCESSTOOLCONTROLDATARULESOWNERSINTEGRATIONGOVERNANCE

Start where it hurts

Six situations. A different first move in each.

Pick the one that sounds like your last quarter. The wrong first move is how a project loses six months before anyone notices.

01The workarounds have workarounds.

Have the system examined before anyone proposes replacing it.

See what a Health Check looks at
02Investors want answers the system cannot produce.

Fix planning and close first — the reporting problem is usually downstream.

Plan and close without rebuilding it
03Every new country adds another workaround.

Localization and consolidation belong in the ledger, where the posting happens.

Run the business on one set of books
04Spreadsheets and local systems no longer keep up.

Map the processes first. The shortlist then falls out of the map.

See how the selection runs
05The CFO needs a case the board can interrogate.

The deck uses your numbers and processes and argues the alternatives.

Talk to the person who would run yours
06I don’t have a company. I have isolated islands.

One template, localized where the law demands it and nowhere else.

Connect the islands

How this works

Process, tool, automation, AI.

In that order, and we do not skip one. A system selected before the process is understood is a guess with an invoice attached.

Technical exploded sequence: process, tool, automation and AIPROCESS / REALITYTOOL / FITAUTOMATION / RULEAI / ANALYSIS
01

Process

What actually happens, written down — including the workarounds nobody documented.

02

Tool

The system chosen from the mapped process and argued against alternatives.

03

Automation

Repeated, rule-shaped work handed to the system once the rule is stable.

04

AI

Used today in design and analysis, not inside the live finance system.

Before you sign anything

Four things happen. Software is last.

Most of this industry runs the list backwards: demo first, process later, usually during the build and usually at your cost.

01

The first call

What the business sells, where it is heading, and what is breaking right now. Nobody opens a demo and nobody mentions a licence.

02

Your process, walked end to end

Your version of the work, next to the way it is normally run. That comparison shows which differences are real and which are habits.

03

A proposal with a price and an argument

Options A, B and C, with the reasoning next to each — written for a board that will ask why the other two were dropped.

04

The software, after the process work

You see the system once we understand how you actually work. A demo run on somebody else’s data proves nothing about your close.

And once the contract is signed

Five phases. Finance signs off before handover.

Discovery ends with your legal entity structure, chart of accounts, integration landscape and period-close workflow written down. Configuration starts after that.

01

Discovery

Financial architecture review, entity mapping, integration audit, and KPI alignment.

02

Design

Chart of accounts, consolidation structure, workflows and recognition rules documented first.

03

Build

Sprint-based configuration, data migration, integrations, and testing against real scenarios.

04

Go-live

Hypercare, managed parallel run, and a financial close signed off.

05

Scale

A named support consultant, module expansions, and an annual Health Check.

90+NetSuite projects behind the advice
~100people across ERP and EPM
2006supporting finance teams since
<100days to go-live on a single-entity build

Work already delivered

Five published projects.

Five are the ones Cloudmaven has written permission to describe. The rest are not named here.

AMANN

From international expenses and multi-country rules handled by hand to standardised approvals and master data synchronised into SAP.

Scenic

From disparate consolidation and intercompany systems to one reliable source with automated consolidation and elimination.

Hasenkamp

From manual international expenses across twenty entities to end-to-end expense management integrated with Exact ERP.

NZYM

From manual expenses across six entities to automatic posting into Microsoft Dynamics 365 Business Central.

Perk

From disparate data and manual consolidation to one integrated financial platform with automated elimination.

Who stays

The same names, through the year after go-live.

After the project closes, somebody still owns your account, and it is a person rather than a queue.

The first call

Lars Kirschstein

Managing Director

Scope and contract

Christoph Schweins

Managing Director

The technical read

Fares Khattab

ERP & NetSuite Specialist

Products and connectors

Jarrid Gilfillan

Head of Products

After go-live

Eric Roger Jean

Install base

One bounded way to start

The Health Check: ten working days, and a written answer you keep.

We examine how the system is set up, what that setup costs you, and what to fix first. You keep the report and its prioritised first-fix list.

Talk to someone first
Technical diagnostic trace drawingCURRENT SYSTEM TRACEFIRST FIX