Topic
Sourcing and compliance
How data is sourced, and what a due diligence review asks of a vendor.
- How to document data lineage for a licensed external datasetWhat to record for every delivery of a licensed dataset: licence, batch, checksums, schema version and transformations, mapped to OpenLineage and the D&TA provenance standards, with a checklist.
- Pay ranges in job postings for remote vs on-site sales rolesPosted pay for remote and on-site sales roles compared with role, seniority and pay location held fixed, with 2026 medians, state pay transparency rules and study findings.
- Typical base to variable pay split for enterprise account executivesEnterprise account executive pay is read against a 50/50 split of OTE. This guide defines OTE, explains 60/40 and 70/30 plans, gives 2026 medians from job ads and works through an illustrative posting.
- Open source company data for commercial use: registries and licencesOpen company data comes under four kinds of terms: a public-information statement, a public-domain dedication, an attribution licence and a share-alike database licence. Here is what each publisher's text asks and what is left to build.
- Questions a data platform should ask before reselling a third-party datasetReselling a dataset puts your customers on rights you hold from someone else. Eight questions in the order a platform meets them, the evidence to ask for under each, and an API resale worked through with its dates.
- What happens to licensed data when a contract ends: the destruction clauseA destruction clause names what to remove, by when and with what proof. A published template, ten places licensed rows end up, platform recovery windows and a worked exit with its dates.
- Derived data in a data licensing agreement: definition and ownershipIndustry wording tests derived data twice: can the licensed data be rebuilt from an output, and can the output stand in for it. Here is that wording, database law by country, and an illustrative clause applied to five outputs.
- Can you use licensed company data to train a machine learning model?The licence decides whether licensed company data may train a model. A table of clauses for training, evaluation, retrieval by assistants and the end of term, with what regulators and licence stewards have published.
- Data provider attribution: the rules when data is shown in a productAn attribution duty reaches a product by one of three routes: an open licence, an API's terms or your licence agreement. Here is what each text asks of a screen that shows the data, a checklist to apply, and one screen worked through.
- Types of alternative data used by hedge funds, from card data to web dataCard transactions, satellite imagery, web and app usage, sentiment and company web data, side by side. What each observes, its grain, its compliance questions and a worked example of a small team's first purchases.
- Account-level vs contact-level intent data in B2B, and the GDPRAn account-level intent record describes a company and a contact-level one describes a person. A table of the two, questions for each vendor, what the EDPB, the ICO and the Commission say, and one account worked at both levels.
- Material non-public information risk in alternative data: what to askA statute, two rules, a staff Risk Alert and a settled order. The SEC record on alternative data and MNPI by who spoke and when, with a vendor checklist and a worked sample trace.
- How to run a trial of an alternative dataset: what the agreement coversA data trial is a short licence and an experiment. Fix the pass marks before delivery, read the FISD trial template term by term, then run seven tests in order and record each result.
- AI readiness signals: how to read a company website's stance on AIA company website states how it treats AI: what it keeps from crawlers and what it opens to agents. Every signal in one table, who defined each, and how to build a profile per company with hiring and intent.
- How to see which companies block AI crawlers in robots.txtGPTBot, ClaudeBot, Google-Extended and the rest: what each token governs, which group of a robots.txt applies to it, what counts as a stance on AI, and how to date a company's change of course.
- RFP questions to ask a buyer intent data vendorAn intent data RFP should make each vendor show what a score is built from. Eighteen questions in five groups, a grading scale, a worked scoring example and a back-test to run on sample data.
- How to evaluate a company data vendor in ten questionsTen questions for any vendor of company data, from coverage to change management, each with a document to request and a test to run on a sample. Our own answers are included, each with the public document behind it.
- Why we read job postings from the company's own boardA job posting can be read where the employer published it or where it was copied to. The source decides how many records a role produces, whose role it is and what its dates mean.
- Alternative data due diligence questionnaires, question by questionThe FISD questionnaire topic by topic, with the evidence each question calls for, and how Neudata and Eagle Alpha handle questionnaires once vendors have answered them.
- What alternative data scouts look for in a new datasetWhat Neudata and Eagle Alpha publish about how funds judge a new dataset, set beside five checks you can run on a company-level dataset, with the Fokals tables as the example.
- Building crawlers vs licensing company dataA crawler framework fetches pages, and company data needs more work after the fetch. What building takes, what a licence delivers in its place, and how the two combine.
- Alternatives to building your own company data crawlersFour routes to rows of company data from the web: your own crawler, a managed scraping service, open datasets or a licensed feed. What each takes off your hands, and what stays with you.
- Data provenanceData provenance records where data came from, when it was observed and what was done to it. What a record should hold, and how source and observation time appear in Fokals tables.
- Due diligence questionnaire (DDQ)The questionnaire a buyer sends a data vendor to check sourcing, rights, personal data and MNPI. What it asks, which standard forms exist and how to answer with documents.
- First-party dataFirst-party data is what an organisation collects directly from its own customers and operations. Two senses of the term, and why the second matters in due diligence on a data vendor.
- LEIThe 20-character code for a legal entity such as a company or fund. What a record holds, how the check digits work and how an LEI maps to the securities it issues.
- Material non-public information (MNPI)Information that a reasonable investor would find important and that has not been released. The two tests, the questions a fund asks of a data source and common mistakes.
- robots.txtrobots.txt is the file at the root of a website that tells crawlers which paths to avoid. How its rules are matched, what happens when it is missing, and why it is not security.
- Third-party dataThird-party data is information collected by someone else and supplied to you under licence. What to ask a supplier before you rely on it, and how company-level data differs from audience data.
- Web crawlerA web crawler visits pages automatically and records what it reads. How crawlers work, how they differ from scrapers and what separates responsible conduct from harmful.