Evidence

Check our work.

Every company-data vendor says its scoring is intelligent and its data is fresh. Almost none of them will show you the table, the cut-off, or the moment they stopped looking. This page is those three things.

Five exhibits

01 · Exhibit one

Three rounds. The record moved first.

Three European companies that announced funding this year. For each one, everything our record already held before the announcement — with the dates, and with the rows that were never certain marked as never certain.

How to read a date here

Event date. The day the thing happened — the article, the post, the round.

Measured on. The day we saw it. The change happened at some point before this date, not on it.

Netherlands

Lucend

days before the announcement

22 Dec 2025 Signalled intent to raise Not confirmed

Turned up at an investor event to meet capital. Nobody announced anything — we inferred it, and stored it as an inference.
1 Jan 2026 Raised a round

$3.3M seed.

Formerly Coolgradient; the company renamed before the round. Two earlier award rows in the record still carry the old name, which is why a name match alone is not enough to follow a company.

Netherlands

SOUS

days before the announcement

measured 23 Jan 2026 Open roles

Roles appearing on the careers page.
measured 6 Feb 2026 Homepage repositioned

99.2% of the homepage content had changed since we last read it.
measured 20 Mar 2026 Open roles
measured 23 Mar 2026 Homepage repositioned

A second near-total rewrite, three days before the announcement.
26 Mar 2026 Raised a round

€4M seed.

Every row before the round is a background-tier signal — individually worth 1 or 2 on the weighting opposite. On its own, none of this is a reason to call anyone. That is exactly why the weighting exists.

Belgium

Ventory

136

days before the announcement

27 Dec 2025 Won a named customer

New customers in MedTech.
20 Jan 2026 Senior hire

A business development hire — a new decision-maker, often with a mandate to change tooling.
20 Jan 2026 Achieved a certification

ISO/IEC 27001. Compliance certifications often precede an enterprise sales motion.
measured 27 Jan 2026 Homepage repositioned
12 May 2026 Raised a round

€2.65M, led by KBC Securities.

The strongest of the three, and the one with the least drama in it: a customer win, a senior hire and a certification, months apart, all notable-tier. A market this size produces that pattern constantly — reading it is the work.

None of this is a prediction.

We did not know these rounds were coming, and a page that claimed otherwise would be the exact thing this one exists to argue against. The claim is narrower and it is checkable: before each announcement, our record already carried dated movement at that company — a hiring push, a full homepage rewrite, a certification, a senior hire, an investor event. Whether that movement was worth a conversation is a judgement. Making that judgement, on a market too big to read by hand, is the product.

SOURCE · signal rows read from the production record on 14 Aug 2026 · every row above is reproducible against the company profile it belongs to

02 · Exhibit two

A rumour, marked as a rumour.

The earliest row in the strongest of those three timelines is not an announcement. Nobody said they were raising. What we saw was a company turning up at an investor event, and what we wrote down was that we had inferred it.

We read every published signal taxonomy in this market. Not one of them separates an announcement from an inference. Ours does, on every row, in the field itself — which means a model reading our data downstream cannot quietly promote a guess into a fact.

Ten days later the round was announced and the row that carried this warning turned out to be right. It kept the warning anyway.

One row, as stored Not confirmed

"date": "2025-12-22",
"label": "Signalled intent to raise",
"category": "funding",
"tier": "major",
"unconfirmed": true,
"confidence_note":
   "Rumour or inference, not an
    announcement. Do not relay as
    established fact.",
"meaning": "Signalled an intent to
   raise; the round has NOT closed."

03 · Exhibit three

Detection is the cheap half.

Finding events is not hard any more. The expensive half is deciding what never reaches you — and being able to read that decision. This is the actual weighting, rendered straight from the configuration file the product runs on. If an engineer changes a number, this page changes with it.

critical4 of 5 shown

Weight 10

Shutdown

Weight 10

Shutdown Risk

