Landscape
How Knowledge Company compares
Two families share this space: tools that compare your content against a source of truth and report the gap, and registries that maintain the record itself. This page explains the distinction, the four questions that separate them, and what we run today.
Last reviewed 1 September 2026
There are two families here
Almost everything in this landscape is one of two things, and the distinction decides what a product is able to promise.
Checkers
Compare content against a source of truth and report the gap. Genuinely useful — and each of them treats that source as somebody else’s problem, which caps the accuracy score any of them can produce.
Registries
Maintain the canonical record and syndicate it. MDM does this for entities, PIM for product attributes, Veeva for pharma claims. Knowledge Company does it for the claims written in prose.
Four questions that locate every company here
01
Ground truth
What do they compare against? Checkers assume it, registries produce it. This one question sorts the whole field.
02
What fires it
Across the landscape there are about eight distinct triggers — traffic decay, a commit, a ticket spike, a calendar reminder. None of them is a fact changing.
03
Write access
Almost every tool writes to exactly one system: the one it lives inside. The exceptions are the registries, which push one record to hundreds of external channels.
04
Who buys it
Marketing budgets are contested and shrinking. Risk, compliance and regulatory budgets grow on exposure and rarely churn.
What we run
What we actually do
One loop, run on a schedule, against pages you have already published. Three steps, the same everywhere — only the last one changes by platform.
01
Extract the claims
We read the surface and pull out every factual assertion — numbers, dates, prices, names, promises, links. The unit is the claim, not the paragraph.
02
Check each against a source
Your pricing page, your product, your docs. Anything that disagrees with the current state of the company is flagged with the specific clause that broke.
03
Edit in place and stamp it
The correction lands in the live post, not a changelog nobody reads. Each one carries a published date, an updated date and a verified date.
Live today · 03 surfaces
Where it runs today
Three surfaces are live. The rest of the queue is in build, and we would rather say so than draw you a page for something that does not exist yet.
01 · Live
Medium
Your Medium archive keeps making claims long after they stopped being true. We read it, check every claim, and correct the post in place.
See what decays →
02 · Live
Substack
You cannot unsend a newsletter, but the archive is what keeps being read. We maintain it issue by issue, at the same URL.
See what decays →
03 · Live
AI Search (GEO)
Your claims get repeated to people who never visit the page. We keep what the answer engines learn from you current, and cited.
See what it learns →
See what your own pages currently claim
Most of this category reports a gap against a record somebody else has to maintain. We maintain the record. Start with the whitepaper.