- Company sizes or stages where this product is overkill or insufficient
- Very early startups with low ticket volume may not justify the operational overhead and variable usage costs.
- Very large enterprises with strict vendor governance may find public security documentation insufficient without further diligence.
- Industries or use cases where competitors are clearly superior
- Highly regulated financial services deployments requiring long-proven cobrowsing vendors with mature compliance programs (Glance/Surfly).
- Product analytics-first organizations where FullStory/Hotjar better align to analytics needs.
- Technical requirements that this product cannot meet (or are unclear)
- On-prem or hybrid hosting requirements (not documented publicly).
- SCIM provisioning requirements (not clearly documented).
- Budget constraints
- Buyers that require transparent, predictable pricing without usage-based variability may prefer vendors with visible public pricing or fixed-seat models.
- Specific workflows or integrations where the product falls short
- If support workflows rely heavily on tools not listed in vendor highlights, validate integration depth during procurement.
- Red flags in the buying process
- Heavy reliance on custom quotes without clear guardrails on usage, overages, retention, and add-on pricing.
- Broad statements about compliance (e.g., "SOC 2") without an available attestation or clear scope.
- Current limitations acknowledged by the vendor
- Public pages focus on capabilities and do not provide a comprehensive limitations list.
- Features on the roadmap (not yet available)
- Public roadmaps were not identified in this research.
- Reviewer feedback suggests some competitors are perceived as stronger in roadmap communication or velocity.
- Scale limitations
- Not publicly documented. Buyers should ask about replay retention limits, storage costs, and performance at high session volumes.
- Security or compliance gaps
- Lack of publicly documented SOC 2 attestation type/scope and lack of public ISO certification evidence may be blockers for some enterprises.
- Technical debt / architectural limitations mentioned in reviews
- Not evidenced in the accessible sources reviewed.
- API limitations or integration constraints
- G2 lists API availability in paid tiers; public documentation on API capabilities and limits is limited.