Topic
Data products
Building products, features and models on licensed company data.
- What a data licence covers: internal use, embedding, redistributionA data licence grants a use, not a dataset. This guide places common plans under internal use, embedding or redistribution and lists what to settle for each before you sign.
- Adding technographic filters to a prospecting toolA technology filter is a set of definitions before it is a dropdown. What "runs it now", "first seen" and "recently added" should mean, and the datasets and indexes that serve them.
- Building a company knowledge graph from identifiers and eventsA company graph answers questions that span datasets. This guide gives the node and edge tables, the join that finds a brand's listed parent and the way to link your own records.
- Building company change alerts into your productAn alert is a dated event shown to someone who follows a company. This guide covers the tables to read, the schema to store, how to dedupe and what each message may say.
- Company data as context for AI agents and copilotsDesign the tools, the result format and the tests for an agent that answers questions about companies from dated, sourced rows instead of scraped pages.
- Enriching company records in your data productEnrichment starts with a match and ends with a licence. Here is how to match records on domain, which fields to add, how to refresh them and what to settle for embedding.
- Powering account scores in a sales platform with licensed signalsFor product teams that put a score beside each account: what a weekly row carries, the three states a score can be in, how to survive a version change and what to settle in the licence.
- Producing market research from weekly aggregate seriesA weekly series is only as good as its footnote. Here is how research and media teams pull the Fokals Market Series, test a number before it is printed and cite it.
- Redistributing company data to your customers under licenceA working list for platforms and product teams that deliver licensed company data onward: what the data carries, what you can promise customers and which questions to put in writing.
- Listing a data product on Datarade: what providers should knowA provider's reading of Datarade's own pages: the application, the listing fields, the rules on personal and web data, the lead flow and the plans, checked on 4 October 2026.
- Serving company data to AI agents over Model Context ProtocolA team wraps the Fokals REST API as MCP tools in a thin server of its own. This guide covers tool design, paging, keys, rate limits and untrusted text against the current specification.
- Serving company signals from ClickHouseDesign ClickHouse tables for company change events, signals and weekly scores: which engine, which ordering key, and how a second access path is added when a second query needs one.
- What it takes to list a data product on Snowflake MarketplaceA provider-side guide for data teams deciding whether to list on Snowflake Marketplace: prerequisites, listing fields, review, regional delivery, duties after publication and the licence questions to settle first.
- Coresignal alternatives for company and jobs dataCoresignal is built around company, employee and jobs records from the public web. What each product is built for, the sources that fit each part of a workload, and the company and jobs parts mapped dataset by dataset.
- People Data Labs alternatives for company dataPeople Data Labs documents a person dataset beside its company dataset. Fokals is company-level data throughout. A fair map of the two as documented, a move dataset by dataset, and the sources that fit each need.
- Veridion alternatives for web-sourced company dataVeridion and Fokals both collect company data from public web sources, for different sets of companies and in different shapes. A fair map of each, the neighbouring sources, and a test to run on your own records.
- Wappalyzer alternatives for technology detection dataWappalyzer identifies website technologies on demand, with lead lists and alerts. If you need detection as a dated dataset to build on, here is how the alternatives compare.
- Data enrichmentData enrichment adds fields from an external source to records you already hold. This entry shows the steps, a table of fields with refresh rates and common mistakes.
- Data licenceThe contract that gives a buyer the right to use a dataset, and sets its limits. Internal use, embedding and redistribution, the terms to settle and how terms travel.
- Label versionA label version names the frozen rules and model behind a dataset's labels. Why it matters for comparing periods and for products built on labels, and the versions used in Fokals data.
- Redistribution licenceA redistribution licence lets a buyer pass licensed data on to its own customers. This entry sets it beside internal use and embedding and lists the terms to settle first.