RFP Pitfalls: What SAP Implementation Teams Wish Procurement Knew

Arjun Mehta breaks down what you need to know

I’ve sat through too many RFP evaluations where the winning vendor delivered a flawless scripted demo—and then stumbled the moment real data hit the system. After 25 years of living inside ABAP code, SAP integrations, and more than a few painful cutovers, I can tell you that most enterprise software RFPs are built for the vendor’s sales deck, not your implementation reality.

The good news? The fixes are straightforward. The hard part is convincing procurement teams to stop buying software like they’re ordering office furniture.

The Real Story

Most RFP processes are structured around feature checklists and scripted demos. Vendors send their best sales engineers, load a pristine sandbox with exactly the data that makes their product shine, and walk through flows that have been rehearsed dozens of times. You score them, pick the highest feature count, and sign. Then the implementation team walks in and finds out that your seven custom legacy interfaces don’t map to anything the vendor has ever seen.

I saw this firsthand on an S/4HANA migration RFP for a mid-size manufacturer. The winning vendor scored 94% on functional demos. Their references were excellent. Data migration, integration, and cutover together made up less than 10% of the total scoring weight. A year later, the project was two months behind, and the cutover plan had to be reworked three times because no one had asked how the vendor would handle the client’s custom IDoc transformations or their 14 years of archived pricing data. The vendor wasn’t incompetent—they just hadn’t been evaluated on the things that actually make or break an SAP implementation.

What This Means for You

If you’re a consultant or solution architect sitting on the RFP evaluation team, your role is to inject implementation reality into a procurement process that often rewards marketing polish. If you’re a manager or executive, you need to understand that the RFP is not just a vendor selection tool—it’s a project plan in disguise. The questions you ask today determine whether your implementation team walks into a greenfield or a minefield.

Here’s what I’ve learned to demand in any SAP-related RFP:

• Scenario demos on your data. Stop accepting scripted demos. Give each vendor a sanitized but realistic dataset—a few thousand material master records, open purchase orders, legacy billing data. Ask them to show how their solution handles duplicate vendors, incomplete material groups, or a failed IDoc during order creation. The goal is not to see perfect flows; it’s to see how the vendor responds when things don’t match the sales script.

• Explicit scoring for migration, integration, and cutover. These are the silent killers of SAP projects. I’ve been called into rescue projects where the RFP had 40 pages of functional requirements and exactly one paragraph on data migration. That’s backwards. Data migration, integration design, and cutover execution should be at least 30–35% of the total RFP score. If procurement pushes back, remind them that a perfect configuration means nothing if you can’t move your historical data safely or keep your EDI interfaces running.

• Measurable outcomes from similar engagements. Don’t settle for “we’ve done 50 S/4HANA projects.” Ask for post-go-live stability metrics: average number of high-priority incidents in the first 30 days, how many cutover cycles were rehearsed, what percentage of data objects were loaded successfully on the first attempt, and how long it took to reach production stability. Any vendor with serious implementation chops tracks these numbers. If they can’t provide them, that’s a red flag.

• Named delivery team composition. Sales engineers sell; delivery teams deliver. Too many RFPs evaluate the sales pitch and never ask who will actually be on your project. Require a named delivery lead, a named integration architect, and a named data migration lead in the proposal. I don’t need a bench list—I need to know those three people have done this exact work before. If the vendor won’t commit names before contract signing, be prepared to see their A-team vanish after the first steering committee meeting.

• Internal process owners and decision rights before vendor selection. This is the one that makes me pound the table. I’ve watched implementations stall for months because the client hadn’t defined who owns master data, who approves the chart of accounts design, or who can decide on a cutover window. The RFP process should force that clarity before you bring in an implementation partner. If your internal team can’t answer “who signs off on the final data migration plan?” then you are not ready to select a vendor.

Action Items

If you’re involved in an SAP or enterprise software RFP right now, here are the changes I’d push for this week:

• Rewrite the demo requirements. Replace feature-by-feature click-throughs with two or three scenario-based workshops using your own data. Score vendors on how they handle the messy parts, not just the happy path.

• Rebalance the scoring model. Create a separate scoring category for data migration, integration architecture, and cutover planning. Give it real weight—at least 30%. Procurement will resist; implementation teams should insist.

• Ask for post-go-live metrics from three references. Don’t just ask “would you hire them again?” Ask about the first 60 days after go-live: incident counts, workaround counts, batch job failure rates, and how quickly the vendor responded to critical issues.

• Lock down internal decision rights. Before you issue the RFP, document who owns master data, who approves integration changes, and who has final say on cutover timing. If you don’t know, stop the RFP until you do.

• Evaluate delivery team, not just feature coverage. Include a scored section for the proposed team’s hands-on experience with your specific SAP modules

References

• What Implementation Teams Wish Organizations Knew About Enterprise RFPs- What Implementation Teams Wish Organizations Knew About Enterprise RFPs- SAP Integration Suite Help Portal

References

• What Implementation Teams Wish Organizations Knew About Enterprise RFPs
• What Implementation Teams Wish Organizations Knew About Enterprise RFPs
• SAP Integration Suite Help Portal