- When independent review validation is required
- If procurement requires a substantial base of independent reviews on Gartner Peer Insights, G2, or TrustRadius, SelectaPension may be difficult to validate based on the limited discoverability/coverage observed in accessible sources.
- When you need transparent pricing and a self-serve evaluation
- If the procurement requirement is published pricing tiers and immediate sandbox access, vendors with clearer published pricing or trial access may be easier to evaluate.
- When security/compliance must be evidenced publicly
- If public evidence of SOC 2/ISO certification, data residency, and enterprise controls is required prior to procurement, the vendors public security documentation appears limited and this should be treated as a procurement risk.
- When the primary need is holistic goals-based financial planning
- If the core requirement is deep goals-based client planning, household balance-sheet planning, and rich client portal collaboration, a dedicated planning tool (for example Voyant in the UK planning category) may better meet that primary need, with pension switching handled by a specialist add-on.
- When the workflow is already standardized around another research ecosystem
- If the firm is standardized on Defaqto Engage (or a similar research ecosystem) for research and compliance processes, changing switching/reporting engines could add operational friction unless migration and template mapping support are available and validated.
- Current limitations acknowledged by the vendor
- The vendor pages reviewed do not include an explicit limitations section.
- Roadmap / "not yet available"
- The vendor has published information about a new Portfolio Insight capability, but a detailed public roadmap with dates was not provided.
- Scale limitations
- Scale or performance limits were not documented in the publicly accessible materials reviewed.
- Security or compliance gaps
- Public documentation did not clearly specify SOC 2/ISO certifications, data residency, or enterprise security features; this represents a vendor information gap to address during due diligence.
- API limitations or integration constraints
- Integration descriptions are high level; technical API documentation, data models, rate limits, and error-handling approaches were not located in the public materials.