- Company sizes or stages where the product is overkill or insufficient
- Very small teams with occasional patent searches may be better served by free tools (Google Patents, Espacenet) or by commissioning ad-hoc expert searches.
- Industries or use cases where competitors are clearly superior
- Global enterprises that prioritize an entrenched, globally supported patent intelligence stack may prefer incumbents such as Clarivate Derwent or Questel Orbit for procurement familiarity and perceived lower vendor risk.
- Organizations requiring broad multi-source innovation intelligence (patents, literature, deals, news, clinical data) may find larger suites (e.g., PatSnap) more aligned.
- Technical requirements that the product may not meet
- If SCIM provisioning, dedicated regional data residency, or documented penetration test summaries are required and the vendor cannot provide them, this constitutes a significant concern.
- Budget constraints that make alternatives more appropriate
- Organizations with fixed or limited budgets may prefer open or lower-cost alternatives (e.g., Lens.org) or narrower tools focused solely on search rather than full analytics suites.
- Specific workflows or integrations where the product falls short
- If the core need is enforcement, claim-chart automation, or litigation-centric workflows, specialist tools may be better suited than a patent search and landscape platform.
- Red flags in the buying process
- Lack of transparent pricing, absence of trial access, or inability to provide reference customers should prompt caution; evaluators should insist on a pilot and contractual protections.
- Current limitations acknowledged by the vendor
- The help content acknowledges that AI outputs may be inaccurate or incomplete.
- The AI drawing generation feature is described as experimental and may not meet quality expectations.
- Features on the roadmap (not yet available) - note estimated dates if available
- Release notes show active iteration (SSO improvements, audit logs by request, IP allowlisting, reporting/trend features). Exact roadmap dates beyond posted releases are not clearly provided.
- Scale limitations (at what volume/size does it break down?)
- No public scale benchmarks were found. Some features note practical limits (for example, importing up to 10,000 patents in a single operation into certain project workflows).
- Security or compliance gaps
- SOC 2 Type II and some other compliance attestations are not publicly documented.
- Data residency and hosting regions are not clearly documented in public materials.
- Technical debt or architectural limitations mentioned in reviews
- No third-party reviews were found that document architectural limitations.
- API limitations or integration constraints
- API documentation and integration details are not prominently documented publicly; evaluators should request API specifications and integration guides.