Projects
How SignalDock groups signals onto a real-world project and its companies.
A project is a durable entity in an organization: a construction site, event, or other job that more than one signal can point at. Signals keep their own history; the project is the resolved “what is this about?”.
Matching
Entity resolution runs after a signal is scored (and not ignored). Matching is deterministic first, then AI disambiguation:
| Method | Typical evidence |
|---|---|
| Domain | Company website / email domain |
| Registration | KVK or other registry id |
| Name | Normalized name |
| Address | Address + geocode (PDOK; failure never blocks the stage) |
| Source id | Stable id from the source system |
| AI | Disambiguation when deterministic methods disagree |
Each candidate is stored as an entity_match with confidence, reasoning, and
a decision (auto_merged, suggested, or rejected). Low confidence is never
auto-merged.
Companies and roles
Projects link to companies with a role: applicant, owner, contractor, architect, organizer, or other. Contacts hang off the company (persona, email, phone, LinkedIn) after enrichment.
What you do with a project
From the project you can open attached signals, see companies and
contacts, and follow opportunities created from high-scoring signals. The
project is not the CRM record: sync writes companies, people, and deals
through the CRM provider and records external ids on crm_sync_records.
Last updated on