Data methodology

Evidence in. Explainable signals out.

Capital Radar separates observations, inferred indicators and confidence so users can investigate a signal without mistaking it for a confirmed event.

01

Collect

Structured public and licensed sources, authorized operator files and manual observations enter a controlled ingestion pipeline.

02

Normalize

Names, locations, URLs, stages, sectors and dates are converted into consistent formats before matching.

03

Resolve

Source records are connected to canonical companies, investors, LP organizations and funds. Ambiguous matches can be held for review.

04

Score

Transparent component scores combine relevant evidence. Missing data lowers confidence or receives a neutral treatment rather than becoming a confirmed negative.

05

Interpret

Capital Radar produces a plain-English hypothesis, supporting evidence and explicit verification language.

06

Correct

Human corrections and overrides are preserved so later imports do not silently replace reviewed information.

Signal families

What the scores mean—and what they do not.

Fundraising Radar

Uses successor timing, vintage, activity, strategy, performance context and source confidence to prioritize manager research. It does not confirm a fundraise.

Investor and capital matching

Uses sector, stage, geography, mandate, activity, similar-company and capacity context to rank possible relevance. It does not confirm appetite.

Startup momentum

Uses financing, stage, investor validation, hiring evidence, company context and confidence to prioritize company research.

Hiring signals

Uses unique dated job records, rolling time windows and source corroboration. Repeated listings are deduplicated before job volume is interpreted.

Market heat

Uses company, funding, investor and fund activity to compare similarly covered sectors. Coverage differences must be considered.

Confidence is part of the answer

A high score with weak evidence should not be treated like a well-corroborated signal. Capital Radar displays confidence and component context so users can decide what must be verified next.

Corrections matter

Private-market records change and sources can disagree. Reviewed corrections and overrides are preserved instead of being silently replaced by a later import.

Request platform access