- When mature, independently validated customer evidence is required
- If procurement depends on an extensive body of third-party reviews, references, and established deployment histories, the limited public review footprint increases risk.
- When broad, proven planning modules are required immediately
- If an organization needs out-of-the-box, mature demand/supply planning modules, optimizer solvers, and vertical templates on day one, incumbent vendors with longer track records may be more suitable.
- When the organization cannot support change management
- If teams are not prepared to redesign governance and exception workflows, automation initiatives may be underutilized or unsuccessful.
- When strict data residency / compliance requirements must be publicly documented
- The vendor lists certifications but does not publicly document hosting regions, residency options, or detailed control descriptions in accessible pages.
- When transparent, predictable pricing is required
- The vendor does not publish pricing; organizations with constrained budgets and a need for transparent list pricing may find procurement forecasting difficult.
- Current limitations acknowledged by the vendor
- No explicit public "known issues" page or detailed public roadmap was identified in accessible vendor pages.
- Features on the roadmap (not yet available)
- The vendor did not publish a detailed roadmap in accessible materials; earlier reporting noted limited public detail on product roadmaps during initial launch.
- Scale limitations (at what volume/size does it break down?)
- Not publicly documented.
- Security or compliance gaps
- While the vendor claims SOC 2 Type II and ISO 27001, details such as data residency, SCIM support, audit log capabilities, and third-party penetration test disclosures are not publicly documented.
- API limitations or integration constraints
- Not publicly documented in accessible materials.