- Company sizes or stages where this product is overkill or insufficient
- Early-stage teams that only need a lightweight pipeline tracker may prefer lower-cost, simpler CRMs to reduce adoption friction.
- Very large enterprises requiring global governance, complex multi-organization data architecture, and extensive ecosystem integrations may be better served by platforms such as Salesforce or Dynamics 365.
- Industries or use cases where competitors are more suitable
- Content-heavy inbound marketing organizations may prefer platforms with broader native marketing tooling (for example, HubSpot).
- Highly regulated healthcare or payment environments likely require documented HIPAA/PCI controls and may need vendors with clear compliance attestations.
- Technical requirements that this product cannot meet (based on accessible documentation)
- If formal SOC 2 reports, public penetration-test summaries, or specific ISO cloud extensions are mandatory, the vendor’s publicly available documentation may be insufficient.
- Budget constraints that make alternatives more appropriate
- Organizations needing only basic deal tracking may find entry-level CRMs with lower per-seat pricing more appropriate.
- Specific workflows or integrations where limitations have been reported
- Organizations that require advanced reporting and visualization should validate capabilities during evaluation due to user comments indicating limitations in built-in charts and graphs.
- Procurement red flags
- Unclear tiering for SSO/security features and integration services can create scope ambiguity; procurement should obtain written scoping of included features and service levels.
- Current limitations acknowledged by the vendor
- The vendor does not publish a formal limitations page in the accessible sources.
- Features on the roadmap
- The help center contains release notes (for example, a May 2026 release entry), but detailed roadmap commitments and timelines were not extracted in this research.
- Scale limitations
- Performance and scale characteristics are not publicly documented; procurement should test the platform with representative data volumes and concurrency patterns.
- Security or compliance gaps
- SOC 2 and several ISO extensions (27017/27018) are not documented in the publicly accessible sources.
- Public documentation does not clearly specify SCIM, detailed audit logging, encryption key management options, or formal data residency guarantees.
- API limitations or integration constraints
- An API is documented in the help center, but public details such as rate limits, endpoint coverage, and authentication models were not available in the captured excerpts and should be validated in technical evaluation.