1. When an organization requires a full CEM suite more than an intelligence layer. If the priority is mass notification, two-way employee check-ins, templated workflows, and end-to-end resilience governance, vendors that provide those modules natively may be a better fit.
2. When mobile capability must match desktop feature parity. Reviewer feedback indicates the mobile application may not provide all desktop features.
3. When procurement requires publicly documented, explicit compliance and enterprise control matrices. If ISO 27001, detailed data residency options, SCIM support, and audit log schemas must be visible in public materials, Factal’s public documentation may be insufficient; expect a need for NDA or direct vendor documentation.
4. When transparent list pricing is a strict requirement. Public list pricing was not found in the sources reviewed; some buyers prefer vendors with published tiers or marketplace listings.
- Mobile vs desktop feature parity: raised in a G2 review and should be validated with the vendor if mobile is critical.
- MFA availability: the security page referenced planned MFA; procurement should confirm current availability and configuration options.
- Limited public detail on some enterprise controls: SCIM, detailed audit logging, ISO certifications, and data residency options are not clearly presented in public materials reviewed; these should be requested during diligence.
- Brand confusion risk: multiple similar names (Factal, Factal.io, The Factual, factual) can create procurement and search friction; confirm the exact vendor entity and contract scope.