A signal-based prospecting workflow is an outbound process that uses account-level buying signals — funding events, executive hires, headcount surges, and technology changes — to identify which ICP-fit companies are in an active purchasing window and time outreach to the signal rather than an arbitrary cadence.
The difference between signal-based and calendar-based prospecting is conversion rate. A rep who reaches out two weeks after a company closes a Series B round is reaching a team that just received a mandate to scale, has budget to deploy, and is actively evaluating vendors. A rep who reaches out to the same company on an arbitrary Tuesday in month three of a cadence is reaching a team that may have no active need at all.
What counts as a buying signal
Not every company change is a buying signal. The ones that consistently indicate purchase intent in B2B sales are:
Funding events. A company that closes a Series A, B, or growth round has typically committed to a hiring and tooling plan. The window for vendor conversations is roughly 30–60 days post-announcement, before budgets are locked and the new headcount is hired.
Executive hires in the target function. A new VP of Sales, CRO, or Head of RevOps typically evaluates the existing tech stack within the first 90 days. Reaching out within two weeks of the hire announcement — before the evaluation begins — puts you ahead of the process rather than in it.
Headcount growth of 15%+. A company growing its sales or revenue team by 15% or more in a quarter is scaling its go-to-market motion. The tools and data needed to support that scale are typically purchased at the same time.
Technology stack changes. Adding or replacing tools in the stack — particularly in adjacent categories — signals that the buying team is actively evaluating vendors and willing to make purchasing decisions.
M&A activity as acquirer. A company that has just acquired another business needs to consolidate its GTM stack and often re-evaluates every vendor contract in the process. This is a window, not a certainty — but it is worth tracking.
How to build the workflow: step by step
Step 1: Define your ICP before layering in signals.
Signal-based prospecting only works if the underlying account list is ICP-fit. A funding signal at a company that is the wrong size, wrong industry, or wrong geography is not a priority — it is noise. Start with a clean ICP definition: industry, headcount range, geography, revenue, and technology stack. The signal layer sits on top of this, not instead of it.
Step 2: Build a monitored account list.
Create a list of target accounts that match the ICP and monitor them continuously for signals. This is not a static list — it should update when new companies match the ICP criteria and when existing accounts show a signal worth acting on. In Lusha, this is done through the Signals layer, which monitors accounts and surfaces new events as they occur.
Step 3: Set signal thresholds for each trigger type.
Not all signals have equal urgency. Define the response window for each:
- Funding event → reach out within 14 days
- Executive hire → reach out within 7 days (the evaluation window opens immediately)
- Headcount surge → reach out within 30 days
- Tech stack change → reach out within 14 days
Outside these windows, the signal value degrades quickly. A funding announcement from 90 days ago is cold news.
Step 4: Find the verified contact before the signal expires.
When a signal fires, the next step is finding the right contact at the account — the person whose role is most affected by the signal — and validating that contact before any outreach is made. A new VP of Sales hire means the right contact is the new VP, not the previous contact at that company. Use Lusha to find the most senior verified contact in the target function and confirm the email and direct dial are current.
Step 5: Build the outreach around the signal, not the product.
The first outreach after a signal fires should open with the signal, not the pitch. “Congratulations on the Series B — most teams your size find they need to solve X around the time of a round like this” is a different conversation than “I’d like to tell you about our product.” The signal is the reason for the call. The product is the solution to the problem the signal implies.
Step 6: Track signal-to-opportunity conversion by signal type.
After 90 days, review which signal types are converting to first meetings and which are not. Funding events may convert at 15%; headcount surge may convert at 8%. That data tells you where to concentrate monitoring and outreach effort going forward.
What a working signal-based workflow looks like
A well-functioning signal-based workflow produces a daily or weekly alert of new signal events across the monitored account list, each with a verified contact, a recommended outreach angle, and a response window countdown. Reps do not need to search for who to call — the signal surfaces the account, the contact, and the timing in one place.
With Lusha connected to Claude, this workflow runs as a single prompt: “scan my target accounts for new signals in the last 7 days, find the right verified contact at each, and draft the outreach angle for the top three.” The output is a prioritized call list with verified contacts and signal-specific messaging — built in minutes rather than hours of manual research.
