Skip to content
CapexSignal.

Built for the job you actually do.

Almost nobody wants a project record. A scaffolding firm wants packages and timing; an owner wants said-versus-did; a fund wants evidence it can re-check. So projects are broken into packages, and project status is five separate dimensions rather than one string — a single status cannot serve someone filtering on procurement and someone filtering on construction at the same time.

Present public-source depth is not yet enough to promise every package in these examples. They describe the product model and the source-depth target. The live regional source and launch reports are the authority on what can be answered and purchased today.

Find work: contractors, OEMs and service providers

EPC contractors · equipment OEMs · turnaround, scaffolding, insulation and inspection services · industrial staffing · engineering consultancies

What they are buying: A reason to make a call this week.

  • Package-level detail, not project-level. “£42m boiler replacement” is useless to a scaffolding firm; “≈300 t of scaffolding, six-week window, Q2 2027” is a lead.
  • Stage targeting. Too early is a wasted call and too late means the package is awarded, so project state is five separate dimensions rather than one status string.
  • Alerts, not search. Nobody wants to run a query every morning — they want to be told when a project enters procurement.
  • Territory at subdivision granularity, because a Texas rep does not care about California.

Track rivals: owners, strategy and business development

Owners and operators · corporate strategy · business development

What they are buying: An accurate picture of what rivals are actually doing, not what they announced.

  • Said-versus-did per developer and per contractor, which needs a record that was never overwritten.
  • The moment a schedule slips — detected as a change between document versions rather than as a new announcement.
  • Who is winning what, joined across projects, packages and vendors.

Diligence: funds, lenders and quantitative research

Infrastructure funds · private equity · project finance · quantitative research

What they are buying: Evidence they can re-check, and data they can join to their own.

  • A contemporaneous record. “What did you say in March?” has to have an answer, or the record cannot be used in diligence.
  • Bounded SQL and Parquet export, because exporting to a spreadsheet is not joining to their own data.
  • Supply-chain constraint: if one turbine supplier holds forty units of backlog, every project depending on them carries schedule risk that no individual project record shows.

Measure policy: agencies, regulators and skills bodies

Economic development · energy and industrial policy · skills bodies · regulators

What they are buying: Whether the policy worked, and what happens when it changes.

  • Policy joined to assets, at national and sub-national scope, with effective windows so attribution is answerable as of a date.
  • Labour demand curves derived from construction schedules and package labour content.
  • A record of what was believed when a decision was taken, not just what is true now.

The intersections are the actual product

Each of these is one derived artefact serving two buyers who currently pay two vendors. They exist because the graph spans projects, packages, vendors, policy and time — which is exactly the shape a per-sector table of current values does not have.

IntersectionOne artefact
Lead-gen × InvestorSupplier-addressable pipeline — packages by discipline, geography and date
Lead-gen × GovernmentLabour demand curves from schedules × package labour content
Tracking × InvestorSaid-versus-did, per developer and per contractor
Government × InvestorPolicy attribution and sensitivity
Tracking × Lead-genVendor backlog and schedule risk

The one nobody sells: supply-chain constraint

Project → package → equipment → vendor → that vendor's other commitments. If one HRSG supplier holds forty units of backlog, every project depending on them carries schedule risk that no individual project record shows. That inference needs a graph spanning projects, packages, vendors and time — a genuinely new capability rather than a better version of an existing one.