//Updates & Support

FindEpcmai Updates — What we've built,
how it works, and where it's going

We publish release notes for every meaningful update — new signal sources, pipeline coverage extensions, architecture changes, and feature launches. This is the full record.

CURRENT PRODUCTION ENVIRONMENT

Version 2.0 — Current Release

Status: Live & Operational // Latest
WHAT CHANGED

The Complete Pipeline

V2 is the full system. Where V1 proved the signal — that early project intelligence could be captured at scale and made useful — V2 builds the complete intelligence pipeline around it. Every project that enters the system now passes through a structured, multi-stage architecture: ingestion, classification, deduplication, validation, matching, enrichment, and alerting. Nothing reaches your feed that hasn't passed through the full pipeline.
PIPELINE ARCHITECTURE

Architecture — How V2 Works

Click through the stages of the V2 intelligence pipeline below to inspect how data points are processed and what updates were introduced:

STAGE SPECIFICATIONS // 01

Stage 1 — Signal Ingestion

Thousands of sources are monitored continuously across regulatory portals, government databases, stock exchange filings, corporate announcements, environmental registries, and industry publications. Sources are monitored in real time — not batched weekly. Each raw data point captured is called a signal candidate — an unverified piece of information that may indicate project activity.

WHAT'S NEW IN V2

Source coverage extended significantly. Signal candidates are now captured across multiple geographies and regulatory frameworks simultaneously, with source credibility scoring applied at ingestion.

STAGE HEALTH: MAPPED & VERIFIEDPIPELINE INTEGRATION ACTIVE
UNIQUE SIGNALS TRACKED1,000+
VALIDATED PROJECT DATABASE5,000+
TRACKED SIGNAL TYPES5 Types
INTELLIGENCE PIPELINE STAGES6 Stages
ALERT DELIVERY RESPONSEReal-Time
// LEGACY BUILD ARCHIVE

Version 1.0 — MVP Release

Status: Superseded by V2 // 4 Months Ago
THE PROOF OF CONCEPT

What V1 Was

V1 was the proof of concept — the answer to one question: can early project signals be captured at scale, classified reliably, and made useful to a BD team?

The answer was yes. V1 shipped a working signal ingestion and classification pipeline, a basic project database, and a manual-review feed. It was intentionally narrow.

V1 ARCHITECTURAL LIMITATIONS
Signal Ingestion — V1

A curated set of sources monitored on a scheduled basis — regulatory portals, select government databases, and industry publications. Ingestion ran on a fixed schedule rather than continuously.

Limitation: Scheduled ingestion introduced lag. Signals captured hours or days after publication rather than in real time.

Signal Classification — V1

Rule-based classification using keyword matching and source-type tagging. Signal type was determined by source category and keyword presence rather than learned model.

Limitation: High false positive rate on ambiguous signals. Signals from multi-topic sources were frequently misclassified.

Project Database — V1

Projects were logged as individual records linked to their originating signal. No deduplication.

Limitation: Significant duplicate rate in the database. Users saw the same project multiple times, reducing feed quality and trust.

Feed — V1

A chronological list of new project records, manually reviewed before publication. No personalisation or relevance scoring.

Limitation: Feed was not personalised. Users had to manually filter for relevant projects, reintroducing the same problem.

Alerts — V1

Weekly digest email summarising new projects added in the previous 7 days.

Limitation: Batch delivery meant users received intelligence up to 7 days after a signal was captured. No event-driven alerting.

V1 OUTCOME AND PILOT METRICS
VALIDATED PROOF

Early project signals can be captured at scale from public sources

CLASSIFICATION RATE

AI classification of signal type is viable with acceptable accuracy

PILOT ENGAGEMENT

Pilot users engaged consistently with the feed, validating market need

1,000+ UNIQUE SIGNALS CAPTURED5,000+ PROJECT RECORDS LOGGED (PRE-DEDUPLICATION)
ARCHITECTURE MATRIX

V1 MVP vs. V2 Current Release

CapabilityV1 MVPV2 Current
Signal IngestionScheduled, select sourcesContinuous, broad source coverage
ClassificationRule-based, keyword matchingAI model, multi-factor scoring
DeduplicationNone — duplicate records commonEntity resolution engine
Project validationManual reviewAutomated validation pipeline
Feed personalisationNone — same feed for all usersAI Match Feed, scored per user profile
Relevance scoringNot present5-dimension scoring model
Stakeholder dataSparse, manually curatedAutomated enrichment at scale
Alert deliveryWeekly batch digestReal-time, event-driven
Geographic coverageLimitedMulti-geography, multi-regulatory
FUTURE SPECIFICATIONS

What's Coming

The next release cycle will focus on expanding pipeline intelligence and introducing native CRM sync triggers:

// NEXT 01

CRM & ERP integration — pushing matched projects and stakeholder records directly into Salesforce, HubSpot, Zoho, SAP, and Odoo

// NEXT 02

Expanded signal types — hiring activity signals and corporate restructuring announcements added to the classification model

// NEXT 03

Stakeholder contact enrichment — adding verified contact details to identified stakeholder records

// NEXT 04

Team collaboration features — shared pipeline views, pursuit tagging, and team-level alert management

FindEpcm
STAY UPDATED

Want to know when new signals hit your sector?

Early access users get notified the moment new signal sources or geographies are added that match their business profile.