Introducing SignalDock

Every day, municipalities publish permits, tenders go live, and companies announce expansions. Somewhere in that stream is your next customer. The problem has never been access to the data. It is the work between reading a publication and having a qualified opportunity in your CRM.

SignalDock automates that work.

From publication to pipeline

A signal moves through a fixed set of stages:

1. Ingest. Sources are polled on a schedule and stored idempotently.
2. Classify. An AI model decides whether the signal is relevant to your project.
3. Qualify. Deterministic scoring rules turn facts into a score and a decision.
4. Resolve and enrich. We find the organisation behind the signal and the people to talk to.
5. Sync. Opportunities land in your CRM with the full reasoning attached.

Scoring is intentionally not a black box. Every rule has a key, a weight and a reason, so a sales lead can see why a signal scored 78 and not 40.

const breakdown = scoreSignal(rules, facts, thresholds);
// breakdown.decision === "opportunity"
// breakdown.components[0].reason === "12,000 attendees within 500–20,000"

EventDock, the first organization

SignalDock started as the engine behind EventDock, which finds Dutch construction sites and events that need temporary camera security, WiFi and access control. Permits published on Overheid.nl are scored on size, duration, distance and product fit, then enriched through Apollo and synced to Attio.

The same pipeline now runs for any team with a public source and a CRM.

What is next

We are opening SignalDock to a small group of teams. If your pipeline starts with public data, start an organization or read the documentation.