Budget is approved, the board is watching, your shortlist is forming – this is the moment that will define whether your SAP programme delivers what it promised or becomes a case study in what not to do.
Most organizations evaluating SAP delivery partners focus on the wrong things. They score presentation quality, count certified consultants, and compare day rates. What they don't do is ask the questions that actually predict delivery success.
This guide gives you a framework for independent SAP partner assessment in 2026, built on what we've seen work and what we've seen fail.
The SAP delivery partner market isn't a level playing field; the largest system integrators have dedicated bid teams whose sole job is to win your RFP. They’re very good at it, but that doesn't mean they're the right partner for your programme.
The gaps between what gets sold and what gets delivered are real, and they're common. Consultants named in the proposal don't show up on day one; pricing structured around a fixed scope starts moving the moment you sign; and the senior partner who led the pitch hands over to a delivery team you've never met.
None of this is a secret, but when you're under pressure to select and move fast, it's easy to mistake a polished proposal for a credible delivery plan.
Your job during SAP SI selection is to see past the pitch.
Every major SI will give you a reference list. What you need to understand is whether those references are genuinely comparable to your situation, not just your industry.
Ask specifically:
A partner confident in their delivery record will answer these questions directly. One that deflects or redirects to headline clients is telling you something.
This is the single most common source of post-contract disappointment in SAP implementation. The people who sell the programme are rarely the people who deliver it.
Push hard on this during evaluation. Ask for the CVs of the actual delivery leads, the solution architect, and the key functional consultants. Ask what happens if those individuals are pulled onto another engagement. Get the answers in writing, and make sure your contract reflects them.
Every SAP programme encounters scope questions. How your partner handles those moments will define your relationship for the next two to three years.
Ask them to walk you through a real situation where scope was contested. How did they communicate it? How was it resolved? What did it cost the client? A good partner will be honest. A partner focused on winning the deal will give you the answer they think you want to hear.
The best SAP delivery partners build your organization's capability, not dependency on their own. Watch for signs that a partner is designing a model that requires them to stay long after go-live.
Ask what they do to transfer knowledge. Ask how they measure whether your team is ready to operate the system independently. Ask what post-go-live support looks like and what it costs.
How a partner structures their commercial proposal tells you a great deal about how confident they are in their own delivery. A fixed-price proposal built on assumptions they haven't validated is not a sign of confidence. It's a risk transfer mechanism.
Understand exactly what is and isn't included. Understand how change requests are scoped and priced. Understand what your exit options are if things go wrong.
There's also a less visible consideration that runs through all five: cultural fit. It's harder to score than cost or technical capability, but it can have a greater impact on how your programme performs when difficult decisions arise. We’ll come back to that later.
These are the warning signs we see most often when reviewing partner proposals and pitch presentations.
Vague resourcing plans – If the proposal talks about "a team of experienced consultants" without naming them, that's not a plan. Push for specifics.
Pricing that's significantly lower than competitors – Occasionally this reflects genuine efficiency. More often it reflects an undercooked scope that will expand after contract signature.
Resistance to reference calls – Any partner worth selecting will welcome reference conversations with past clients. Reluctance is a red flag.
A go-live timeline that matches your preference, not their experience – If every partner on your shortlist is quoting a different timeline and one of them has conveniently matched the date you mentioned in the brief, treat that with caution.
Heavy focus on technology, light focus on change – A partner who leads every conversation with product features and says very little about how your organization will adopt and embed the change is showing you where their priorities are.
An inability to explain what could go wrong – Confident, experienced partners can tell you exactly where the risks are on a programme like yours. Partners who present a risk-free picture either haven't done the work or aren't being straight with you.
A well-run SAP RFP process does more than collect comparable proposals. It tests how your potential partners think, communicate, and behave under pressure.
Define your evaluation criteria before you issue the RFP – Score weighting should reflect what you actually care about, not what's easiest to compare.
Issue a realistic brief – Vague requirements produce vague proposals. The more specific you are about your landscape, your constraints, and your success criteria, the more useful the responses will be.
Run structured reference calls yourself – Don't let the partner manage the reference process. Ask your own questions and speak to people at a similar level to you in the client organization, not just the ones the partner puts forward.
Include a structured challenge session – Ask each partner to present their risk register for a programme like yours. Ask them what they would do differently if they were you. The quality of those answers will tell you more than any written proposal.
Involve your internal team in the evaluation – The people who will work with this partner every day should have a voice in the selection; their instincts matter.
Most organizations go into SI selection with the best intentions and limited independent perspective. They rely on the information the partners themselves provide, supplemented by analyst reports that are often funded by the same firms being assessed.
That's not due diligence. That's managed information.
Independent SAP partner assessment means working with someone who has no commercial relationship with any of the partners on your shortlist. No referral agreements. No preferred partner status. No financial reason to steer you toward one firm over another.
At Resulting, that's exactly what we are. We've worked alongside most of the major SIs. We know their strengths, their delivery patterns, and where the gaps between their pitch and their delivery tend to appear. We bring that knowledge to your evaluation, not a sales agenda.
Cultural fit is often treated as a softer consideration in SAP partner selection, but it shouldn't be.
Cultural fit isn't about whether you like the people in the room, or whether the pitch team feels personable. It's about whether your organization and your implementation partner will work effectively together when the programme becomes difficult.
Because it will become difficult.
There will be scope decisions, missed dependencies, conflicting priorities, difficult data conversations, and moments when the original plan no longer reflects reality. The partner you choose needs to be able to challenge you when necessary, listen when challenged, and deal with problems directly rather than allowing them to grow quietly in the background.
You need to understand how they work, not just what they say they can deliver.
Ask yourself:
These questions matter because a partner can have outstanding technical credentials and still be a poor fit for your programme.
A highly structured organization may need a partner that's disciplined, formal, and comfortable working through detailed governance. A business that needs to move quickly may value a partner that can make decisions, adapt to change, and work with less hierarchy. Neither approach is automatically better, the important thing is if the way of working matches your needs.
Make sure you meet the delivery leads, solution architect, and key functional consultants; give your team the opportunity to challenge them directly and observe how they respond.
A structured cleanroom or challenge session can be particularly useful here. Ask your shortlisted partners to work through a realistic programme issue, such as a delayed design decision, a disputed scope item, or a business team that's not ready for testing. You'll learn more from how they handle the discussion than from another polished presentation.
Afterwards, ask your team for an honest view. Who would they trust when the programme is under pressure? Who listened properly? Who gave a clear answer? Who was willing to say what could go wrong?
Cultural fit may be difficult to score with the same precision as cost or technical capability. That doesn't make it less important; in practice, it can be the factor that determines whether the other criteria translate into successful delivery.
The right partner should bring capability, experience, and commercial discipline. They should also be someone your team can work with when the plan changes and the pressure rises. That's when cultural fit stops being a nice-to-have and starts affecting your timeline, budget, and business case.
These four questions will tell you more about a partner's real delivery capability than any written proposal.
These are just a starting point. For further guidance, speak to our team.
SAP partner selection is not a procurement exercise, it's one of the most consequential decisions your organization will make this year. The cost of getting it wrong far outweighs the cost of getting independent support to get it right.
You wouldn't make a major legal decision without independent legal advice. This is no different.
If you want help choosing the right implementation partner for your programme, give us a call, or download our S/4HANA SI selection guide for more information.