Real-Time Expansion Signals: How to Respond to Market Entry Moves in Hours, Not Weeks
The average B2B company takes 47 hours to respond to a new lead. Most expansion signals get picked up days or weeks after they fire. By then, someone else is in the conversation. Here is how to build the infrastructure to respond the same day.
Three things need to be in place. First, the signal needs to surface the same day it fires — not when a weekly report lands or when a rep manually checks a database. This means daily-refresh data connected to an alert system. Second, the alert needs to route to the right person immediately — not sit in a shared inbox or a CRM queue nobody monitors. Third, the rep needs a pre-written message ready to go, referenced to the specific signal, so they can send within the hour rather than spending two days figuring out what to write. Most teams have the signal. They are missing the routing and the pre-written playbook. That gap — between a signal firing and a rep sending a relevant message — is where most of the first-mover advantage evaporates.
Why most teams are slow even when they have the signal
Here is what typically happens when a company registers a legal entity in a new market.
The entity filing appears in the country's official business registry. Pubrio picks it up the same day. A Crunchbase entry gets created days later. A LinkedIn company update may or may not follow. The news hits a trade publication, if it hits one at all, weeks after the filing.
The average team finds out about this signal at step three or four — LinkedIn or trade press — which means they are already 1–3 weeks behind the filing. By that point, the country manager hired to run the new market has been in their seat for a week or two, has had introductory calls with 4–5 vendors, and has a rough shortlist forming.
But the signal timing is only half the problem. The other half is what happens after the signal is detected.
The signal comes in. It goes into a CRM queue or a shared Slack channel. Someone assigns it. The rep looks at it, decides to research the account, opens 6 browser tabs, writes a first draft, gets feedback, rewrites it, and sends something 3 days later. Technically they acted on the signal. Practically they gave away the first-mover advantage entirely.
The close rate for responding within 5 minutes is 32%. For responding after 24 hours it drops to 12% — a 2.6x difference with no change to the offer, the rep, or the pitch. Speed is not a personality trait. It is an infrastructure problem.
The three things you need to respond in hours
1. Same-day signal delivery
The signal is only useful if it arrives the same day it fires. This sounds obvious. It is not how most data tools work.
Most B2B data providers batch their updates. Data is collected across a period and pushed in batches — weekly exports, monthly refreshes, quarterly database updates. By the time the signal arrives in your tool, weeks may have passed since the original event.
Pubrio refreshes its signal graph daily. When a company files a legal entity, hires a country manager on a regional job platform, or announces a local partnership in local-language trade press, the signal appears in Pubrio within 24 hours of the source event. That is the baseline requirement for real-time response: the signal must arrive the same day it is generated.
The second part of delivery is routing. A signal that arrives in Pubrio but requires a rep to manually log in and check is not a real-time signal — it is a self-service database. Real-time response requires the signal to be pushed to the rep, not pulled by them. This means either a native alert system (email or Slack notification when a monitored account shows a new signal) or an integration that pushes signals directly into the CRM as a new task or opportunity.
2. Immediate routing to the right person
A signal that arrives in a shared inbox is a signal waiting to go stale. The routing question — which rep owns this account, which signal type is this, how urgent is it — should be answered automatically before the signal reaches anyone.
Build the routing logic before the signals start arriving:
- Legal entity filed in a market where we have a sales team → Immediate alert to the AE who owns that territory, flagged urgent, 24-hour SLA
- Legal entity filed in a market where we have no sales team → Alert to sales leadership with a "should we engage?" prompt
- Exec move (country manager hired) at an Expanding-stage account → Alert to the AE who owns the account plus the SDR covering that region
- Funding signal with expansion mandate at an ICP-fit account → Alert to BDR team with a 48-hour SLA
- Exploring-stage signal (ad campaign, press mention) at an ICP-fit account → Add to monitoring list, no immediate outreach required
The routing logic is simple. The discipline is building it before the signal arrives rather than deciding case-by-case, which is how speed evaporates.
3. Pre-written messages for each signal type
The most common reason reps are slow is not that they are disorganized. It is that they do not know what to write. A legal entity filing in Indonesia is a concrete event, but what do you say about it? How do you reference it without sounding like you are tracking them? How do you make it relevant to what you sell?
The answer is to write the message before the signal fires — one template per signal type, per stage, per region. Not a generic email template. A signal-specific template with one blank to fill in: the company name, the market, and the specific signal type.
Examples:
Legal entity filing: "Hi [Name] — noticed [Company] just registered a legal entity in [Country]. Companies at this stage usually need [your category] within the first 60 days. We've helped [3 similar companies] set this up there — happy to share what worked for them in 15 minutes."
Country manager hire: "Hi [Name] — congratulations on the new role at [Company] in [Country]. I know the first 90 days involve evaluating a lot of new vendors. We work with companies entering [Country] specifically — happy to be a useful resource, no agenda."
Funding with expansion mandate: "Hi [Name] — saw [Company] just raised [round] with a focus on [market]. That usually means the [your category] decision is coming up. We've helped several companies make this call before the entity is even filed — happy to share what we've seen."
Each template takes the rep from signal-received to message-sent in under 10 minutes. That is the difference between a 47-hour average response time and a same-day response.
| Signal type | SLA | Route to | Message angle |
|---|---|---|---|
| Legal entity | Same day | Territory AE — urgent flag | We've helped companies set up in [market] at this stage — 15 minutes to share what worked |
| Exec move | Same day | AE who owns the account | Congrats on the new role — we work with companies entering [market], happy to be a resource |
| New office | 24 hours | Territory AE | Saw the new office in [city] — companies at this stage usually need [your category] within 30 days |
| Funding | 48 hours | BDR team | Saw the raise focused on [market] — that usually means [your category] decision is coming up |
| Partnership | 48 hours | AE — co-sell angle | Saw the partnership with [partner] — we work alongside them in [market], could be useful |
| Ad campaign / Press | Monitor | Add to watch list | No outreach yet — wait for a Committing or Expanding signal before engaging |
Putting it together: the same-day response workflow
When all three pieces are in place, the workflow looks like this:
- Pubrio detects a signal — legal entity filed in Indonesia for a company matching your ICP
- An alert fires to the assigned AE and their manager within the hour
- The AE opens the alert, sees the signal type and company context
- They open the pre-written legal entity template, fill in the company name and market, and send within 10 minutes
- Total time from signal to outreach: under 2 hours
This is not hypothetical. It is the operational result of building the three pieces — same-day signal delivery, pre-built routing logic, and pre-written templates — before the signals start arriving.
The teams that wait until a signal fires to figure out who should send what and when will average 47 hours. The teams that build the infrastructure first will average under 4 hours. 78% of B2B buyers buy from the first company to respond. That statistic does not care whether your product is better. It rewards whoever built the faster process.
Pubrio delivers daily-refreshed signals for 800M+ companies across 200+ markets — surfaced the day they fire, not weeks later. Pair it with routing logic and pre-written templates, and the 47-hour average becomes a same-day response.
Not When It Hits the News.
