- High-stakes, externally audited use cases
- When market numbers must withstand audit or regulatory scrutiny (for example, regulated disclosures or litigation contexts), the presence of external criticism and possible methodology opacity may be unacceptable.
- Teams requiring maximum methodological transparency
- Organizations that require raw data lineage, detailed sampling documentation, error bounds, and full reproducibility may find packaged report metrics insufficient without extensive vendor cooperation and contractual guarantees.
- Security-driven enterprise procurement
- Procurement requiring publicly documented SOC 2 Type II / ISO 27001 certifications and explicit documentation of SSO/SCIM/audit-log features should request vendor attestations; the publicly accessible materials reviewed did not provide such documentation.
- When a dedicated product analytics platform is required
- For teams whose primary need is in-product analytics (funnels, cohorts, event tracking), iResearch’s offering is not positioned as an in-app analytics SDK. Dedicated product analytics vendors are more appropriate for that use case.
- Public disputes about data accuracy / integrity
- External commentary has referenced questionable practices within some third-party research in China and has named iResearch in some discussions; this represents a reputational and verification risk that should be assessed in due diligence.
- Transparency gaps
- Pricing tiers are not publicly documented in accessible pages; prospective customers must engage sales for quotes.
- Enterprise security features and formal certifications are not publicly documented in the accessible pages reviewed.
- Availability and access friction
- Some report portals require account access or licensing; content IP restrictions can limit downstream reuse and distribution.