- Scenarios where alternatives are better
- If you require extensive, independently reviewed enterprise security assurances (SOC 2 Type II, ISO 27001) and procurement policy mandates public attestations, consider vendors with published audit reports.
- If you already operate a mature LMS and only need compliance content and tracking, an in-house LMS with SCORM packages or a specialist training vendor may be simpler than adopting a broader risk suite.
- If your strategic requirement prioritizes professional learning and PD credit tracking as the primary hub, consider vendors that explicitly position PD and compliance in a single system.
- If you have concerns about post-acquisition support transitions, request SLAs, escalation paths, and references from districts that have experienced the vendor post-acquisition.
- Current limitations acknowledged by the vendor
- Vendor marketing pages emphasize benefits; explicit limitations are not prominently stated in public marketing materials.
- Features on the roadmap (not yet available)
- A public product roadmap was not identified in accessible sources.
- Scale limitations
- No public scale thresholds or performance benchmarks were found in the research.
- Security or compliance gaps
- Public security certifications (SOC 2/ISO) and a Data Processing Agreement were not found in the accessible sources; procurement teams should request these artifacts.
- Technical debt or architectural limitations mentioned in reviews
- No PSW-specific technical limitation narratives were found in mainstream review platforms; ecosystem-level posts reference operational complaints about Raptor but are not PSW-specific.
- API limitations or integration constraints
- Integration capabilities are not clearly documented publicly; procurement teams should request the vendor to specify supported SIS/HR systems, roster sync methods (CSV, SFTP, API), SSO methods (SAML/OIDC), and any SCIM support.