How to Automate Expansion Signal Routing: A 5-Step Operational Blueprint
The hard part, to begin with, is to find an expansion signal. Teams know who owns it, what to send and when to act. Most teams fall apart without someone checking a database. This is the 5-step blueprint for automating signal routing from detection to outreach.
Five steps, built in order. Step 1: connect a daily-refresh signal source so signals arrive the day they fire, not in a weekly batch. Step 2: classify every signal by type and urgency before it reaches a rep — legal entity filings are same-day priority; Exploring-stage signals go to a monitoring queue. Step 3: define routing rules that assign each signal to the right person automatically, without anyone making a manual decision. Step 4: attach a pre-written message to every signal alert so the rep can respond within minutes, not days. Step 5: log every action back to CRM so signal performance is measurable and the workflow can be improved. Teams that have all five steps in place respond to high-priority signals the same day. Teams missing any one of them average 47 hours or more.
The problem with manual signal routing
Most teams that use expansion signals have the same operational failure: the signal arrives somewhere, but nobody knows whose job it is to act on it.
A legal entity filing surfaces in Pubrio. It lands in a shared Slack channel or a CRM notification queue. The sales manager sees it, tags someone, that person looks at it two days later, spends an afternoon researching the account, writes a first draft, and sends something on day three. Technically the signal was actioned. Practically the first-mover window — which closes in days for high-confidence signals — is gone.
A strong routing workflow needs to do three things: deliver the alert instantly while the signal is still fresh, add context so the rep understands why the event matters before they open the source, and suggest the next move so the rep is not hunting for a reason to reach out and deciding what to say at the same time.
Most teams have the delivery. They are missing the context and the suggested next move. That gap turns a 2-hour response into a 47-hour response.
The five steps below build the full workflow — from signal detection to outreach sent — with no manual handoff required.
Step 1 — Connect a daily-refresh signal source
Signals must arrive within 24 hours of the source event. If your source batches weekly, the routing logic fires days after the event — and the window may already be closed by the time the rep sees it.
Pubrio refreshes daily across 200+ markets. When a company files a legal entity, hires a country manager, or announces a local partnership, the signal appears in Pubrio within 24 hours. Connect via API, HubSpot, or OttoKit — and the signal enters the workflow the day it fires.
What to configure: Connect Pubrio via HubSpot or OttoKit. Confirm daily refresh is active. Test by verifying a known signal event appears in your system within 24 hours of the source filing.
Step 2 — Classify signals before they reach a rep
Not all signals require the same response. A legal entity filing at an Expanding-stage account needs a same-day response. A geo-targeted ad at an Exploring-stage account needs to go into a monitoring queue with no immediate outreach. Sending both to the same rep queue with the same urgency produces one of two outcomes: the rep treats everything as low priority, or the rep burns time on Exploring signals that should not be actioned yet.
Build classification logic that runs before the signal reaches anyone:
Priority 1 — Same day: Legal entity, executive hire, office lease, licence filing. Route immediately to territory AE with a 24-hour SLA.
Priority 2 — 48 hours: Funding with expansion mandate, partnership, local domain. Route to AE or BDR.
Priority 3 — Monitor: Geo-targeted ads, conference, press mention. No outreach yet. If a Priority 1 or 2 signal fires for the same account within 90 days, escalate immediately.
Routing without an SLA is worse than no routing at all — at least with no automation the signal stays visible. Assigning a signal to a rep who never opens the record means the signal effectively disappears. Build SLAs into the routing logic before anything is live.
What to configure: Three-tier classification rules in your CRM or automation tool (OttoKit or Hubspot). Every signal gets classified before routing — never leave classification as a manual rep decision.
Step 3 — Route to the right person automatically
Once classified, the signal needs to reach exactly one person — not a shared inbox, not a team channel, not a manager who will reassign it. Every manual step between signal and rep adds hours.
Build routing rules that resolve ownership automatically:
- Territory AE for new market signals (coverage gap flag to leadership if no AE assigned)
- Account AE + SDR for existing CRM accounts
- BDR for ICP-fit accounts not yet in CRM
- CSM or AM for signals at existing customers — this is an expansion revenue trigger, not new business
The routing logic is simple to write. The discipline is building it completely before any signals start flowing — so there is never a signal in a grey zone where someone has to decide manually.
What to configure: Workflow rules in HubSpot (workflow enrollment), or OttoKit. Every signal type should have exactly one owner defined. If it does not, the workflow is not complete.
Step 4 — Attach a pre-written message to every alert
Reps are slow because they open the alert and spend 90 minutes figuring out what to say. Pre-write one message per signal type, attach it to every alert, and the rep fills in one variable — company name and market — and sends in 10 minutes.
Legal entity filing: "Hi [Name] — noticed [Company] just registered an entity in [Market]. Companies at this stage usually need [your category] within the first 60 days. We've helped [similar companies] set this up there — happy to share what worked in 15 minutes."
Executive hire: "Hi [Name] — congrats on the new role at [Company] in [Market]. First 90 days usually involve evaluating a lot of new vendors. We work specifically with companies entering [Market] — happy to be a useful resource, no agenda."
Funding with expansion mandate: "Hi [Name] — saw [Company] raised [round] with a focus on [Market]. That usually means the [your category] decision is coming. We've helped several companies make this call before the entity is even filed — happy to share what we've seen."
Across a 10-rep team acting on 5 signals per week, that is 70 hours of rep time recovered weekly.
What to configure: One template per signal type, linked from every CRM task or Slack alert. The rep should never have to hunt for it.
Step 5 — Log every action back to CRM and measure
Build CRM writeback at every step:
- Signal detected → activity logged (type, date, source)
- Alert sent → task created with SLA timestamp
- Message sent → activity logged against account
- Reply received → opportunity created and linked to signal
- Deal closed → signal type tagged for attribution
Run a signal attribution report every 90 days: which types produced the most pipeline, which stages converted highest, which markets were most active. Signal routing is the highest-leverage bottleneck to automate first — it determines whether first-mover advantage is captured or lost on every signal your team receives.
What to configure: CRM automation rules logging a task at each step. 90-day review cadence for attribution reporting.
How Pubrio fits into the routing stack
Pubrio is Step 1 — the daily-refresh signal source that feeds the entire workflow. 16 signal types across four expansion stages, sourced from local registries, regional job platforms, and local-language trade press across 200+ markets, refreshed every 24 hours.
Connect via:
- HubSpot — workflow enrollment triggered by signal type and stage
- OttoKit — automation workflows triggered by signal events
- API — for custom routing logic in any tool your team already uses
Once connected, Steps 2–5 are built in your automation tool of choice. Pubrio provides the signal. Your routing logic decides who gets it, when, and with what message.
800M+ companies. 50+ local sources. 200+ markets. Daily refresh.
Your Routing Workflow.
