Bombora Setup Guide for Outbound Sales Teams (2026)

Most outbound teams send the same sequence to every account on their list and hope timing works out. It usually does not. A Bombora setup guide for outbound teams solves the timing problem by telling you which accounts are actively researching your category right now, so your reps reach out while the buyer is already leaning in. Intent data does not replace a good offer or a clean list, but it does answer the one question cold outreach can rarely answer on its own: who to email this week, and why now.

We fold intent signals into the systems we run for B2B clients, so this guide walks through the full setup the way we actually do it. You will learn how to define intent topics, connect the data to your stack, set surge thresholds that mean something, build target lists from live signals, route surging accounts into the right sequence, and measure whether any of it moved pipeline.

Why Intent Data Helps Outbound

Cold outreach is a timing game as much as a targeting game. You can have the perfect account and the perfect contact, and still land in the inbox three months before they care. Intent data narrows the window. Instead of emailing 1,000 accounts cold, you email the 80 that are reading about your category this month first.

Bombora is a B2B intent data provider. It aggregates anonymized content consumption signals from a large co-op of publisher websites, then measures when a company's research activity on a given topic spikes above that company's own baseline. That spike is surfaced as a Company Surge signal. When an account "surges" on a topic, it means people at that company are consuming noticeably more content about it than they normally do.

The practical value for outbound is simple. Surging accounts are more likely to reply, more likely to take a meeting, and more likely to already have the problem you solve top of mind. You are not manufacturing demand. You are catching it.

Step 1: Define Your Intent Topics

Before you connect anything, decide what "in-market" actually looks like for your business. Bombora offers thousands of topics. If you subscribe to too many, every account surges on something and the signal becomes noise. If you pick too few, you miss real buyers.

Start with three tiers of topics:

• Core topics: The exact category you sell (for example, "sales intelligence software" or "managed IT services"). These are your strongest buy signals.
• Problem topics: The pain your product removes (for example, "employee onboarding" or "data breach response"). Accounts researching the problem may not know solutions like yours exist yet.
• Adjacent topics: Related initiatives that often precede a purchase (for example, "digital transformation" or "sales hiring"). Weaker signals, useful for early-stage awareness.

Keep the list tight to begin with. Ten to twenty carefully chosen topics beats a hundred loose ones. You can always expand once you see which topics correlate with real replies.

Step 2: Connect Bombora to Your Stack

Bombora is a data layer, not a campaign tool. Its value only shows up when the signal reaches a system that can act on it. Bombora integrates with CRMs, ABM platforms, and advertising platforms, so pick the destination that matches how your team already works.

The common connection points are:

• Your CRM (Salesforce, HubSpot) so surge scores appear directly on the account record your reps already look at.
• Your ABM platform if you run one, so intent feeds audience building and orchestration.
• Your outbound or sequencing tool so surging accounts can be pulled into the right campaign.
• Your ad platform so you can retarget surging accounts with display or LinkedIn ads alongside the outreach.

For most outbound teams, the CRM is the anchor. Get the surge score onto the account record first, because everything downstream (list building, routing, reporting) reads from there.

Step 3: Set Your Surge Thresholds

A surge score is relative to each account's own baseline, so not every flagged account deserves an email. You need a threshold that separates "mildly curious" from "actively researching."

Bombora surfaces surge as a score, typically alongside how far above baseline an account is trending. Set your bar deliberately:

• High bar to start: Only route the strongest surges into live sequences at first. A smaller, hotter list is easier to measure and less likely to burn your sending reputation on lukewarm accounts.
• Combine topic count with score: An account surging on three of your core topics at once is a stronger signal than one surging on a single adjacent topic. Weight accordingly.
• Layer fit on top of intent: Intent without fit is a trap. An account can surge hard and still be the wrong size, wrong industry, or outside your service area. Always filter surge by your ideal customer profile before anyone gets an email.

Write the threshold down as an explicit rule. "Route to sequence when surge is high on a core topic AND the account matches our ICP filters" is a rule a system can enforce. "Email the hot ones" is not.

