- If audited enterprise security documentation is required
- If procurement requires SOC 2 Type II or ISO 27001 evidence, Referly may not meet requirements unless the vendor provides documentation under NDA.
- If a purely self-serve, very low-cost tool is required
- At the published starter price (~€500/month), very small teams or solo founders may find specialist visitor-identification tools or DIY workflows more cost-effective.
- If organizational policy prohibits connecting Google Workspace/CRM data
- If security policy prohibits connecting Gmail/Calendar data or using browser extensions, a significant portion of Referly’s signal set may be unusable.
- If the primary need is specialist visitor identification only
- Specialist vendors focused solely on visitor identification may provide higher match rates, deeper enrichment, or more robust reporting for that single use case.
- If a mature ABM/intent stack is already in place
- Organizations with established ABM vendors and RevOps automation may find Referly redundant unless it provides unique, measurable incremental signal value.
- Publicly visible limitations and uncertainties
- Security certifications are not publicly documented.
- Salesforce integration is described as forthcoming on the main page; the timeline and scope are unclear.
- The privacy policy references historical EU–US transfer standards; buyers should request current Data Processing Agreement (DPA) language and confirmation of the legal basis for international transfers.
- Scale limitations
- Not clearly documented; the Corporate plan implies support for higher CRM contact volumes, but explicit performance or throughput specifications were not published.
- API limitations or integration constraints
- Webhook integration is listed, but no comprehensive public developer documentation was found in the sources reviewed. Buyers should request API documentation and SLA details.