New articleSAP IS-U to S/4HANA Utilities: choosing between conversion, greenfield and selective transition

Pre-RFP advisory

Shape the RFP before vendors shape the scope

Before you issue an RFP for SAP IS-U, S/4HANA Utilities, BRIM, SuccessFactors or a related program, we help you assess the current state, map requirements to SAP standard versus extension versus custom, and write clearer scope language for vendors.

When it fits

Advice for the buyer, before the RFP

You are a utility or company preparing to issue an RFP for SAP IS-U, S/4HANA Utilities, BRIM, SuccessFactors or a similar program, and you want buyer-side advice before the document goes out.

We act as an advisor to your buying team. We do not sell a neutrality certification or claim to be an independent evaluator for every deal.

If we might also respond to the same RFP later, we will disclose that interest before the advisory work starts.

What you get

Pre-assessment, fit-gap and RFP-ready language

  • Current-state pre-assessment

    A structured look at the landscape, processes and pain points that will shape the RFP: systems in play, known custom code hotspots, data and integration dependencies, and what must stay in flight during a change.

  • Requirements mapped to fit-gap

    An inventory of stated needs mapped to SAP standard, released extension, or custom build. The goal is fewer vague must-haves and a clearer view of where vendors will diverge.

  • Scope and phasing inputs

    Draft boundaries for what belongs in the first release versus later phases, so responses are easier to compare and less likely to hide assumptions.

  • RFP-ready requirement language

    Plain requirement wording you can place in the RFP or supporting pack, written so vendors answer the same questions instead of reinventing scope.

Why buyers use it

Clearer scope, comparable bids

  • Fewer surprises in vendor responses

    When fit-gap is written before the RFP, responses spend less time inventing scope and more time answering the same baseline.

  • Clearer scope for the buyer team

    IT and business owners share one view of what is standard, what needs extension and what is truly custom before money is committed.

  • More comparable bids

    Shared requirement language and phase boundaries make it easier to score proposals against the same yardstick.

How it starts: A short call to confirm the RFP timing, the systems in scope and who owns the buying decision. Then we agree the advisory package and deliverables before any vendor outreach.

Related: How we engage, the S/4 readiness assessment, and S/4HANA Utilities readiness.

Talk through a pre-RFP pack

Bring the systems in scope and the date you want the RFP out. We will say whether this advisory fits before you engage vendors.