Don’t Green Light Your S/4 Transition Just Yet.

See where it breaks before you sign.

The 30-Day FIT 4 SAP Proof of Concept.

In other words…
Your Insurance Policy Before You Commit →

One deliverable.
Clear scope.
Clean core.
30 days.
No surprises.

You think this too good to be true? Read me first…

Your last implementation went 40% over budget and delivered 60% of value.
Consultants vanished after go-live.
The board wants proof before signing another contract.

I get it. That’s why I built this.

Watercolour of Isard Haasakker in glasses and an open-necked white shirt, sleeves rolled up, at a whiteboard in a boardroom in late golden light, pointing with a pink marker at a hand-drawn sequence: a FIT 4 SAP shield, then a Statement of Work (SOW) with a tick, then SAP Activate. Four managers in business casual listen around the table, mugs, water glasses and notebooks in front of them, a city skyline in the window.

For £50k, you discover the problems now, not when your S/4HANA project is on fire.
This is not an assessment, but a prototype of your most critical scenario in clean-core S/4HANA.
This gives you negotiation leverage for the Statement of Work.
Then I step back.

What Makes FIT 4 SAP Different.

Traditional Proof of ConceptFIT 4 SAP Proof of Concept
Show what worksShow what breaks. A prototype of your critical scenario in clean-core S/4HANA, not a report about it.
Sell the senior, staff whoever is availableDo the work myself. The person you meet is the person who builds.
Hold discovery meetingsWalk the floor. I talk to the people doing the work and find the workarounds nobody documented.
Negotiate to yesLet the evidence decide. Green light, fix the gaps, or redesign.
Stay for the implementationStep back after day 30. I have no stake in your implementation contract.
Free of chargeCharge a fixed £50k. A free prototype is built to work; this one is built to break.

Why this works →

Watercolour illustration: a smiling bald manager in an open-necked light blue shirt, sleeves rolled up, seated at a polished desk with his hands clasped, a city skyline at sunset in the window behind him.

The Offer.

For the CEO who has to say yes, or no.

30 days.
One prototype.

Three possible outcomes:

  • Green light with confidence: Standard S/4HANA handles your scenario. Proceed to full implementation knowing it works.

  • Fix gaps before committing: We found the breaks. We prototyped the solutions. You know exactly what custom rules you need.

  • Redesign with evidence: Your operating model may need rethinking. Better to know now than after £10M spent.

You don’t get vendor promises.

You get governance receipts.

  • Scar Log: Every gap revealed, logged, owned. No hidden problems.

  • Decision Register: Every choice documented with who, why, when. No forgotten assumptions.

  • Board Pack: Ten slides that tell the truth. Evidence, not optimism.

Watercolour illustration: a smiling manager with a grey-blonde bob and glasses, arms folded, in an open-necked white shirt and navy trousers, standing in an office with a city skyline at sunset behind her.

What Happens when Things Go Wrong?

For the CIO who will own what breaks.

When things break during the 30 days, I don’t pretend everything is OK.
In fact, it’s better to break it now, before you commit, than weeks before go-live.
Together we test what a Clean Core S4 has to offer.

Then, we pivot into Findings-First Mode.
This is when the 30-Day Proof of Concept earns its keep.

We document every scar: every gap, every risk, every unanswered question.

You still get delivery on Day 30.
Not a fake demo.
Complete transparency about what worked and what didn’t.
Board-ready materials you can trust.

No theatre.
No spin.
No hidden risk.

Watercolour illustration: a smiling manager with fair hair pulled back and a blue patterned scarf over a white shirt, seated in an armchair with her chin on her hand, a city skyline at sunset in the window behind her.

Rules Of Engagement.

For the CFO who signs the cheque.

FIT means two things:

  • Fit into Clean Core S4: No bloated customisations. Future-proof configuration.

  • Fast Implementation Track (F.I.T.): My governance discipline built from 30 years of seeing what breaks.

And FAST within FIT stands for Focus And Simplify Transformation.
Don’t aim to go-live as quickly as possible. Aim never to delay go-live.
That is the real money saver.
Your money is saved before you sign the Statement of Work.

We agree upfront on the ONE critical thing to prove.
Scope locks.
Fee is paid.
The rules don’t change mid-flight.

That is why the Questionnaire is so important.
It gives clarity before you commit to the Statement of Work.

Most S/4HANA overruns trace back to the same mistake: trying to do everything at once.
FIT 4 SAP proves the one thing that truly matters first.

This isn’t a demo.
It’s a disciplined 30-day pressure cooker designed to prevent you becoming the next failed case study.

Watercolour illustration: a manager with curly greying hair and a beard, in a navy cardigan over an open-necked shirt, seated with his chin resting on his hand and a knowing smile, a city skyline at sunset behind him.

Check Your Scenario Before You Commit.

For the programme lead who knows where it hurts.

A short diagnostic to see if a 30-day S/4HANA prototype makes sense for you.
Your details are only used to send the questionnaire.

No follow-ups. No mailing list. No pressure.
See the privacy policy.

Explore The Methodology.

You don’t need promises.
You need to see how this actually works.

Three pathways.
Take whichever you need first.

Watercolour of four managers in business casual standing around a flip chart in a boardroom in late golden light. One of them, a woman with glasses, ticks the last of three boxes with a pink marker beside a FIT 4 SAP shield: Questionnaire, Scope Agreement, Proof of Concept. The others look on, smiling. Mugs, water glasses and notebooks on the table, a city skyline in the window.

How Does It Work?

The full four-phase breakdown.
The pre-PoC questions that expose hidden complexity.
The week-by-week delivery rhythm.
The conditions for green light, fix the gaps, or redesign.

What You Get

The governance artefacts explained in plain English.
Scar Log. Decision Register. Board Pack.
What “Findings-First Mode” looks like when things break, and why that’s a good thing.

Why It Works

The governance philosophy that sits beneath the prototype.
Why constraints reveal truth.
Why scope locks prevent drift.
Why Clean Core matters.
And how the Fast Implementation Track principles hold everything together.