One builder replaced slow, manual outbound with a system that reacts instantly to real buying signals.
Live intent triggers the flow, accounts are filtered for ICP fit, leads are enriched only when there’s a reason to act, and outreach is launched with full context — all while activity logs automatically back to the CRM.
The result: faster outreach, better timing, and fewer wasted touches.
One of the recurring challenges in outbound isn’t finding leads. It’s timing.
Most teams already have access to signals like job changes, funding announcements, tech stack updates — but those signals tend to sit in dashboards, inboxes, or Slack channels until they cool off. By the time someone acts, the moment has passed, or worse, the outreach feels generic and disconnected from what actually happened.
This is the problem Tosin Togbe set out to solve.
Instead of adding another tool or building a complex system, he focused on one simple question:
What if every real buying signal triggered immediate, relevant action without manual steps in between?
Here’s how he built it.
Step 1: Start with live buying signals, not lists
The foundation of Tosin’s setup is real-time intent.
Rather than working from static lead lists or scheduled exports, his workflow listens for live events that actually change the likelihood of a conversation, including:
- Job changes
- New funding rounds
- Companies adding or changing tools in their tech stack
These events act as the trigger. Nothing moves unless something meaningful happens first.
This alone removes a lot of guesswork. Outreach isn’t based on assumptions or timing guesses, but on observable changes inside an account.
Step 2: Filter hard for ICP fit
Not every signal is worth acting on.
Before anything is enriched or routed, Tosin’s workflow checks whether the account actually matches his ICP. The system filters automatically based on:
- Region
- Industry
- Company size
If a company doesn’t meet the criteria, it’s filtered out immediately. No enrichment, no outreach, no noise.
This step is critical. It ensures that speed doesn’t come at the expense of relevance, and that reps only see opportunities that are genuinely worth their attention.
Step 3: Enrich only when there’s intent
Once a signal passes the ICP filter, enrichment kicks in.
Instead of enriching every lead upfront, Tosin enriches only when there’s a reason to act, pulling in:
- Verified work email addresses
- Direct phone numbers
This keeps data usage efficient and ensures that every enriched record is tied to an actual opportunity, not a speculative list build.
The result is clean, usable contact data exactly at the moment it’s needed.
Step 4: Route directly into outreach with context
From there, enriched leads are pushed straight into Outreach or Salesloft.
What makes this step work isn’t just automation, but context.
Each sequence references the specific signal that triggered the workflow:
- A recent funding round
- A team expansion
- A new tool added to the stack
Because the signal is carried through the entire flow, the message doesn’t sound templated or robotic. It sounds like someone who understands why now.
This is where relevance and speed meet. Outreach happens quickly, but it still feels considered.
Step 5: Keep humans in the loop with Slack alerts
At the same time, every qualified signal is posted to Slack.
This gives the team immediate visibility into what’s happening and creates optional human intervention when it matters. Reps can jump in manually if needed, or simply trust that the system is already handling the follow-up.
Slack becomes an awareness layer, not a bottleneck.
Step 6: Log everything back into the CRM
Finally, all activity syncs back into HubSpot.
Signals, enrichment, outreach, and movement are logged automatically, so pipeline visibility stays intact. There’s no need to chase updates or reconcile actions after the fact.
The CRM reflects what actually happened, without requiring extra effort from the team.
The result: speed without chaos
By connecting signals, enrichment, outreach, and logging into one continuous flow, Tosin reduced speed to lead from days to minutes.
More importantly, he removed the friction that usually comes with moving fast. Reps don’t need to watch dashboards. RevOps doesn’t need to clean up after automation. Outreach happens only when there’s a clear reason to reach out.
This is a good example of what builder-led outbound looks like today:
systems that respond to reality, move quickly, and stay grounded in context.
We’ll be sharing more real workflows like this in the Builders Series — practical setups built by operators who care less about tools and more about how everything connects.
Keep reading:
How one builder used n8n + Lusha’s API to enrich enterprise CTOs in mins
How Lusha uses job-change signals to re-activate high-intent prospects
Lusha + monday CRM: keep every board enriched with verified data
Waterfall data enrichment: why streaming data beats static stacking
FAQs
Buying signals are observable events that indicate a potential shift in intent, such as job changes, new funding rounds, or changes to a company’s tech stack. When used correctly, they help teams reach out at the right moment instead of relying on static lists.
Timing has a direct impact on response rates. Acting on a signal while it’s still fresh increases relevance and reduces the chance that a prospect has already engaged with another vendor.
By filtering signals through ICP criteria before enrichment or outreach, teams avoid contacting accounts that aren’t a good fit. This keeps sequences focused on high-quality opportunities only.
No. In this workflow, enrichment happens only after a signal is detected and the account matches the ICP. This keeps data usage efficient and ensures enriched records are tied to real opportunities.
All actions — signals, enrichment, outreach, and follow-up — are logged automatically in the CRM. This keeps pipeline visibility intact without requiring manual updates or cleanup.
Not necessarily. This approach works well for small and mid-sized teams that want to move quickly without adding manual processes, especially in environments where timing and relevance matter.