Step 4: Build Target Account Lists From Company Surge

Once the signal is in your CRM and your threshold is set, building lists becomes mechanical. Create a saved view or dynamic list that captures accounts meeting all your criteria at once.

A strong Company Surge list combines:

• Surge score above your threshold
• Surge on a core or problem topic (not just adjacent)
• Account matches your ICP (size, industry, geography, tech stack if relevant)
• No open opportunity already in flight
• Not already in an active sequence

The output is a rolling list of accounts worth reaching this week. Because surge refreshes on a regular cycle, the list is a living queue rather than a one-time export. New accounts enter as they start researching, and accounts drop off as their surge cools. That rolling nature is exactly what makes intent useful for outbound: it keeps handing you fresh, timely accounts.

Step 5: Route Surging Accounts to Sequences

This is the step that separates teams who bought intent data from teams who use it. The signal is only worth the subscription if a surging account reliably ends up in the right message.

Map each topic bucket to a matching sequence:

• Accounts surging on a core topic get your most direct, solution-forward sequence. They know the category. Lead with a specific outcome.
• Accounts surging on a problem topic get a problem-led sequence. They may not know solutions like yours exist, so open with the pain, not the product.
• Accounts surging on an adjacent topic get a lighter, awareness-first touch, or go into a nurture track rather than a hard outbound push.

The routing should be automatic wherever possible. When a rep has to manually check a report, copy an account, and paste it into a sequence, the process breaks the first busy week. In the systems we run, a qualifying surge triggers enrollment into the matched sequence without anyone touching it, so timing never depends on someone remembering to look.

Step 6: Measure the Impact

Intent data is not free, so treat it like any other input and measure whether it earns its place. The mistake is measuring the wrong thing. Do not judge Bombora on how many accounts surged. Judge it on whether surging accounts converted better than cold ones.

Run a simple comparison. Track the metrics that actually matter for outbound and compare surge-driven outreach against your baseline:

We do not track open rates and never recommend them, because the tracking pixel that measures opens hurts deliverability. Reply rate, positive reply rate, meetings, pipeline, and cost per lead are the honest scoreboard. Typical cold campaigns see low single-digit reply rates, so if your surge list consistently beats your cold baseline on positive replies and meetings, the data is working.

Common Mistakes to Avoid

A few predictable errors kill the ROI on intent data. Watch for these:

• Subscribing to too many topics. Everything surges, nothing stands out. Start narrow.
• Treating surge as a buy signal. It is a research signal. Someone at the account is curious. That is the start of a conversation, not the end of one.
• Skipping the ICP filter. A perfectly surging account that is the wrong fit is a wasted send and a reputation risk.
• Leaving the signal in a report. If surge data lives in a dashboard nobody opens, you paid for a decoration. It has to reach the sequence.
• Never re-testing thresholds. The right bar shifts as you learn. Review which topics and thresholds actually correlate with meetings, and adjust.

Keep in Mind: Signals and Privacy

Two cautions deserve real weight before you build your whole motion on intent.

For the data-sourcing and consent side of outbound, our GDPR cold email compliance guide covers what a compliant, relevance-first message needs. And if you want to see how intent fits into a broader stack, our B2B outbound tool stack breakdown maps where it sits alongside enrichment, sending, and CRM.

Bombora Pricing

Bombora uses custom, contact-sales pricing. It does not publish standard rates, and the cost depends on the topics, data volume, and integrations you need. Anyone quoting you an exact Bombora price from a blog post is guessing. Check with Bombora directly for a current quote, and factor in the real total cost: the data feed plus the tools or people that turn the signal into booked meetings. Data you cannot operationalize is an expensive export.

Ready to Turn Intent Into Booked Meetings?

Buying intent data is the easy part. Wiring it into a system that automatically routes surging accounts to the right sequence, keeps records clean, and reports on pipeline is where most teams stall. We orchestrate intent signals into the outbound engine so timing stops being a manual chore and starts being a built-in advantage, and you keep everything we build.

Book your free pilot →