Intelligence infrastructure

Three months.
Then you own the machine.

We build the system that reads primary records on a schedule, resolves the entities across them, screens what comes out against your mandate, and hands you something you can act on. Then we hand you the keys — your hosting, your code, no licence.

398.7MRecords we hold and operate across 24 databases
302Scheduled jobs running our own estate in production
114 GBPrimary-source data, all of it public record
<$1kWhat it costs us per month to run all of it
The problem

Most of what your firm needs to know is already published.

It is in filings, registries and regulatory disclosures — public, free, and effectively unreadable at volume. Firms solve this by hiring analysts to copy it into a database by hand, or by buying a platform that arrives empty and waits for someone to fill it. Both fail the same way: the work is never finished, so it is never current.

What we build instead

INGEST
Primary records, on a schedule Regulatory filings, corporate registries, ownership disclosures, sector data. Collected automatically, not by an analyst.
RESOLVE
One entity across every source The same company under its filing name, its registry name and its legal identifier, joined — which is the expensive part and the part that makes the rest possible.
SCREEN
Against your mandate, not ours Written criteria, applied the same way every time, with the disqualifiers recorded so a rejection can be checked.
DELIVER
A decision artifact Named companies, named people, and the filing each came from. Not a dashboard nobody opens.
GATE
Checks that fail loudly Every stage is measured. When a source goes stale or a join degrades, the system says so rather than quietly returning less.

The engagement

One project. Three months. Fixed.

MONTH ONE

Sources and identity

We wire the records that matter to your mandate and build the entity resolution across them. By the end of the month there is a populated store, not a schema.

MONTH TWO

Screening and the artifact

Your mandate written down as criteria, applied, and the output shaped into the thing your team actually uses — a screen, a memo, a queue. Reviewed against real output, not mockups.

MONTH THREE

Automation and handover

It runs on a schedule without us. Monitoring, gates, failure alerts, documentation, and a walkthrough with whoever will own it.

What it costs
$15,000 / month
Three months · $45,000 total · invoiced monthly in arrears

Fixed scope agreed in writing before we start, with the exclusions named. No discovery phase, no change orders for work inside the scope. If a month does not deliver what the scope said, you do not pay for it.

You own the result. It runs in your environment on your hosting. The code is yours at the end of month three. There is no per-seat licence and no lock-in, and continuing support afterwards is optional and quoted separately.

What is not included


Proof

We run one of these ourselves.

Not a reference architecture. A production estate: 398,694,291 records across 24 databases and 114 GB, maintained by 302 scheduled jobs, for under a thousand dollars a month.

01 / POPULATED

It arrives full

A deal platform ships you an empty database and a implementation timeline. Ours starts with the records already collected and resolved, so the first screen runs on day one rather than after a quarter of data entry.

02 / MEASURED

We publish our own failures

Our research estate runs eleven validation gates and five of them currently fail — named, not hidden. When we re-measured our own results against a proper benchmark the effects shrank by 75–82%, and we wrote that down. A system nobody measures is a system nobody should trust, including ours.

03 / OPERATED

We are the first user

Everything we would build for you is running against our own estate first. We find the failures on our own time, which is why the engagement is three months and not three quarters.

A system we built

An investor room, with readership

One component from a past build — a branded, access-controlled data room where the issuer can see which investor opened which document and who has gone quiet. Sample data, fictional company, no sign-up.

Open it
Codes — ISSUER (company view) · LP-MERIDIAN (investor view)

Start

Send us a mandate. We'll screen it.

Tell us in a paragraph what you look for — sector, geography, size, structure. We will run it against what we already hold and send back named companies, the people who signed their filings, and the source for each line. No charge, no call required, and we will tell you plainly if we hold nothing useful for your mandate.

jennifer@hegemonicgrowth.com

Jennifer Cole · Engagements