# ERP Implementation Partner Evaluation Worksheet > Source: https://netray.co/tools/erp-implementation-partner-evaluation-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Score system integrators and ERP partners on experience, team, method, references and commercial terms, with a weighted total for each criterion. ## Category erp-migration ## Audience - CIO - ERP project lead - Procurement ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Criterion **Key:** criterion **Type:** text #### Weight (%) **Key:** weight **Type:** number #### Partner A (1-5) **Key:** partner_a **Type:** number #### Partner B (1-5) **Key:** partner_b **Type:** number #### Partner C (1-5) **Key:** partner_c **Type:** number #### A weighted **Key:** wa **Type:** number **Expr:** weight * partner_a / 5 **Format:** decimal #### B weighted **Key:** wb **Type:** number **Expr:** weight * partner_b / 5 **Format:** decimal #### C weighted **Key:** wc **Type:** number **Expr:** weight * partner_c / 5 **Format:** decimal #### Evidence / notes **Key:** evidence **Type:** text **Rows:** **Criterion:** Product certification and years on this ERP **Weight:** 15 **Partner a:** 5 **Partner b:** 4 **Partner c:** 3 **Evidence:** Certificates, number of go-lives **Criterion:** Manufacturing industry references **Weight:** 20 **Partner a:** 4 **Partner b:** 5 **Partner c:** 3 **Evidence:** Two reference calls each **Criterion:** Named team quality and continuity **Weight:** 20 **Partner a:** 3 **Partner b:** 4 **Partner c:** 4 **Evidence:** CVs, interviews with leads **Criterion:** Methodology, data migration and testing approach **Weight:** 15 **Partner a:** 4 **Partner b:** 4 **Partner c:** 3 **Evidence:** Sample plan, test strategy **Criterion:** Local presence and support after go-live **Weight:** 10 **Partner a:** 4 **Partner b:** 3 **Partner c:** 5 **Evidence:** Support model and hours **Criterion:** Commercial terms and price transparency **Weight:** 15 **Partner a:** 3 **Partner b:** 4 **Partner c:** 4 **Evidence:** Fixed price share, rate card **Criterion:** Cultural fit and communication **Weight:** 5 **Partner a:** 4 **Partner b:** 4 **Partner c:** 4 **Evidence:** Workshop observation **Totals:** #### Total weight (must be 100) **Key:** weight **Agg:** sum **Format:** integer #### Partner A score **Key:** wa **Agg:** sum **Format:** decimal #### Partner B score **Key:** wb **Agg:** sum **Format:** decimal #### Partner C score **Key:** wc **Agg:** sum **Format:** decimal **Summary:** #### Highest weighted score **Key:** leader **Expr:** max(sum_wa, sum_wb, sum_wc) **Format:** decimal **Primary:** true #### Gap between A and B **Key:** gap **Expr:** abs(sum_wa - sum_wb) **Format:** decimal **Notes:** Weights should add to 100 and be set before you see partner proposals. A gap of less than three points between partners is within noise, so decide using references, the named team and commercial terms. ## Content **Intro:** The software gets the attention, but the implementation partner usually decides whether an ERP project succeeds. This worksheet scores partners on the same weighted criteria so the choice rests on evidence about the team that will actually do the work. **Sections:** #### How to use the worksheet **Body:** Agree the criteria and weights with the steering committee first, then score each partner from 1 to 5 after proposals, interviews and reference calls. The sheet multiplies weight by score divided by five, so a perfect partner earns exactly 100. Replace the example rows with your criteria, and write what evidence supports each score. Export to Excel for the decision file. **Bullets:** - Weights add up to 100 and are fixed before scoring - Interview the proposed project manager and lead consultants - Call at least two references per partner - Record evidence for each score #### Criteria that predict success **Body:** Experience on the specific ERP product and version matters more than a partner's size. Ask how many comparable go-lives the proposed team members have personally delivered, not the firm. Manufacturing references with a similar mix of discrete, process or project work reduce risk. Check methodology for data migration, testing and cutover, because these are where most schedules slip. #### Commercial terms **Body:** Compare fixed price and time and materials honestly. A fixed price for a vaguely defined scope often turns into change orders. Ask for the rate card, the named resources, the substitution rules and how the partner treats overruns it causes. Include warranty or hypercare terms and what happens to the team if a key person leaves. Weight this criterion enough that a very cheap bid with a thin team does not win on price alone. #### Common mistakes **Body:** Do not accept a strong sales team as evidence of a strong delivery team. Do not let the ERP vendor's preferred partner skip evaluation. Do not score on gut feeling after a pleasant workshop; attach evidence to every row. If scores are within a few points, rely on references and the quality of the named team. **Cta:** If you are using Infor SyteLine, M3 or LN, Netray works alongside implementation partners on AI, reporting and migration accelerators, and can join partner evaluation calls on the technical side. **Faq:** #### Should I pick the ERP vendor or the partner first? **Answer:** Evaluate both in parallel when you can, since the best software with a weak local partner can fail. At minimum, assess the partner before signing the software contract so you can walk away from a pairing that does not work. #### How many partners should I compare? **Answer:** Two to three per shortlisted ERP is workable. More than that increases effort without improving the decision, especially for regional ERPs with a limited partner network. #### What are red flags in a partner proposal? **Answer:** No named team, no manufacturing references, unclear data migration scope, resource rates far below others, and refusal to allow reference calls with the project managers who delivered earlier projects. #### Should price carry more than 15 percent weight? **Answer:** It can, but the weight should reflect that low rates often mean junior staff. Many teams score price separately on total expected cost, including likely overruns, rather than on the headline rate card alone. ## Search terms erp implementation partner evaluation, erp system integrator selection template, how to choose erp implementation partner, erp consultant scorecard, erp partner selection criteria, system integrator evaluation excel --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json