Signals overview
Timely reasons to engage your network before opportunities go cold.
Overview
Signals answer why now, company updates, event activity, municipal changes, and BD review prompts, so your team does not rely on memory alone. For BD and marketing leads, a short weekly signals pass is often the fastest way to turn a contact list into outreach with context.
When to use this
- Monday standup: Skim what changed on target accounts and stale relationships.
- Before a developer or owner call: Confirm there is a recent reason to reference beyond “checking in.”
- After a conference: Tie event activity back to people you met or firms on your shortlist.
Signal families
| Family | Examples | Doc |
|---|---|---|
| Company | News, hires, project hints | This page + from events |
| Cities | Municipal and market activity | Municipality research |
| Events | Speakers, sessions, attendance | Signals from events |
| BD review | Overdue touchpoints, stale accounts | BD review overview |
The All tab merges company, city, and event signals into one chronological feed. Each item carries a signal kind (what happened) and BD topics (why it might matter for pursuit).
Availability depends on your workspace plan and seat type. Revenue and Network seats see the fullest pursuit surfaces; see Plans and pricing.
Taxonomy and account linking
Every canonical signal is classified at ingest time:
- Signal kind: structured type such as project activity, leadership change, municipal action, or event activity.
- BD topics: pursuit angles such as timing, relationship, early opportunity, procurement, or market intel.
Toolblocks also links signals to accounts in your workspace when there is a confident match (company name, domain, geography, or a manual link you add). On an account:
- About this account: direct matches (named party, domain, manual).
- In their markets: geographic overlap only (useful context, not a direct account hit).
You can dismiss incorrect links or add manual links from the account signals panel. Weekly priorities use linked evidence with source URLs for review.
Steps
Open Signals from the workspace sidebar (under Win work in docs).
Open the signal, verify the source, then log activity or schedule follow-up, do not send automated outreach without review.
Dismiss noise aggressively; a short weekly review beats an overflowing feed.
Signals support proactive BD. They do not guarantee accuracy. Confirm on the source link before referencing in email. AI summaries are draft for review.
Related
- Browse all signals, public catalog of what Toolblocks can surface
- Win work overview
- Research overview
- Follow-up reminders