A system integrator (SI) selection framework is a structured decision model that determines whether an organization should engage an external system integrator for technology implementation — and if so, which tier of SI is the right fit. [src1] The framework routes decisions across three dimensions: project complexity (scale, multi-geography, regulatory requirements), internal capability (domain expertise, engineering capacity, change management maturity), and risk tolerance (timeline criticality, budget flexibility, acceptable failure probability). SI engagements range from Tier 1 global firms (Accenture, Deloitte, IBM, Capgemini) through mid-market/Tier 2 specialists to boutique integrators with narrow technology or industry focus. [src4]
START — User needs to decide SI engagement model
├── Does the user need SI selection help, or a different decision?
│ ├── General build vs buy vs partner decision
│ │ └── → Build vs Buy vs Partner Decision Tree
│ ├── ERP vendor selection (not SI selection)
│ │ └── → ERP Vendor Evaluation Criteria
│ └── SI engagement model decision
│ └── Continue below ← YOU ARE HERE
├── Decision 1: External SI vs Internal Team
│ ├── Internal team has cross-domain expertise + timeline is flexible?
│ │ ├── YES + regulatory/IP requires total control → INTERNAL TEAM
│ │ └── YES but complexity exceeds bandwidth → HYBRID
│ ├── Timeline is urgent (<6 months) or scope spans 3+ systems?
│ │ └── → EXTERNAL SI
│ └── Internal team lacks domain expertise in target platform?
│ └── → EXTERNAL SI or HYBRID
├── Decision 2: SI Tier Selection (if external SI chosen)
│ ├── Multi-country rollout, 5+ geographies, regulatory complexity?
│ │ └── → TIER 1 (global delivery infrastructure required)
│ ├── Single platform requiring deep specialization?
│ │ └── → TIER 2 or BOUTIQUE (often deeper platform expertise)
│ ├── Budget-constrained mid-market company (<$1B revenue)?
│ │ └── → TIER 2 or BOUTIQUE (Tier 1 cost structure mismatched)
│ └── Novel/emerging technology with few experienced implementers?
│ └── → BOUTIQUE with proven delivery on that technology
└── Decision 3: Validate the Specific Team
├── Review resumes of proposed project leads (not sales team)
├── Check offshore-to-onshore ratio against project needs
└── Conduct cultural fit assessment with front-line stakeholdersOrganizations default to Tier 1 firms because leadership perceives safety in a recognizable brand, leading to overpaying for capacity the project does not need. [src5]
Evaluate whether the project genuinely requires Tier 1 capabilities. For single-platform, single-region implementations, a Tier 2 or boutique SI with deep platform expertise typically delivers better outcomes at lower cost. [src1]
RFP processes focus on SI firm credentials and case studies while ignoring the specific team proposed for the project. The actual outcome depends on the 10-30 people who will be on-site, not the firm's global headcount. [src4]
Insist on meeting the actual project manager, solution architect, and functional leads. Review their individual track records and include cultural fit interviews with front-line stakeholders. [src4]
A Tier 2 SI bidding 30% less may be proposing 30% less scope — less change management, fewer accelerators, smaller contingency. Comparing raw bid prices without normalizing scope leads to budget overruns. [src1]
Create a standardized scope baseline and require all bidders to price against it. Compare blended hourly rates, offshore ratios, and scope coverage independently. [src1]
Misconception: Tier 1 SIs are always safer because they have more resources.
Reality: Tier 1 firms staff from a global resource pool. Your project may receive a team with no experience in your industry or platform, assembled from available bench resources. Brand safety does not transfer to a specific project team. [src5]
Misconception: Building an internal team is always cheaper than hiring an SI.
Reality: In-house integration frequently hides costs including talent acquisition, training, tool licensing, compliance overhead, and opportunity cost. For complex, time-bounded implementations, an SI is often cheaper on a total cost basis. [src2]
Misconception: Boutique SIs cannot handle enterprise-scale projects.
Reality: Boutique firms with deep platform specialization often achieve better outcomes than Tier 1 generalists on focused implementations. Their constraint is geographic scale and multi-platform breadth, not complexity within their domain. [src4]
Misconception: Once you select an SI, the decision is final for the project duration.
Reality: Governance checkpoints should include explicit go/no-go evaluations. Transitioning at 90 days — while costly — is less expensive than completing a failing multi-year engagement. [src4]
| Concept | Key Difference | When to Use |
|---|---|---|
| SI Tier Selection Framework | Determines which tier of SI or internal team fits the project | When deciding who will implement a technology project |
| Build vs Buy vs Partner Decision Tree | Determines approach (build, buy COTS, or partner) | Before selecting an implementer — what approach to take |
| ERP Vendor Evaluation | Scores ERP software vendors on functional fit | When selecting which software, not who implements it |
| Staff Augmentation vs Managed Services | Determines engagement model, not partner tier | When SI is selected but contract model is not |
Fetch this when a user is deciding whether to engage a system integrator for a technology implementation, choosing between SI tiers (Tier 1 global vs mid-market vs boutique), or evaluating whether to build an internal implementation team. Relevant for CIOs, CTOs, VPs of IT, and procurement teams running SI RFP processes.