A technology decision is being made on the strength of the word, not the problem.
Cloud. Kubernetes. AI. A platform migration. The technology gets chosen before anyone establishes whether this problem needs it. Sometimes it genuinely does. Often the same outcome was available at a fraction of the operating cost. The organisation then carries the difference every month, for years: a demolition hammer bought to drive a nail, and then staffed.
- Indicative range
- Typically €9,000–15,000, fixed scope
- Shape
- Usually ten business days, remote.
What you are already seeing
- The tool was named before the problem was measured.
- The solution is described more clearly than the constraint it removes.
- Vendor claims and internal evidence are not being kept apart.
- Nobody can state what the current direction costs, so nothing can be compared to it.
What gets examined
- 01
What is actually being decided, and what is outside it.
- 02
Whether the proposed technology is proportionate to the problem, or considerably larger than it.
- 03
What each option demands of architecture, operations, security and the people who will run it.
- 04
What the exit path costs if the choice turns out badly.
What you are left holding
- 01
A recommendation with the rejected options and the reasons.
- 02
Cost and operating assumptions stated so they can be challenged.
- 03
Conditions that must hold before committing.
- 04
A 90-day action plan with named owners.
Before you send anything
Plain language is enough — the system, who owns the outcome, and the date that matters. Keep confidential reports, credentials and production data out of a first message; a secure exchange route is agreed before any of it moves. Indicative ranges are exactly that: the scope, exclusions and price are confirmed in a written proposal before work starts.