Skip to main content
    Current language: English
    Back to profile

    ENG-001 / Advisory

    Independent SAP Ariba and S/4HANA advisory, from someone who has run the operation, not just the slide deck.

    Twelve years inside source-to-pay programs at global scale: $20B of annual spend, 380,000 users, 99.8% SLA delivery. Engagements are scoped small, start with evidence, and end with something your team can operate without me.

    Book Consultation Book consultation
    01 / Engagements

    Four ways this usually starts.

    A

    Rollout design review

    Before you build: dependency order, purchasing-unit model, catalog and policy strategy, and the decisions that are expensive to reverse later.

    • Guided buying and guided sourcing enablement sequencing
    • Purchasing-unit and landing-page scoping matrix
    • Realistic effort and phasing against your scope
    B

    Ariba to S/4HANA integration review

    CIG or CPI, master-data sync, cXML document flow and the failure points between the two systems that nobody owns until go-live week.

    • Document chain traced end to end
    • Master-data and commodity-code readiness
    • Error monitoring and ownership model
    C

    Troubleshooting and rescue

    A program that stalled, a hypercare queue that will not drain, or a symptom nobody can localize between Ariba, the ERP and the supplier.

    • Structured triage across the document chain
    • Root-cause write-up your team can act on
    • Escalation package ready for SAP where needed
    D

    Operating model and enablement

    Support structures, run-book design and coaching so the configuration you paid for keeps working after the integrator leaves.

    • Support tiering and ownership boundaries
    • Run-books for recurring failure patterns
    • Workshops for admins and functional buyers
    02 / How it works

    Small, evidence-first, no long procurement cycle.

    1. 01

      Consultation call

      Thirty minutes on your landscape, release and the problem as you see it. No charge, no deck.

    2. 02

      Scoped first piece

      A bounded review or diagnostic with a fixed scope and a written output, so you can judge the work before committing further.

    3. 03

      Findings and decisions

      Written findings, ranked by what they cost you, with the decisions that belong to your team clearly separated from the ones I can make.

    4. 04

      Delivery or handover

      Either I stay through implementation, or your team runs it with the run-book. Both are fine outcomes.

    03 / Fit

    Where this helps, and where it does not.

    Good fit

    • SAP Ariba deployments already live, or in design with real constraints
    • Ariba and S/4HANA integrated landscapes
    • Programs with a symptom nobody can attribute to a layer
    • Teams who want to own the system afterwards

    Poor fit

    • Staff augmentation by the head count
    • Non-SAP procurement suites
    • License resale or implementation subcontracting
    • Work that needs a body on site full time, long term
    04 / Track record

    The numbers behind the advice.

    Annual spend under management
    $20BAnnual spend under management
    Users supported across programs
    380kUsers supported across programs
    SLA delivery against a 99% target
    99.8%SLA delivery against a 99% target
    Source-to-pay operations experience
    12 yrsSource-to-pay operations experience

    Read the free guides first

    05 / Section

    Consulting questions

    How do engagements start?
    With a thirty-minute consultation call about your landscape, SAP Ariba release and the problem you are seeing. If there is a fit, the next step is a bounded review or diagnostic with a written output before any longer commitment.
    Do you work remotely?
    Yes. Engagements run remotely across time zones, with working sessions scheduled around your team. Prior delivery has covered L2 teams across two continents.
    Which SAP Ariba areas are covered?
    Guided buying, guided sourcing, supplier lifecycle and performance, contracts, supplier risk, and the integration between SAP Ariba and S/4HANA through CIG or CPI.
    Can you help a program that is already in trouble?
    That is a common starting point. The first step is structured triage across the document chain to localize the failure before anyone proposes a fix, followed by a written root-cause summary your team can act on.
    What does an engagement cost?
    Scope drives the number, so it is agreed after the consultation call and confirmed in writing before work begins. Reviews and diagnostics are quoted as fixed-scope pieces rather than open-ended time.
    06 / Request

    Request a consultation

    Thirty minutes on your landscape and the problem as you see it. Tell me what you are running and what is not working — you will get a reply by email.

    Engage

    Start with a thirty-minute consultation.

    Send your landscape, release and the problem in a paragraph. You will get a reply within one business day.