Ask a simple question about a private company — how many people work there, what it actually sells, who invested in the last round — and you can usually find an answer. The harder question, and the one that matters when real money or a real decision is on the line, is: where did that answer come from?
That question is what data provenance is about. Provenance is the recorded origin and history of a fact: what source it came from, who wrote it down, when, and what has happened to it since. It is the difference between verifiable company data and confident-sounding guesswork. And in private company research — where there are no mandatory quarterly filings, no audited statements, and no single authoritative registry — provenance is not a nice-to-have. It is the foundation everything else stands on.
We built aVenture, a research platform for private company intelligence, around that conviction. This post explains what field-level provenance means in practice, why most company data you encounter doesn't have it, and how we engineered our platform so that every fact can answer for itself.
The problem: numbers with no origin
Most company databases present facts as flat values. An employee count is a number in a cell. A funding total is a figure on a profile. There is no visible answer to the questions a careful researcher immediately asks:
- Did this come from the company itself, a news article, or someone's estimate?
- When was it last checked?
- Has anyone — including the company — disputed it?
- Was it entered by a person, imported from a feed, or generated by software?
When data has no origin, every downstream use of it inherits an invisible risk. An analyst cites the number in a memo. The memo informs a decision. Months later, the number turns out to have been a three-year-old estimate scraped from a stale page — and nobody can reconstruct where it entered the chain. That failure mode is common precisely because provenance is usually discarded at the moment of data entry, and it can never be reconstructed afterwards.
Due diligence data quality is, at its core, a provenance problem. The diligence standard isn't "we found a number"; it's "we can show where the number came from and why we believed it."
What field-level provenance looks like
On our platform, provenance is not an attribute of a company profile as a whole. It is recorded at the level of the individual fact — because a single profile is assembled from many sources of very different reliability, and treating them as one blob hides exactly the distinctions that matter.
Every fact in our research graph carries four things:
1. The kind of source it came from
A fact ingested from a company's own website is not the same as a fact from a news article, which is not the same as a fact from an independent blog, a staff review, an AI research agent's finding, or a correction submitted by a user. We record the source category with the fact itself, so a researcher can weigh it accordingly. First-party statements carry a different kind of authority — and a different kind of bias — than third-party reporting, and the data model should preserve that distinction rather than flatten it.
2. Its verification status
Facts are explicitly marked as unconfirmed, confirmed, or disputed. Disputed facts additionally record who disputes them — the company itself, a related party, or a third party. This matters more than it might sound: a headcount figure disputed by the company is a very different signal than one disputed by a competitor, and a researcher deserves to see both the claim and the disagreement rather than whichever one happened to be written last.
3. The actor that wrote it
Every write to the graph records whether it was made by a human staff member or an AI research agent — and when it was an agent, the specific model that produced it. We think this is non-negotiable in an era when much research data is machine-assisted. If software contributed a fact, the record should say so plainly, and it should say which software. Accountability that stops at "the system added this" isn't accountability.
4. When it happened
Timestamps on creation and on every subsequent change, so the age of a fact is always visible — not just the age of the profile it sits on.
Corrections that don't erase history
Provenance would be incomplete if it only covered how a fact arrived. It also has to cover what happened afterwards.
Every change to every record on our platform lands in an audit trail: what changed, what the value was before, who or what changed it, and when. When a fact gets corrected — and in private company research, facts get corrected constantly, because companies pivot, teams grow, and old reporting goes stale — the correction doesn't silently overwrite history. The previous value, its source, and the change itself remain part of the record.
This has a practical payoff beyond tidiness. If you cited a figure in March and it reads differently in June, you can see exactly when it changed and why. Research you did in the past remains explainable in the present. For anyone whose work product is a memo, a model, or an investment committee document, that's the difference between diligence you can defend and diligence you have to shrug about.
Keeping junk out: validation at the moment of writing
There is a second, quieter half of data quality that provenance alone doesn't solve: making sure a fact is well-formed before it enters the graph at all.
Every category of research fact on our platform is governed by a validation contract that is enforced at write time. Numeric facts must fall within allowed ranges or take allowed values. Categorical facts must use a defined set of options rather than free-form strings. Even narrative research text is checked for shape — length and structure — before it is accepted.
The effect is that free-form junk cannot quietly accumulate. A malformed value doesn't become someone else's cleanup project six months later; it is rejected at the door. Combined with provenance, this gives the graph a property we care a lot about: everything in it is both traceable (you know where it came from) and well-formed (you know it satisfied the rules for its type when it was written).
Staleness is a data point too
A true fact from four years ago can be more misleading than no fact at all. So beyond source and structure, our records carry currency signals: facts and links are flagged as current or historical, and companies themselves carry an operating status, so a dissolved or acquired company doesn't masquerade as a going concern in your results.
Treating staleness explicitly — rather than letting old data sit indistinguishable from fresh data — is part of the same discipline. Provenance tells you where a fact came from; currency tells you whether it still deserves your trust today.
Why we hold ourselves to this
We've written before, in our draft privacy policy, about how we see public research data: as something that serves the public interest by helping investors and researchers make informed decisions. We take that framing seriously, and it cuts both ways. If research data is going to inform real decisions, then the burden is on the platform to make that data inspectable — to show its work, fact by fact, the way we'd expect any serious researcher to.
Source-backed research is the standard we'd want as users, and it's the standard we think the private markets deserve. A claim without a source is an opinion wearing a suit.
What this means for your research
Concretely, building on provenance-first data means:
- You can cite what you find. Facts arrive with their origin attached, so moving from "the database says" to "according to the company's site as of this date" takes no extra work.
- You can defend your diligence. The chain from source to fact to your memo is reconstructible, even months later, even after corrections.
- You can weigh conflicting information honestly. Disputed facts show the dispute instead of hiding it, and first-party claims are distinguishable from third-party reporting.
- You can trust the freshness signal. Stale facts and inactive companies are flagged as such rather than blending in.
We have not commercially launched yet — we're building this in the open, deliberately, because we think getting the foundation right matters more than shipping a bigger pile of unattributed data. If the approach resonates with how you think company research should work, we'd genuinely like you to try it early and tell us where it falls short.
Join the research preview waitlist at aventure.vc/free-research.