SI Selection Decision Framework
Definition
A System Integrator (SI) Selection Decision Framework is a structured evaluation methodology that scores candidate implementation partners across four weighted dimensions -- depth of resources, industry experience, implementation approach, and support methodology -- to match an SI's capabilities to a project's size, ERP vendor ecosystem, geographic requirements, and budget constraints. The framework replaces subjective selection with a defensible, auditable process that reduces the risk of implementation failure by ensuring fit across technical competency, cultural alignment, and commercial terms. [src1]
Key Properties
- Four-Pillar Scoring Model: Evaluates SIs on resources, industry experience, implementation methodology, and post-go-live support -- with implementation approach weighted heaviest (typically 30-40% of total score) [src1]
- Tier Classification: Tier 1 SIs (Deloitte, Accenture, IBM, Capgemini) carry blended rates of $175-250/hr; Tier 2 SIs (regional/niche firms) run $100-150/hr with 30% lower overall bids on comparable scope [src2]
- Minimum Viable Shortlist: Best practice is 3-5 finalists from an initial long list of 8-12, with at least one Tier 2 entrant for cost benchmarking [src3]
- Geographic Delivery Model: Ranges from 100% onshore (highest cost, lowest risk) to hybrid onshore/offshore (30-50% cost savings, higher coordination overhead) [src4]
- Weighted Scorecard Output: Produces a single composite score (typically 0-100 or 1-5 scale) per candidate, enabling apples-to-apples comparison across evaluation committee members [src1]
Constraints
- The ERP/platform decision must be finalized first; running SI selection in parallel with software selection creates circular dependencies where SI preferences bias the software choice [src5]
- Weighted scorecards require a minimum 5-person evaluation committee with cross-functional representation (IT, finance, operations, change management) to produce statistically meaningful scores [src3]
- Reference checks only surface successful projects; SIs never volunteer failed implementations, so independent research (Gartner Peer Insights, court filings for disputes) is essential [src3]
- Fixed-price bids appear lower-risk but shift scope management burden to the buyer; time-and-materials contracts are more transparent but require stronger internal PMO capability [src2]
- Sub-$2M projects rarely justify the overhead of a full RFP process; direct negotiation with 2-3 pre-qualified firms is more efficient below this threshold [src4]
Framework Selection Decision Tree
START -- User needs to select an ERP implementation partner (SI)
|
+-- Has the ERP/platform been selected?
| +-- NO --> Complete ERP vendor selection first
| | See: ERP Vendor Selection Framework
| +-- YES --> Continue
|
+-- What is the total project budget?
| +-- Under $2M --> Skip formal RFP; direct-negotiate with 2-3 pre-qualified SIs
| +-- $2M-$10M --> Standard RFP with 3-5 shortlisted candidates
| | +-- Include at least 1 Tier 2 SI for cost benchmarking
| +-- Over $10M --> Full RFP + implementation planning workshops with finalists
| +-- Mandatory: on-site demos, reference site visits, team interviews
|
+-- Is the project multi-geography?
| +-- NO (single country) --> Prioritize local/regional SI with onshore delivery
| +-- YES (multi-country) --> Require SI with proven multi-geo track record
| +-- Evaluate: local entity presence, language capabilities, regulatory knowledge
|
+-- What ERP vendor ecosystem?
| +-- SAP --> Filter for SAP-certified partners (Gold/Platinum)
| +-- Oracle --> Filter for Oracle Cloud implementation specialists
| +-- Microsoft D365 --> Filter for Microsoft Inner Circle / Gold partners
| +-- NetSuite --> Filter for NetSuite Alliance / SuiteCloud partners
| +-- Workday --> Filter for Workday certified deployment partners
|
+-- Apply 4-pillar weighted scorecard:
+-- Resources (20-25%): bench depth, turnover rate, named team commitment
+-- Industry Experience (20-25%): vertical-specific track record, similar-size projects
+-- Implementation Approach (30-40%): methodology, change management, testing rigor
+-- Support Model (15-20%): post-go-live structure, SLA terms, hypercare period
Application Checklist
Step 1: Define Selection Criteria and Weights
- Inputs needed: Project scope document, budget range, ERP vendor, geographic requirements, industry vertical, timeline constraints
- Output: Weighted scorecard template with 15-25 evaluation criteria mapped to the four pillars
- Constraint: Implementation approach must be weighted at least 30% of total score; organizations that underweight methodology have 2x higher implementation failure rates [src1]
Step 2: Build Long List and Issue RFP
- Inputs needed: Weighted criteria, ERP vendor partner directory, industry peer recommendations, Gartner/Forrester analyst shortlists
- Output: Long list of 8-12 candidates, narrowed to 3-5 finalists after initial screening
- Constraint: Include at least one Tier 2 SI in the finalist pool; single-tier evaluations produce a 20-30% cost premium from lack of competitive tension [src2]
Step 3: Conduct Structured Evaluation
- Inputs needed: RFP responses, finalist presentations, reference interviews (minimum 3 per SI), implementation planning workshops with top 2 candidates
- Output: Completed scorecards from all evaluation committee members, normalized composite scores
- Constraint: Any evaluator whose scores deviate more than 2 standard deviations from the mean must document their rationale; undocumented outlier scores are excluded [src3]
Step 4: Negotiate and Award
- Inputs needed: Composite scores, commercial proposals, contract redlines, staffing commitments (named resources)
- Output: Signed SOW with milestone-based payment schedule, named team commitment, performance guarantees
- Constraint: Never award based solely on price; the lowest-cost bid correlates with higher change-order volume, which erodes the initial savings within 6 months of go-live [src2]
Step 5: Validate Before Kickoff
- Inputs needed: Signed contract, named team resumes, project charter
- Output: Go/no-go decision based on team confirmation
- Constraint: If more than 30% of the proposed team is substituted between proposal and kickoff, re-evaluate; bait-and-switch staffing is the single most common SI risk [src1]
Anti-Patterns
Wrong: Selecting the SI before finalizing the ERP platform
Organizations that run SI and software selection in parallel end up choosing the ERP system their preferred SI knows best, rather than the one that fits their business. This creates vendor lock-in where the SI's expertise drives the technology decision. [src5]
Correct: Complete platform selection first, then evaluate SIs within that ecosystem
Finalize the ERP vendor based on functional fit, then evaluate SIs who are certified partners within that ecosystem. This ensures the technology decision is business-driven and the SI is evaluated purely on implementation capability. [src3]
Wrong: Using a single decision-maker without cross-functional input
When IT alone selects the SI, the evaluation overweights technical factors and underweights change management, training, and business process expertise. Projects selected this way have significantly higher user adoption failures. [src1]
Correct: Assemble a 5-7 person cross-functional evaluation committee
Cross-functional evaluation ensures the SI's methodology addresses technical delivery, organizational change, and business process transformation equally. Each function scores independently before committee discussion. [src1]
Wrong: Choosing the lowest-cost bid without analyzing the staffing model
Tier 2 SIs sometimes win on price by staffing projects with junior consultants, resulting in longer timelines and higher change-order volumes. A lower bid with mostly junior staff often costs more than a higher bid with experienced leads. [src2]
Correct: Evaluate blended rates alongside team seniority and named-resource commitments
Request a staffing pyramid showing the ratio of partners/directors, managers, senior consultants, and analysts. Require named resources for lead roles with contractual anti-substitution clauses. [src2]
Common Misconceptions
Misconception: The biggest SI is always the safest choice for large projects.
Reality: Tier 1 SIs staff large engagements with a thin layer of experienced leads and a large base of junior consultants. For projects under $10M, a Tier 2 SI with deep vertical expertise often delivers better outcomes at 30-40% lower cost. [src2]
Misconception: Fixed-price contracts eliminate budget risk for the buyer.
Reality: Fixed-price contracts incentivize SIs to minimize scope and maximize change orders. The average fixed-price ERP project incurs 15-25% in change orders, often exceeding time-and-materials projections. [src3]
Misconception: SI references provide reliable evidence of delivery capability.
Reality: SIs curate their reference lists to show only successful projects. Independent validation through Gartner Peer Insights, industry forums, and direct outreach to non-provided references is essential. [src3]
Misconception: Offshore delivery models always reduce project cost.
Reality: Offshore delivery reduces hourly rates by 40-60% but increases coordination overhead by 20-30% and extends timelines by 15-25%. Net savings typically land at 20-35% rather than the headline rate differential. [src4]
Comparison with Similar Concepts
| Concept | Key Difference | When to Use |
|---|---|---|
| SI Selection Decision Framework | Evaluates implementation partners after ERP is chosen | Selecting who will implement and configure your chosen ERP platform |
| ERP Vendor Selection Framework | Evaluates the software platform itself | Choosing between SAP, Oracle, D365, NetSuite before SI selection |
| Build vs Buy vs Partner Decision Tree | Strategic make-or-buy analysis for any capability | Deciding whether to build custom, buy COTS, or outsource entirely |
| Managed Services Evaluation | Evaluates ongoing operational partners | Selecting a post-implementation support and maintenance partner |
When This Matters
Fetch this when a user is planning an ERP implementation and needs to evaluate, score, and select a system integrator, or when comparing SI tiers, negotiating SI contracts, or building an RFP evaluation scorecard for implementation partners.