Insights · Diagnose

What an honest fixed-price ERP diagnostic contains.

Most assessments are sales documents with findings attached. An honest diagnostic names the constraint, lists the silent decisions, and ends in a plan you could execute without its author.

PONTURA INSIGHTS · 5 SEPTEMBER 2026

"Assessment" may be the most devalued word in consulting. Most of them are sales documents with findings attached: thirty slides of observations, a maturity spider chart, and a phase-2 proposal disguised as a conclusion. You learn what you already knew, and the only decision the document enables is whether to hire its author.

The contents

Five things an honest diagnostic contains.

The constraint, named. One thing — not twelve observations. Every operation has exactly one thing limiting throughput or reliability today, and it is rarely the one on the steering-committee slide. An assessment that ends without naming it hasn't ended; it has stopped.

A decision list. Troubled projects are full of decisions that were taken silently — by default, by omission, by whoever configured the screen that day. An honest diagnostic drags them into the light: what was decided, by whom, on what grounds, and which of those decisions are load-bearing.

The landscape as it is. Not the architecture slide — the actual system landscape, with the interfaces that really flow, the master data as it really looks, and the spreadsheet layer everyone pretends is temporary.

A plan you could give to our competitor. Sequence, staffing, risks — concrete enough to execute without its author. That is the test of an honest plan: it is executable with us or without us. If a plan only works when its author sells you the next phase, it isn't a plan; it is a quote.

A fixed price, agreed before the start. Not because estimating is easy, but because of what it does to incentives. A diagnostic billed by the day is rewarded for taking longer; a fixed-price one is rewarded for reaching a decision.

What it leaves out

The absence is the signature.

An honest diagnostic does not contain a software recommendation on page one — the tool question comes after the constraint, if at all. It does not contain a maturity score against a proprietary model. And it does not need a hundred pages: findings, decisions, and a plan fit in a document people will actually read.

Questions that test any assessment offer
  • Will you talk to the people who run the operation, or only the ones who steer it?
  • Is the price fixed before you start?
  • Will the plan be executable without you?
  • What happens if the honest conclusion is "stop"?

This is how every Pontura engagement starts — greenfield or rescue. We call it the Diagnose phase: short, fixed-price, and it ends in decisions, not observations. If a project has already drifted, it is also how a rescue begins.

Tell us what isn't moving.

Plan a project call