Choosing an SAP S/4HANA partner: what to ask in 2026

Start with the deployment model, not the partner logo

The most common failure mode in S/4HANA partner selection is running an RFP before the deployment model is agreed internally. RISE with SAP, GROW with SAP, Private Cloud Edition, Selective Data Transition and greenfield BTP-first delivery are not interchangeable. They attract different partner strengths, different SAP field involvement, and different commercial constructs. Shortlist against the deployment model you have committed to, not against the largest partner logos in your region. A Platinum partner with limited GROW references is the wrong answer for a mid-market fit-to-standard rollout, regardless of brand.

If the deployment model is genuinely undecided, that is a discovery engagement, not a selection engagement. Run it with two partners on a fixed-scope, fixed-fee basis and use the outputs to run the real selection afterwards. Conflating the two collapses commercial leverage and produces a partner locked in for the wrong reasons.

The five filters that separate real S/4HANA capability from slideware

Every S/4HANA partner will claim depth on your chosen deployment model. Five filters, applied in order, cut a longlist of twenty to a workable shortlist of three without needing to sit through a single deck.

• Deployment-model references shipped in the last 18 months, in your industry, at a comparable scale. Fewer than three is a red flag regardless of tier.
• SAP Partner Business Manager (PBM) signal. Ask SAP directly which partners they would route your named account to. The answer is more honest than any capability deck.
• Named delivery leadership. Who is the programme director, solution architect and change lead on your engagement, and are they contractually committed, not just on the org chart.
• Clean-core discipline. How the partner treats extensions, modifications and BTP side-by-side patterns. Partners still selling in-stack customisation are optimising for their bill rate, not your TCO.
• Commercial construct. Fixed-scope where fit-to-standard applies (GROW), phased fixed-price for defined workstreams, and time-and-materials only where genuinely justified by scope volatility.

What the SAP field team is actually signalling

Every serious S/4HANA selection should include a structured conversation with your SAP account executive and PBM. They will not tell you which partner to pick, and they should not. What they will signal is which partners have delivered reference-able projects for accounts like yours, which partners are currently over-committed on programmes in your region, and which partners have registered opportunities that would create a conflict of interest. Treat that conversation as intelligence, not endorsement. The partners with the strongest PBM relationships have usually earned them by generating their own demand rather than waiting for referrals - a topic covered in the SAP partner marketing strategy guide and outbound for SAP S/4HANA delivery partners.

Questions that surface real capability

Every capability deck answers the questions you would expect. The questions below are less expected, and the answers are diagnostic. Ask them in a working session, not an RFP response, and pay attention to who in the room actually answers.

1. Walk us through your last three projects on this deployment model. Name the programme director, the customer, the timeline, the RICEFW count and the two things that went wrong.
2. Show us the clean-core scorecard from your most recent Private Cloud Edition or GROW project. If there is not one, explain how you make extension-versus-modification decisions.
3. Which two competitors do we see you against most often on programmes of this shape, and where do you consistently lose?
4. How is the delivery team you are proposing insulated from being pulled onto other programmes mid-flight? What is the contractual mechanism?
5. Which two things about our current ECC estate or industry constraints are you most concerned about, and why?
6. What is your view on where SAP Business Data Cloud, Datasphere and third-party platforms like Snowflake or Databricks fit against our reporting requirements?

What good reference calls look like

Every shortlisted partner will provide references. The pattern of who they offer, and who they will not, matters as much as the calls themselves. Ask for references on the specific deployment model, in the specific industry, and specifically ones where the programme did not go smoothly. A partner unwilling to provide a difficult reference is a partner unwilling to have the difficult conversation on your programme.

• Two references on the same deployment model, in the same industry, at a comparable scale.
• One reference on a project that went off track and was recovered. Ask the customer what the partner did differently, and what they wish had happened sooner.
• One reference where the customer is 12+ months post go-live, so you can see how the partner behaves once the SOW is closed.
• Direct conversations, not curated case studies. If the partner insists on being on the call, that is a signal about their default operating mode.

The S/4HANA partner selection funnel

For a mid-market or lower-enterprise S/4HANA programme, the numbers below reflect what a disciplined selection process looks like when run over roughly 90 days. The intent is to compress calendar time without compressing scrutiny.

Red flags that should end the conversation

• A capability deck that names every SAP module and every industry with no visible specificity on your deployment model.
• The proposed delivery team differing significantly from the team in the pitch, with no clear escalation path if that happens again mid-programme.
• Reluctance to commit to a clean-core approach, or a proposal that quietly reintroduces heavy in-stack customisation to protect scope.
• A commercial construct that transfers every risk to the customer while retaining fixed-price certainty for the partner.
• Unwillingness to run a paid, fixed-scope discovery engagement before the main programme.

Where the data platform decision fits

Almost every live S/4HANA programme in 2026 sits next to a parallel decision about the analytics and data platform, typically SAP Business Data Cloud alongside Snowflake, BigQuery or Databricks. Selecting an S/4HANA partner without a defensible view on that adjacency creates unnecessary rework in year two. Whether the partner has genuine credibility with data platform buyers matters, and the Snowflake partner outbound guide and Google Cloud partner outbound guide are useful context for what strong capability looks like on the other side of that boundary.