See it first. Act earlier.
A transparent methodology for evidence-backed project intelligence
Project-Pulse provides business intelligence, not confirmation that a procurement will occur. Its purpose is to help commercial teams investigate earlier with a clear source trail.
Last reviewed 26 July 2026
Source discovery
Documents are discovered through public websites, sitemaps, source registries, sector packs, public search fallbacks where configured and official-domain verification. Crawling respects robots rules, response limits and public-only boundaries.
Extraction and signal detection
Project-Pulse extracts structured fields only after a document has been downloaded, parsed and passed evidence filtering. Unknown values remain unknown rather than being filled with guesses.
Evidence versus inference
Evidence is the text, table row, notice or document reference found in a source. Inference is the commercial interpretation that a project may be moving stage, that a team may be forming or that a role may remain open.
Confidence and limitations
Confidence is strengthened by repeated evidence, clear project identifiers, named organisations, dates and source quality. Automated analysis can still be wrong, stale or superseded, so users should validate material opportunities before acting.
Duplicates, stale records and corrections
Duplicate signals should be linked into one opportunity with multiple evidence records. Stale or superseded information needs review as new source documents appear. Corrections can be reported through the contact route.
Editorial and intelligence note
Project-Pulse provides business intelligence based on permitted public information. An early signal is not confirmation that a procurement will occur, and users should validate material opportunities against original sources and later updates.