- When enterprise PSA depth is required
- Consider end-to-end PSA platforms when project accounting, invoicing, and full financial governance are required rather than a resourcing-focused platform.
- When reporting/BI is a primary buying criterion
- Aggregated review summaries indicate limited reporting depth; organizations needing advanced dashboards without exporting to BI tooling should evaluate alternatives with stronger built-in analytics.
- When heavy UI scale stress is anticipated
- Reviewer signals highlight sluggish performance and scrolling friction with large teams and datasets; validate with a proof-of-concept using real organizational data.
- When scheduling hygiene cannot be maintained
- Any resourcing tool requires accurate, maintained allocations; if organizational processes will not support regular updates, a different or lighter-weight workflow may be more appropriate.
- When detailed published security artifacts are required by procurement
- While SOC 2 Type II is referenced in vendor materials, enterprises requiring a public trust center, detailed subprocessor lists, specific ISO certifications, or explicit data residency guarantees should confirm availability before procurement.
- Issues reported by reviewers / editorial synthesis
- UI friction and usability quirks: scrolling friction and occasional UI mismatches or hiccups.
- Performance with scale: slow load/refresh and lag reported by users working with large schedules.
- Limitations implied by packaging/positioning
- Reporting depth limitations as described in aggregated review summaries.
- Enterprise security feature completeness (SCIM, audit logs, and detailed RBAC) is not fully documented in public materials; buyers should confirm via the vendor's trust artifacts.
- Roadmap / "not yet available"
- No specific roadmap items with dated commitments were captured in the reviewed materials; request current roadmap details during vendor evaluation.