HubSpot has put third party buyer intent data directly onto the company record, and it has done so without asking anyone to buy a second product. Company Surge signals, powered by Bombora, entered beta in HubSpot during the week of 17 August 2026, and they arrive inside the standard intent signal tracking that customers already have. For anyone running a B2B revenue function on HubSpot, that is a genuinely good week.
For most of the past decade, intent data lived somewhere else. It sat in a separate platform with a separate login, a separate contract and a separate owner, who exported a weekly spreadsheet that sales looked at once and then quietly stopped opening. The insight was always real. The plumbing was the problem. Moving the signal into the CRM, where the workflows, the scoring model, the lists and the reports already live, removes the single biggest reason intent programmes never quite took hold.
The opportunity here is bigger than it first looks, and the teams that will get the most from it are the ones that decide, before they switch anything on, exactly what a surge is going to change on Monday morning.
What did HubSpot actually ship?
Company Surge is a native HubSpot intent signal, powered by Bombora, that flags when a tracked company’s research activity spikes on topics related to your business. HubSpot proposes up to 12 topics automatically, based on your website and any research intent topics you already track, and you are free to change them. Each signal carries the topic, a research intensity of high, medium, mild or low, the topic category, and the geographic areas where the research is concentrated. Signals appear on the company timeline and in the Signals tab under Buyer Intent, and they are included in the cost of standard intent signal tracking, so no separate Bombora contract is required.
The underlying data comes from Bombora’s B2B Data Co-op, which observes research activity across thousands of business and publisher websites. That is a meaningfully different input from the intent most HubSpot customers already have. First party intent tells you who came to your pricing page. Research intent tells you which organisations are reading about the problem you solve, on properties you do not own, often weeks before they land on your site at all.
The practical effect is that a category of insight that used to sit behind a five figure annual contract and a bespoke integration now behaves like any other field on the company record. It filters lists. It enrols workflows. It feeds company scoring. It shows up in custom reports. Nothing about that is exotic, and that is precisely what makes it useful.
What is buyer intent data, and why does it belong in the CRM?
Buyer intent data measures how actively an organisation is researching a topic, product category or problem, based on the content its employees consume across the web. First party intent covers behaviour on your own properties, such as pricing page visits, document downloads and demo requests. Third party intent, which is what Company Surge provides, covers the research happening everywhere else. It belongs in the CRM because the CRM is where the account record, the deal history, the owner and the automation already sit. A signal that has to be looked up in a second system rarely changes what a seller actually does with their afternoon.
It helps to be precise about what the destination is. HubSpot CRM is the shared customer database at the centre of HubSpot’s platform, used by its Marketing, Sales, Service, Content and Operations Hubs, so a company record updated in one place is the same record everywhere else. When an intent signal lands on that record, marketing, sales, service and operations all inherit it at the same instant, without anyone building a sync.
This is why the delivery mechanism matters as much as the data. Plenty of organisations have bought good intent data and got little from it, not because the signal was wrong, but because acting on it required someone to leave the tool they work in all day. Reducing that friction to zero is a small technical change with an outsized behavioural payoff.
How does research intent improve pipeline velocity?
Pipeline velocity is the rate at which revenue moves through your pipeline, calculated by multiplying the number of open opportunities, the average deal value and the win rate, then dividing by the average sales cycle length in days. Research intent improves it in two specific ways. It lifts win rates, because sellers spend their week on organisations that are already in market rather than on organisations that merely match the profile. And it shortens cycles, because the first conversation starts closer to the question the buyer is already asking. Neither effect requires more activity. Both come from better sequencing of the activity you have.
The gain is easiest to see in industries with long, considered buying cycles. A manufacturer researching configure, price, quote software, or a housing organisation reading about field service scheduling, is signalling a project that will take months to specify and years to run. Reaching that account in the research phase rather than the shortlist phase changes the entire shape of the deal, from who you meet to how much of the requirement you help define.
Territory planning benefits just as directly. Most sales teams allocate effort by firmographics and last year’s revenue, which is a reasonable proxy and a poor predictor. Layering current research activity over that allocation lets a team of eight cover a market that previously needed twelve, and it gives sales leaders a defensible answer when someone asks why a particular account list looks the way it does.
Intent signals give sales and marketing one thing to agree on
The most reliable way to align sales and marketing is to give both functions one shared definition of a good account and one shared trigger for acting on it. Shared revenue targets help. Shared dashboards help. Yet the argument usually restarts at the point of handover, because each side is reading a different source. A native intent signal gives both teams the same evidence at the same moment: marketing sees which accounts to warm, sales sees which accounts to call, and both are looking at the same field on the same record. Agreement gets considerably easier when nobody has to import anything to make their case.
The teams that turn this into results tend to write the play down before the first signal arrives. A high intensity surge on a priority topic triggers a specific sequence: marketing releases a relevant asset to that account, the owner gets a task with a defined response window, and the outreach references the topic rather than the trigger. Nobody tells the prospect that a system flagged them. The seller simply arrives with a more relevant opening.
Writing the play down also settles the question that derails most intent programmes, which is who owns the follow up. Deciding that in advance, in a document that both leaders sign, converts an interesting data feed into an operating routine. It is a half day of work that determines whether the whole thing compounds.
What makes intent data trustworthy enough to act on?
CRM data quality is the degree to which the records in your CRM are accurate, complete, current, consistent and free of duplicates. It matters more for intent data than for almost anything else, because a surge signal has to be matched to a company record to be useful. If the same organisation exists three times under three spellings and two domains, the signal splits across all three and none of them looks urgent. Teams that get strong results from research intent almost always spend a fortnight on account de-duplication and domain mapping first. That work pays for itself immediately, and it improves routing, reporting and attribution at the same time.
Topic selection is the other lever worth taking seriously, and it is more interesting than it sounds. Twelve topics is a real constraint, and the most productive approach is to describe the buyer’s problem rather than your product name. An organisation selling CPQ will usually learn more from topics covering quoting accuracy, product configuration and pricing governance than from the acronym itself, because the people doing the early reading have not yet settled on what to call the solution.
Treat the first quarter as calibration rather than proof. Watch which topics correlate with meetings that actually happen, retire the ones that do not, and let the model tighten. Twelve slots recalibrated every quarter is a far better asset than twelve slots chosen once and left alone, and the recalibration itself teaches you a surprising amount about how your market describes its own problems.
How do you measure the return on an intent programme?
To measure CRM ROI, compare the cost of the platform, the implementation and the internal time it consumes against the incremental revenue and cost savings it produces, then track that comparison over consistent periods. For an intent programme specifically, the cleanest method is a holdout. Route surge flagged accounts to one group of sellers with a defined play, leave a comparable set unflagged for a quarter, and compare meeting rates, opportunity creation and win rates across the two. Because Company Surge sits inside HubSpot reporting, that comparison can be built as a custom report rather than a monthly spreadsheet exercise.
Give it a full quarter before drawing conclusions. Research intent is a leading indicator, and leading indicators need enough cycle time to show up in closed revenue. In the meantime, the honest interim measures are connect rate on surge flagged outreach, the proportion of flagged accounts that convert to a first meeting, and the time between signal and first touch. That last one is the most controllable and the most predictive.
Because the signal is included in existing intent tracking rather than sold separately, the cost side of the calculation is unusually favourable. The investment is mostly attention: choosing topics well, cleaning the account base, and holding the team to a response window. That is a pleasant position to evaluate from, and it means a pilot can be run on its merits rather than on the strength of a business case for new spend.
The Sirocco perspective
We have watched intent data go through several rounds of promise and disappointment, and the pattern has been consistent. The data was rarely the weak link. The weak link was distance: distance between the signal and the record, between the record and the workflow, and between the workflow and the person expected to act. HubSpot has now closed the first of those gaps, which makes the remaining two much easier to close as well.
As an independent CRM partner we work across Salesforce, HubSpot and Microsoft Dynamics 365, and that vantage point is useful here. Native intent inside HubSpot is a strong reason to consolidate around the platform for organisations already invested in it, and it is not, on its own, a reason to move. What it does do is raise the baseline everywhere, because a capability that ships as standard in one platform tends to become an expectation in the others. Clients planning a CRM selection this autumn should certainly ask each vendor what intent data costs, where it lands, and what it can trigger.
Our advice to teams already on HubSpot is refreshingly small in scope. Spend a fortnight tidying company records, choose twelve topics that describe your buyer’s problem, write one page that says what happens when a high intensity signal appears, and set a review date ninety days out. That is a genuinely modest amount of work for a capability that used to require a procurement cycle, and the teams that do it now will be several quarters ahead when everyone else gets around to it.
If you are planning how research intent should fit into your pipeline model, or you want a second view on topic selection and account matching before you switch it on, schedule a consultation with our team.
Get in Touch
If you are working out how Company Surge signals should shape your HubSpot pipeline plays, or you want a second opinion on topic selection and account matching before you turn it on, we are glad to talk it through.
