- Company sizes or stages where this product is overkill or insufficient
- Very small organizations (<100 employees) may find governance and implementation overhead disproportionate to need.
- Industries or use cases where competitors are clearly superior
- Enterprises that require deep, native ITSM suite capabilities and centralized platform procurement may prefer to standardize on an incumbent ITSM provider.
- Technical requirements that this product may not meet
- If an organization requires documented data residency controls, explicit compliance attestations, or detailed export guarantees that the vendor cannot provide in writing, another vendor may be more appropriate.
- Budget constraints that make alternatives more appropriate
- If the procurement budget cannot support multi-month implementations and ongoing optimization, consider lighter-weight ticketing systems with basic chatbot or KB capabilities.
- Specific workflows or integrations where the product could fall short
- If critical integrations (identity provider, HRIS, ERP/AP) are not proven and would require custom development, the project may require substantial professional services.
- Red flags in the buying process
- Lack of public security documentation or inability/unwillingness to provide security evidence under NDA
- Vague pricing tied to undefined outcome metrics or unclear automation/action limits
- Inability to demonstrate audit logs, approval paths, and rollback mechanisms in a sandbox or pilot
- Current limitations acknowledged by the vendor
- Public materials emphasize governance and auditability; explicit public lists of limitations are not prominent and should be requested during diligence.
- Features on the roadmap (not yet available)
- Roadmap details were not publicly documented in the reviewed sources; buyers should request a roadmap under NDA.
- Scale limitations (at what volume/size does it break down?)
- Vendor materials reference large deployments; independent corroboration of scale claims is limited in public sources.
- Security or compliance gaps
- Security certifications such as SOC 2 and ISO 27001 were not publicly documented in the reviewed sources and could be procurement blockers.
- Technical debt or architectural limitations mentioned in reviews
- Reviewer summaries indicate that some features are still maturing and that users have reported occasional glitches, consistent with a product in active development.
- API limitations or integration constraints
- Public integration details are sparse; buyers should validate the set of native integrations, supported action types, and the distinction between native and partner-built integrations.