Choosing an ERP integrator is one of the highest-stakes decisions a company makes during a transformation project. Get it right and you gain a partner who accelerates delivery, limits risk, and transfers knowledge to your team. Get it wrong and you inherit months of rework, budget overruns, and organizational fatigue that can take years to repair.
The challenge is that every integrator pitches roughly the same story: proven methodology, certified consultants, references, post-go-live support. When all three shortlisted vendors sound identical, how do you actually decide?
You need a scoring framework --- one that forces every candidate through the same structured evaluation, replaces gut feeling with evidence, and produces a score you can defend to your steering committee.
This article gives you exactly that: a 100-point framework across 10 criteria, a step-by-step RFP process, the red flags you should never ignore, and negotiation tips that protect your interests.
This article is part of the complete ERP implementation guide. If you are earlier in the journey, start there for the full roadmap.
Why a Scoring Framework Matters
Without a structured approach, integrator selection degrades into a beauty contest. The vendor with the best slides wins --- not the vendor with the best delivery capability. A scoring framework solves three problems:
- Comparability. Every candidate is measured on the same dimensions, so differences become visible.
- Traceability. When the CFO asks “Why them?”, you have a documented rationale.
- Risk detection. Weak areas surface early, before contracts are signed.
Organizations that skip formal evaluation are disproportionately represented in ERP failure statistics. According to multiple industry studies, over 50% of ERP projects exceed their original budget, and poor integrator fit is a leading root cause.
The 100-Point Scoring Framework
Each criterion is worth 10 points. Score each integrator from 0 to 10 per criterion. The total gives you a comparable score out of 100.
Scoring Scale
| Score | Meaning |
|---|---|
| 0—2 | Absent, vague, or clearly insufficient |
| 3—4 | Partially addressed, generic response |
| 5—6 | Adequate, standard market practice |
| 7—8 | Strong, adapted to your specific context |
| 9—10 | Excellent, backed by concrete evidence and proof |
The 10 Criteria
| # | Criterion | Max Points | What to Evaluate |
|---|---|---|---|
| 1 | Industry Expertise | 10 | Depth of knowledge in your vertical (manufacturing, retail, services, etc.). Do they understand your regulatory environment, seasonal cycles, and operational constraints? |
| 2 | Vendor Certification Level | 10 | Official partnership tier with the ERP vendor (SAP, Oracle, Microsoft, Odoo, etc.). Number of certified consultants. Access to vendor escalation channels. |
| 3 | Team Composition & Availability | 10 | Named resources, seniority mix, allocation percentages, backup plan. Will the people who present be the people who deliver? |
| 4 | Reference Clients (Similar Size/Industry) | 10 | Verifiable references in your sector and company size bracket. Willingness to arrange reference calls. Demonstrated outcomes, not just logos. |
| 5 | Implementation Methodology | 10 | Clarity of phases, milestones, deliverables, governance (RACI, steering committee cadence). Iterative delivery vs. tunnel effect. |
| 6 | Data Migration Capabilities | 10 | Structured migration plan: mapping, cleansing, transformation rules, rehearsals before cutover. Experience with your source systems. |
| 7 | Change Management Approach | 10 | Training plan by user profile, key-user network, adoption KPIs, communication plan. Not just a “one-day demo” at the end. |
| 8 | Post-Go-Live Support Model | 10 | Hypercare period, SLA definitions, escalation paths, transition to long-term support. Pricing model for ongoing maintenance. |
| 9 | Pricing Transparency | 10 | Detailed cost breakdown (not a single lump sum). Clear assumptions and exclusions. Change request process. Total Cost of Ownership (TCO) view including licenses, infra, and run costs. |
| 10 | Cultural Fit & Communication | 10 | Responsiveness during the selection process, quality of written deliverables, willingness to challenge your assumptions constructively, language and timezone compatibility. |
How to Use the Grid
- Create a spreadsheet with the 10 criteria as rows and your shortlisted integrators as columns.
- Assign a scoring panel of 3—5 internal stakeholders (IT, Finance, Operations, and at least one future end-user representative).
- Score independently first, then consolidate. This prevents groupthink and surfaces perception gaps.
- Require evidence for any score above 6. If the integrator claims something, ask for the deliverable, the reference, or the contractual commitment that proves it.
- Weight the criteria if needed. The default is equal weight (10 points each). If data migration is your biggest risk, consider weighting criterion 6 at 15 and reducing another accordingly. Just keep the total at 100.
A sample consolidated scorecard might look like this:
| Criterion | Integrator A | Integrator B | Integrator C |
|---|---|---|---|
| 1. Industry Expertise | 8 | 6 | 9 |
| 2. Vendor Certification | 7 | 9 | 7 |
| 3. Team Composition | 6 | 7 | 8 |
| 4. Reference Clients | 7 | 5 | 9 |
| 5. Methodology | 8 | 8 | 7 |
| 6. Data Migration | 5 | 7 | 8 |
| 7. Change Management | 6 | 6 | 8 |
| 8. Post-Go-Live Support | 7 | 8 | 7 |
| 9. Pricing Transparency | 8 | 5 | 7 |
| 10. Cultural Fit | 7 | 6 | 8 |
| Total | 69 | 67 | 78 |
The score does not decide for you --- it informs your decision. An integrator scoring 78 with a weak data migration score (5) still carries a significant risk if data is your top concern.
Running the RFP Process
A well-run Request for Proposal (RFP) is the backbone of integrator selection. Here is a practical sequence:
Step 1: Define the RFP Scope Document
Before contacting anyone, write a concise scope document (10—15 pages maximum) that includes:
- Company context: industry, size, locations, current systems landscape
- Project objectives: measurable business outcomes (not “implement SAP”)
- Functional perimeter: modules, processes, and explicit exclusions
- Technical constraints: existing infrastructure, integration points, security requirements
- Timeline expectations: desired go-live date and any hard deadlines
- Evaluation criteria: share the 10 criteria openly --- transparency attracts serious vendors
Step 2: Issue to a Short List (3—5 Integrators)
Sending an RFP to 10 vendors wastes everyone’s time. Pre-qualify through market research, peer recommendations, and vendor partner directories. Three to five candidates is the sweet spot.
Step 3: Structured Vendor Presentations
Give each integrator the same briefing and the same time slot. Require them to present:
- Their understanding of your business (not a generic company deck)
- The proposed team with names, roles, and CVs
- A draft project plan with phases and milestones
- At least two comparable reference clients
- A detailed pricing breakdown
Step 4: Reference Calls
Insist on speaking directly with reference clients --- not curated testimonials. Ask the reference:
- “What went wrong, and how did the integrator handle it?”
- “Would you hire them again for a similar project?”
- “How was the transition from project to support?”
Step 5: Score, Deliberate, Select
Apply the 100-point framework. Present scores to the steering committee with a recommendation. Allow one final clarification round with the top candidate before contract negotiation.
Red Flags During Vendor Presentations
Even the best scoring framework cannot protect you if you ignore warning signs during the selection process. Watch for these:
The bait-and-switch team. Impressive seniors present during the pitch, but the proposal lists junior or unnamed resources for delivery. Always ask: “Will the people in this room be on the project? At what allocation?”
Reluctance to share references. If an integrator cannot produce two or three verifiable references in your industry, treat it as a serious gap, regardless of their broader portfolio.
Vague pricing with “we’ll refine later.” A proposal that bundles everything into a single number without assumptions, exclusions, or a change-request mechanism is a ticking budget bomb.
Overpromising on timeline. If one vendor promises delivery in half the time of the others with no clear explanation, they are either underestimating scope or planning to cut corners on testing and change management.
No questions asked. A good integrator challenges your assumptions. If they agree with everything and ask nothing, they are not listening --- they are selling.
Ignoring data migration. If the words “data” barely appear in a 50-page proposal, that integrator has not done enough similar projects. Data migration is the number-one risk factor in ERP implementations. For more on this and other failure patterns, see our article on red flags that signal an ERP project is about to derail.
Negotiation Tips
Once you have selected your preferred integrator, negotiation begins. Here are practical guidelines:
Protect Yourself on Scope
- Require a written list of assumptions and exclusions as an annex to the contract. This is your single most important defense against scope creep.
- Define a change request process upfront: how changes are requested, estimated, approved, and billed.
Secure the Team
- Name the key resources in the contract (project manager, solution architect, lead functional consultant).
- Include a replacement clause: if a named resource leaves, the integrator must propose a replacement of equivalent seniority within an agreed timeframe (typically 2—4 weeks).
Structure the Payment
- Milestone-based payments aligned with deliverables, not calendar dates. You pay when you receive and accept something, not when a month ends.
- Retain 10—15% until a defined hypercare period is completed successfully.
Define the Exit
- Ensure data portability and IP ownership are explicitly covered. You should own all configurations, documentation, and custom developments produced during the project.
- Include a disengagement clause with reasonable notice periods and transition support obligations.
Negotiate Support Separately
- Post-go-live support (SLAs, response times, pricing) should be a separate agreement or annex, not buried in the project contract. This gives you leverage to renegotiate or switch providers after stabilization.
Building Your Selection Timeline
A realistic integrator selection process takes 6 to 10 weeks from RFP issuance to signed contract. Here is a typical breakdown:
| Week | Activity |
|---|---|
| 1—2 | Finalize RFP document and short list |
| 3 | Issue RFP, allow 2—3 weeks for responses |
| 4—5 | Receive and review proposals |
| 6 | Vendor presentations and scoring |
| 7 | Reference calls and score consolidation |
| 8 | Steering committee decision |
| 9—10 | Contract negotiation and signature |
Rushing this process is a false economy. Two extra weeks in selection can save months of project overruns.
Conclusion: Choose on Evidence, Not on Pitch Decks
The integrator you choose will be embedded in your organization for 6 to 18 months. They will shape your processes, touch your data, and influence how your teams experience the new system. This decision deserves more than a gut feeling.
Use the 100-point framework. Run a disciplined RFP. Check references. Watch for red flags. Negotiate with your eyes open.
The organizations that succeed with ERP are not the ones that picked the cheapest vendor or the biggest brand. They are the ones that picked the partner whose evidence matched their needs.
Ready to plan the full project? Return to the complete ERP implementation guide for the end-to-end roadmap, from business case through post-go-live optimization.
