The first paid step

The 5 to 10 day ERP Data Readiness Review.

A fixed, low-risk first engagement. It gives you a clear view of what is wrong with your data, what needs fixing, who owns it, and whether the project is safe to move forward — before the ERP migration or reporting rebuild gets expensive.

Remote-first · On-site where it helps · Vendor-neutral

// at a glance
Duration5–10 days
EngagementFixed scope
OutputFix plan
RiskReduced
01 — Why it exists

Most ERP projects fail on data, not software.

Migrations slip and reports lose trust because nobody mapped the data, found the mismatches, or agreed who owns each decision until it was too late. The Readiness Review front-loads that work into a short, fixed engagement.

You come away knowing exactly what is wrong, what it will take to fix, and whether cutover is safe — evidence you can put in front of your board, your ERP partner and your team.

02 — What you receive

Five deliverables, not a slide deck.

01

Source inventory

Every system, spreadsheet and extract that feeds a number — ERP, CRM, finance, warehouse, Excel and reporting. Delivered as XLSX.

02

Data quality issue register

Duplicates, missing values, mismatches, invalid codes and owner gaps — logged, categorised and ranked. Delivered as CSV.

03

Reconciliation checklist

What must tie back to ERP, finance and operational truth — so reports can be trusted again and mismatches stop recurring.

04

Owner matrix

Who signs off customers, suppliers, items, stock, pricing and reporting definitions — so decisions have a name against them.

05

Prioritised fix plan

The action list that turns vague data risk into delivery work — ranked by value, urgency and cutover risk, with a risk summary you can hand straight to your board (PDF).

03 — How the review runs

A short, visible engagement — not a consultancy programme.

DAYS 1–2 · STEP 01

Map the mess

Review systems, spreadsheets, reports, extracts, known pain points and data owners. Build the source inventory.

DAYS 3–5 · STEP 02

Find the risk

Identify duplicates, missing fields, finance mismatches, unclear definitions and cutover blockers. Populate the issue register.

DAYS 6–8 · STEP 03

Prioritise the fix

Turn issues into a practical action plan by value, urgency and cutover risk. Assign owners.

DAYS 9–10 · STEP 04

Build trust

Walk the business through the findings, reconcile the priority reports and hand over a repeatable way forward.

04 — When to book it

Book the review if any of these sound familiar.

"Our reports don't reconcile."

Stock reports don't tie to finance; Power BI doesn't match the ERP.

"We're migrating soon."

The ERP project is moving and data decisions aren't owned properly.

"Nobody trusts the numbers."

Leadership argues over versions of sales, margin and backlog.

Start with a 30-minute data risk call

Find out whether the review is the right first step.

Tell me what needs to migrate, what no longer reconciles, or which report the business no longer trusts. If there's a fit, we scope the review together.