Weight 9

Was acquired

Weight 9

IPO Announced

major4 of 6 shown

Weight 8

Raised a round

Weight 7

Acquired a company

Weight 7

Senior departure

Weight 6

Signalled intent to raise

notable4 of 19 shown

Weight 5

Launched a product

Weight 5

Announced an expansion

Weight 5

Announced a partnership

Weight 5

Senior hire

background5 of 13 shown

Weight 3

Pivot

Weight 3

Acquisition Rumor

Weight 2

Open roles

Weight 2

Open role in a key function

Weight 2

Attended an event

SOURCE · config/signal_insights.php · read at page render, not transcribed

Weighted, not counted

Turning up at a conference is a 2. A closed round is an 8. Counting rows instead of weighting them would let the noisiest event type win every week.

Thresholded at 75

An event becomes work for you only above a score of 75. Below it, it stays in the record as context — and the record says so rather than hiding it.

Suppressed, not repeated

Decay windows and per-account suppression stop the same company taking a slot twice. When you dismiss a card, the reason is written back and the weighting learns from it.

Dropped in the open

Everything cut stays queryable through the API. We are not hiding it from you — we are refusing to send it.

Not a black box: everyone says their AI decides what matters. Ours is a table you can read and a threshold you can check.

04 · Exhibit four

Announcements are published. Changes are not.

Any assistant can look up a company you name. None of them can tell you which one, or what moved.

One company, two scansacme.com

employees

12 May 124 → 11 Aug 163

open roles

12 May 4 → 11 Aug 19

followers

12 May 8,240 → 11 Aug 9,110

homepage

“built for enterprises” → “built for developers”

No page publishes these four lines. They are computed, not written.

The difference was never a document

Retrieval finds what someone published. Nobody publishes a delta — it is computed against a record, not written down and indexed.

It cannot be back-filled

Nobody can tell you what a homepage said in March unless they crawled it in March. The record only grows forwards.

The announcement is the easy half

Anyone can find a funding round once they know whose round to look for. Which company, how fast, and whether it is a pattern — that is the record.

This is the part a better model does not solve: a larger context window cannot see a state it never stored. We run on the same models you do — the record is the part they cannot bring.

Figures schematic · mechanism live — monthly change computed against the previous month's record

05 · Exhibit five

When we haven't looked, the answer says so.

The dangerous failure of a company-data source is not a wrong answer. It is an empty one. A blank result reads as “nothing happened here”, when what it usually means is “nobody checked”. A person might catch that. A system running overnight will not.

So every answer we return carries how recently we observed that company and a flag saying whether the absence of signals means anything at all. When it doesn't, whatever is reading us is told to say so rather than guess — and to ask for a refresh instead of writing the account off.

How this reaches an agent

Attached to every answer

"coverage": {
  "monitoring": "periodic",
  "signal_absence_is_meaningful": false,
  "interpretation":
     "We check in on this company rather
      than following it continuously, so
      its record is not guaranteed to be
      complete right now. Do not read an
      empty list as a quiet period.",
  "refresh_recommended": true
}

A real block, returned for a real company on 14 Aug 2026

Talk to the people who will do the work.

Name your rivals and your question. Your analyst replies within 1 business day. NDA on request, before the scope call. Your findings never train another client's agent.

Starts with a 30-minute call.
Fully credited if you continue.

Book a 7-day Readout

This week 30-Minute Scope Call Kickoff 10 Rivals Named Day 7 Rival Readout Day 14 Your Radar Goes Live This week 30-Minute Scope Call Kickoff 10 Rivals Named Day 7 Rival Readout Day 14 Your Radar Goes Live This week 30-Minute Scope Call Kickoff 10 Rivals Named Day 7 Rival Readout Day 14 Your Radar Goes Live This week 30-Minute Scope Call Kickoff 10 Rivals Named Day 7 Rival Readout Day 14 Your Radar Goes Live