- If procurement requires a publicly documented Simplus-specific trust center with detailed certifications and audit artifacts
- The reviewed public sources did not show a consolidated Simplus-specific security posture page; buyers with strict pre-contract compliance requirements should expect to request documentation and may face procurement delays.
- If the program cannot tolerate staffing variability on complex work
- Public community anecdotes indicate some projects have reported staffing-related delivery issues; organizations with low tolerance for staffing variability should consider alternative partners or require stronger contractual staffing commitments.
- If you are a small organization with limited budget and need a lightweight Salesforce setup
- Larger specialist systems integrators can be resource- and cost-intensive for smaller, lower-complexity implementations; smaller firms or internal resources may provide better ROI in those cases.
- If you require a very large global SI with extensive cross-platform delivery and large offshore scale
- Global SIs such as Accenture or Deloitte may be more aligned for massive, multi-system transformations; buyers should weigh cost, governance overhead, and vendor fit.
- Current limitations acknowledged by the vendor
- Professional services firms typically do not publish a software-style "known issues" page; limitations are generally related to delivery model, staffing, and scope management.
- Features on the roadmap (not yet available)
- Not applicable in the same way as a software product; roadmap references would typically cover internal accelerators and delivery assets rather than customer-facing product features.
- Scale limitations (at what volume/size does it break down?)
- Simplus operating under Infosys can support enterprise-scale programs, but outcomes depend on project governance, staffing model, and resource allocation.
- Security or compliance gaps
- No central Simplus-specific public documentation of security certifications was identified in the reviewed sources; buyers should request confirmation of applicable certifications and compliance evidence.
- Technical debt or architectural limitations mentioned in reviews
- Public community feedback highlights potential delivery risk areas such as inexperienced staffing; buyers should include staffing-level requirements and acceptance criteria in statements of work.
- API limitations or integration constraints
- Integration constraints are generally a function of Salesforce platform choices and client integration landscapes rather than vendor-specific platform limitations.