Vendor selection for the RISE implementation partner.

The selection of the implementation partner for a RISE with SAP conversion shapes the operational outcome as much as the SAP contract itself does. The partner runs the design workshops, sizes the work, mobilises the team, executes the cutover, and runs the hyper care period. The partner is also the source of most of the design decisions that the buyer will live with for years after go live. A buyer that runs a disciplined partner selection process captures the differences between partners in capability, in commercial structure, and in cultural fit before the engagement begins. A buyer that defaults to the partner SAP recommends, or that runs an abbreviated selection driven by relationship inertia, often signs an engagement that does not match the buyer profile and that surfaces structural problems six months into the work. This article describes the partner shortlist construction, the evaluation criteria that matter, and the contractual structure that aligns partner incentive with buyer outcome.

Construction of the partner shortlist

The shortlist for a RISE implementation partner typically comprises four to six candidates. The shortlist should include at least one global system integrator with a deep SAP practice, at least one boutique SAP specialist with strong vertical depth in the buyer industry, at least one mid tier consulting firm with a balanced SAP practice, and at least one regional partner with operational presence in the buyer geography. The four category structure produces a shortlist with genuine variation in cost profile, in delivery model, in vertical depth, and in operational accessibility.

The shortlist should not be filtered through the SAP account team. The SAP account team has natural alignment with the partners that contribute most to SAP commercial outcomes, which is not the same as the partners that produce the best buyer outcomes. The SAP account team recommendation is a useful input but should be weighed against the buyer independent assessment of the partner market.

The shortlist should also avoid the recency bias that surfaces in many buyer selection processes. The partner that ran the buyer last SAP project, even if the project was successful, is not automatically the right partner for the next project. The RISE conversion is a different shape of work from a typical SAP upgrade or enhancement, and the partner that performed well in one model may not perform well in the other.

The buyer should request from each candidate a list of named RISE conversion engagements completed in the prior twenty four months, with named buyer references, named project leadership, and named outcomes. The list is the substrate of the early shortlist evaluation. A candidate that cannot produce a substantive list of recent RISE conversion engagements should not be on the shortlist regardless of the candidate's reputation in adjacent SAP work.

The evaluation criteria that matter

The evaluation criteria for the partner shortlist should cover capability, commercial structure, cultural fit, and risk profile in roughly equal weight. The capability criteria assess the depth and the recency of RISE experience, the quality of the proposed delivery team, the maturity of the partner's accelerators and methodology, and the vertical depth in the buyer industry. The capability assessment should be conducted through technical interviews of the proposed delivery team rather than through written proposals alone. A partner that puts the proposed delivery team in front of the buyer for evaluation interviews demonstrates the substance behind the partner's reputational claims.

The commercial criteria assess the proposed fee structure, the risk sharing mechanism, the change order discipline, and the alignment of the partner economic interest with the buyer operational outcome. A fixed price engagement with weak change order discipline often produces a higher final cost than a time and materials engagement with strong governance. The commercial evaluation should consider the structure as well as the headline number.

The cultural fit criteria assess the partner working style, the responsiveness of partner leadership, the conflict resolution model, and the alignment between partner values and buyer values. Cultural fit is not a soft criterion. Engagements that fail at the cultural level rarely recover at the technical or commercial level, and the cost of a misaligned cultural fit shows up in friction across every project decision.

The risk profile criteria assess the partner financial stability, the depth of bench beyond the proposed team, the partner exposure to other concurrent engagements that might draw resources, and the partner contingency planning for staff turnover. A partner with a thin bench or with overcommitted resources may produce a successful proposal but a struggling delivery.

The reference check process

The reference check process is the single most informative element of the partner selection. The references should be conducted with named buyer counterparts on prior RISE engagements completed by the candidate partner. The reference questions should cover the actual versus planned cost, the actual versus planned timeline, the quality of the delivered system, the responsiveness of partner leadership to issues, the management of the offshore delivery centres if applicable, the handover of operations to the buyer team, and the post go live partner behaviour during defect remediation.

The reference check should also include at least one negative reference. Every partner has engagements that did not go well, and the candidate that cannot produce a balanced reference set including at least one challenging engagement is filtering the reference list rather than presenting it candidly. The negative reference, conducted carefully, reveals more about how the partner handles adversity than five positive references reveal about how the partner handles success.

The buyer should also conduct independent reference checks beyond the candidate provided list. Industry contacts, vendor advisory firms, and the SAP user group communities can provide unsolicited reference perspectives that are not curated for selection presentation. The independent references often surface patterns that the curated references do not.

The contractual structure

The contractual structure for the implementation engagement should reflect the buyer side priorities established through the selection process. The structure should include a milestone payment plan with a defined retention against go live and the post go live stability period. The retention amount should be material, typically ten to twenty percent of the total fee, with a release schedule tied to the achievement of defined acceptance criteria and the absence of defined material defects during the warranty period.

The structure should include change order discipline. Change orders should be structured with defined justification requirements, defined approval levels, defined budget envelopes, and defined documentation. The change order discipline prevents the gradual erosion of the budget through small uncontrolled additions that add to a material total without ever requiring escalated approval.

The structure should include a key personnel clause. The named delivery leadership at the proposal stage should be contractually committed for the duration of the engagement, with substitution requiring buyer approval. The key personnel clause prevents the bait and switch in which the partner proposes a senior team and then staffs the engagement with junior resources after signature.

The structure should include a defect remediation obligation. The partner should be contractually obligated to remediate defects against the acceptance criteria at no incremental cost for a defined warranty period, typically six to twelve months after go live. The defect remediation obligation aligns the partner incentive with the post go live stability of the system rather than with the rapid disengagement that the standard partner contract often produces.

The relationship between partner selection and SAP negotiation

The partner selection and the SAP negotiation are sequential rather than parallel for most buyers. The SAP contract is signed first, the partner is selected after, and the partner statement of work is finalised after the partner is selected. The sequencing creates a vulnerability. The partner becomes a stakeholder in the implementation cost of the SAP scope that has already been committed, which limits the buyer ability to negotiate the SAP scope downward based on partner feedback about the implementation complexity.

A more disciplined sequencing engages the partner shortlist in the SAP negotiation phase, with the shortlisted partners providing independent assessments of the proposed SAP scope, the implementation complexity, and the realistic timeline. The independent assessments give the buyer a counter position to the SAP statements about scope and effort, which is one of the most valuable inputs into the SAP commercial negotiation. The sequencing requires the buyer to manage the partner shortlist as a participant in the SAP negotiation, which is more complex than the sequential model but produces better commercial outcomes on both sides of the engagement.

Conclusion: the partner is the implementation

The partner that the buyer selects is the implementation. The SAP contract specifies the platform and the licensing structure. The partner contract specifies the team that designs, builds, and delivers the system that the buyer will actually operate. A buyer that runs a disciplined partner selection, with a balanced shortlist, with substantive evaluation criteria, with rigorous reference checks, and with a contractual structure that aligns partner incentive with buyer outcome, captures the difference between a partner that completes the project and a partner that delivers the system. A buyer that defaults to the SAP recommended partner, or that runs an abbreviated selection driven by relationship inertia, accepts the partner outcome that the partner itself prefers. The partner selection deserves the same rigor that the SAP negotiation receives, because the operating consequences of the partner choice persist for as long as the operating consequences of the SAP choice.