ETFBOOK

If an organization requires a single vendor to cover multi-asset real-time data, news, messaging, analytics, and compliance workflows, incumbent platforms such as Bloomberg, LSEG Workspace, or FactSet may be more appropriate.

If procurement requires publicly documented SOC 2 Type II / ISO 27001 certificates and published security whitepapers, ETFBOOK’s public footprint appears insufficient; contractual documentation should be requested.

If the use case only requires basic ETF holdings or characteristics for a limited set of funds, sourcing data directly from issuers and exchanges or using lower-cost APIs may be more cost-effective than an enterprise contract.

If the organization is highly averse to platform transitions, the vendor’s decommissioning of a legacy platform indicates the need to confirm roadmap, migration support, and backward compatibility.

If legal/compliance teams are concerned by the Terms & Conditions language restricting access by U.S. persons, clarify whether that language applies to the commercial data service or only to public website content before proceeding.

Public evidence gaps

• Limited accessible third-party customer reviews (G2/TrustRadius/Gartner) specifically for ETFBOOK.

Security/compliance transparency

• No public SOC 2 / ISO documentation was found in accessible sources; enterprises should request security documentation under appropriate confidentiality terms.

Product transition risk

• Public pages indicate a legacy platform decommissioning, which may introduce training, change management, and feature-parity questions during migration.

Legal disclaimers versus vendor claims

• The Terms & Conditions disclaim warranties on correctness/reliability/completeness, which is typical in market-data agreements but materially relevant when vendor materials assert data verification. Buyers should insist on contractual error handling, correction SLAs, and data provenance documentation.

Consolidated ETF data model

• The vendor states that the product consolidates primary flows/AUM, secondary market liquidity metrics, holdings transparency, and reference data into a consistent model and delivery mechanism (platform + API).

Coverage and update cadence (vendor claim)

• The vendor claims Europe and US ETF coverage with a daily T+1 update cadence. This claim should be validated in a proof-of-concept and contractually defined if required for operational workflows.

Delivery model

• The vendor describes modular configurations, bespoke options, and REST API delivery licensed by region and module.

Comparative considerations

• Incumbent vendors may provide broader enterprise controls, entitlement systems, and more extensive third-party validation that some buyers may prefer for large-scale deployments.

• A public-company announcement about a partner engagement with ETFBOOK as an ETN calculation agent.
• A prospectus document listing “SquaredData GmbH (ETFBook)” as an ETP calculation agent.
• An ETF issuer methodology PDF states ETFBOOK is the data provider.

Company sizes (indicative)

• Mid-market to enterprise financial institutions
  • ETF issuers with multiple listings/share classes across European venues
  • Broker-dealers and liquidity providers needing venue/spread/volume analytics
  • Asset managers/wealth managers with dedicated ETF research functions

Industries / verticals

• Asset management
• Capital markets / broker-dealers
• ETF service ecosystem (fund administrators, index-related operations, data operations)

Roles and personas

• Decision makers
  • Head of ETF Capital Markets / ETF Product
  • Head of Data / Market Data Procurement
  • Head of Trading / Execution
• End users
  • ETF product specialists, ETF strategists
  • Trading analytics teams
  • Data engineering teams integrating ETF datasets into internal platforms

Pain points addressed

• Consolidating fragmented ETF data sources (holdings, flows, trading/liquidity)
• Standardizing identifiers, classifications, and product hierarchies across listings/share classes
• Enabling ETF competitive analysis (peer benchmarking, segmentation)

Qualification criteria (fit)

• Need for Europe + US ETF coverage with daily refresh and a consistent schema
• Internal teams capable of operationalizing API/data feeds (data engineering capacity)
• Workflows requiring both primary and secondary market ETF intelligence

Deal disqualifiers (poor fit)

• Organizations that require publicly documented security certifications prior to procurement, unless the vendor provides documentation under NDA
• Buyers that only need basic ETF facts for a small universe and can source them from issuers/exchanges at lower cost
• Teams requiring deep real-time execution data at tick-level as their primary requirement (ETFBOOK’s coverage appears to be oriented toward daily/T+1 datasets for many components)