01The problem
Most system projects do not fail technically. They fail because nobody owned the decision: the vendor waits for the client, the client waits for the vendor, and the process never changes. I take the owner's seat on your side.
Who it is for
- A system project has started, the schedule is slipping and the scope is growing.
- A large project you don't want the vendor running alone.
- Nobody in the company has the time or experience to stand across the table from the vendor.
02What the engagement includes
- Requirements and a written specification before you meet a single vendor
- Vendor evaluation and technical negotiation
- A phased delivery plan with written acceptance criteria
- Change management with the teams who will use the system daily
- Governance and operating policy after go-live
03Stages
- 01 Assessment Reading the current process as it is actually practised, not as it is documented.
- 02 Selection Written requirements, vendor comparison, and a decision based on criteria rather than a slide deck.
- 03 Delivery Weekly follow-up, acceptance testing, and clearing blockers before they become delays.
- 04 Operation Knowledge transfer to your internal team, and policies that keep the system running after my engagement ends.
05Common questions
Do you replace the vendor?
No. The vendor implements their system; I represent your interest opposite them: defining what you need and verifying that what shipped is what was agreed.
What size of project suits this?
From a mid-size company implementing its first system to a factory connecting production to management. Anything smaller rarely needs a third party.
A systems project that is stalling, or has not started yet?
One message is enough to know where to start. I'll reply within one business day.