CTOPODIAOctopodiaTalk to me
Dark Atlantic swell under heavy weather

Octopodia

I break SAP systems before your users do.

Your go-live decision, backed by evidence.

Talk to me

What you get

Maybe it’s a greenfield, maybe it’s an upgrade. These days, it’s probably S/4 (although I started on 3.1i).

But before you switch on that SAP system for thousands of people, you need to prove it can carry your real business at full production scale, safely, before anyone depends on it.

That includes the month-end close, the Monday-morning login storm or the Christmas rush.

That’s what I do.

So when someone asks “Can you show me it’s ready?” or “we’ve tested that, right?” you can say yes.

And go live on evidence, not hope.

Talk to me

The process

Sounds easy…

  1. 1

    Model how your business uses SAP.

  2. 2

    Recreate that demand at production scale, in a safe environment.

  3. 3

    Break it. Whatever fails in the test won’t fail on your go-live.

  4. 4

    Fix and retest until every defect is proven closed. Not recorded, but removed.

  5. 5

    Hand over the evidence and the scripts, workload and baselines, so you can prove every future change too.

(It isn’t.)

Who it helps

In the last few years I’ve helped:

  • A global FMCG go live with S/4 with no performance issues.

  • A UK utilities company avoid a critical issue with their HR system that would have taken weeks to fix in production.

  • A professional services company build a repeatable test pack for each release.

Go-live isn’t a hunch, a guess, or a prayer. It’s a fact.

The bald one in the corner of the room.

I’m Paul, and I’ve spent around twenty five years performance testing SAP for organisations across Europe - implementations, upgrades, S/4HANA migrations, systems that had to print a pallet label every second or pay forty thousand people on Friday.

Most of my proudest work is invisible: disasters that never happened. Easy go-lives. Support teams with nothing to do. Executives who moved on to the next project without ever learning my name.

Along the way I’ve heard every reason not to test. “Hardware is cheap.” “We’re in the cloud, we’ll scale.” “We’ve never had problems before.” I’ve seen these reasons crash on the rocks of reality. Tin might be cheap but a P1 in production is not. Especially if the problem was never tin.

I’ll tell you the truth about your system, even when it’s uncomfortable. Especially then. That’s what you’re paying for.

Irish Atlantic coastline in stormy weather