Buyer intent data becomes useful when it helps the CRM surface the right accounts at the right moment. G2, Bombora, and 6sense each provide a different kind of signal, so the best workflow usually combines them rather than relying on a single source.
Buyer intent data from review sites and intent platforms gives B2B sales teams a signal that transforms cold outreach into timely, contextualised contact: the company you’re calling was actively evaluating your category last week. G2, Bombora, and 6sense are the three most widely integrated intent data sources in sales and marketing tech stacks, and each provides a different type of signal that, when properly routed into CRM, enables a materially different and more effective outbound motion than traditional list-based prospecting. This guide covers how each platform’s intent data works, how to route it into Salesforce and HubSpot, and how to build the workflows that turn intent signals into pipeline.
That matters because intent data is only valuable when it fits the sales motion. If the alerts are noisy or misaligned, the team ends up ignoring them instead of acting on them.
G2, Bombora, and 6sense: Signal Type Comparison
| Platform | Signal Type | Signal Specificity | Ideal Use Case | CRM Integration |
|---|---|---|---|---|
| G2 Buyer Intent | Product-specific: who viewed your G2 profile, compared you to competitors, or read your reviews | Very High – specific to your product | Late-stage outreach to active evaluators | Native Salesforce and HubSpot connectors |
| Bombora Company Surge | Category-level: companies surging on topic clusters (e.g., “CRM software”) | Medium – category intent, not product-specific | Top-of-funnel prospecting to in-market accounts | Native Salesforce connector; HubSpot via Zapier or native |
| 6sense | AI-modelled buying stage combining first, second, and third-party signals | High – buying stage model contextualises signals | Account prioritisation and sales-marketing coordination | Native Salesforce and HubSpot; deep Outreach and Salesloft integration |
G2 Buyer Intent in CRM
G2’s Buyer Intent identifies when companies are actively evaluating products in your category on G2. The platform tracks: profile views (companies viewing your G2 listing), comparison activity (companies comparing you to specific competitors), category browsing (companies viewing products in your G2 category), and competitive activity (companies viewing competitor profiles without viewing yours). G2 identifies the company visiting these pages using IP resolution, firmographic enrichment, and email domain matching.
Integration with Salesforce: G2 integrates directly with Salesforce Account records. When G2 detects intent activity from a company, it pushes the intent signal – activity type, frequency score, and competitor names viewed – to the corresponding Salesforce Account’s G2 intent fields. If the Account doesn’t exist in Salesforce, G2 can create it automatically (configurable). Create a Salesforce report filtered to “G2 Intent Score > 0 – Last 7 Days” and “Account Owner = SDR Queue” for daily SDR prospecting.
Integration with HubSpot: G2’s HubSpot integration pushes intent data to HubSpot Company records. This enables HubSpot workflow automation: when a company’s G2 intent score exceeds a threshold, automatically enroll associated contacts in a sales sequence and create a task for the account owner. The trigger point – what G2 score triggers outreach – should be calibrated to your team’s capacity; too low a threshold creates too many low-quality signals for reps to act on.
Bombora Company Surge in CRM
Bombora aggregates content consumption data from 5,000+ B2B publisher sites. When an account’s employees consume significantly more content about a topic cluster than the historical baseline for that account, Bombora flags the account as “surging” on that topic. The surge score (0-100) indicates the intensity of the signal relative to baseline – a score of 80+ is strong; 60-79 is moderate.
Topic configuration: Before connecting Bombora to your CRM, configure your intent topics – the keyword clusters that indicate a prospect is researching your category. For a CRM vendor, relevant Bombora topics might include: “Customer Relationship Management,” “Sales Force Automation,” “CRM Software,” “Sales Pipeline Management.” Narrow your topics to those with the strongest signal-to-noise ratio for your specific market.
Salesforce integration: Bombora pushes surge scores to custom fields on Salesforce Account records. Common field setup: Bombora Surge Score (number), Bombora Surge Topics (text, comma-separated topic names), Bombora Last Surge Date. Create a Salesforce account list view filtered to accounts surging on your configured topics above a score threshold, within your ICP firmographic criteria, and without an open opportunity – this becomes the SDR prospecting list updated automatically by Bombora’s daily sync.
6sense in CRM
6sense differs from G2 and Bombora in that it synthesises multiple intent signals into a predicted buying stage model rather than providing raw signals. 6sense’s stages – Awareness, Consideration, Decision, Purchase – represent where 6sense’s AI model believes an account is in its buying journey. Decision-stage accounts are, by definition, the highest-priority outreach targets.
Salesforce integration depth: 6sense provides the most comprehensive Salesforce integration of the three platforms. Beyond pushing account stage and intent data to Account records, 6sense integrates with Salesforce Campaign objects (automatically adding high-priority accounts to campaigns), Salesforce Opportunity records (surfacing buying intent signals on open deals), and Salesforce reports (providing 6sense-native reporting dashboards within Salesforce). 6sense’s integration with Outreach and Salesloft allows sequence enrollment to be triggered directly from 6sense account stage changes.
Building the Intent-to-Pipeline Workflow
The highest-converting intent workflow combines all three data sources with a clear prioritisation logic:
- Tier 1 (immediate outreach): G2 intent signal + company within ICP + no active opportunity in CRM. These accounts are actively evaluating your category on G2 – outreach within 24 hours of signal receipt.
- Tier 2 (prioritised prospecting): 6sense Decision-stage account + Bombora surge above threshold + no existing customer. Multi-touch sequence beginning within 48 hours.
- Tier 3 (nurture queue): Bombora surge above threshold + 6sense Consideration stage + no prior engagement. Add to marketing nurture sequence with SDR follow-up after 2 marketing touches.
“G2 intent data is surfacing companies that don’t fit our market at all”
G2’s IP resolution for visitor identification has a meaningful error rate – companies identified may include IP addresses from corporate VPNs, shared office buildings, or data centres that don’t reflect the actual visitor. Additionally, G2 category browsing signals are broader than profile visit signals and include many companies doing casual research rather than active evaluation. Fix: weight G2 signals by specificity. Profile views and competitor comparison activity (where someone compared you directly to a competitor) are high-confidence signals. Category browsing signals are low-confidence and should be filtered out or weighted lower in your CRM workflow. Apply ICP criteria to every G2 signal before it surfaces to sales: company size, industry, and geography must match your ICP or the signal is suppressed.
“Bombora is sending hundreds of intent alerts per week – our SDR team can’t keep up”
High-volume Bombora intent alerts without prioritisation is a workflow design problem, not a data problem. The most common cause: too many intent topics configured, too low a surge score threshold, or no ICP filtering applied before signals surface to sales. Fix: (1) Reduce intent topics to the 5-8 with highest signal-to-noise ratio for your product. (2) Raise the surge score threshold – start at 70+ rather than 50+. (3) Apply strict ICP filtering: only accounts within your target employee count range, target industries, and target geographies should surface to sales. (4) Implement the tier prioritisation model described above – not all intent signals require immediate sales outreach. Bombora signals alone (without G2 or 6sense validation) are best treated as marketing qualification signals that trigger nurture campaigns rather than direct SDR outreach.
Sources
G2, Buyer Intent Platform and Salesforce/HubSpot Integration Documentation (2026)
Bombora, Company Surge Intent Data and CRM Integration Guide (2026)
6sense, Account Intelligence and Revenue AI Platform Documentation (2025)
Forrester, B2B Intent Data Use Cases and Integration Best Practices (2025)
The integration should make the team faster to act, not just give them another dashboard. If the data is not showing up in a way that changes outreach decisions, the setup needs to be simplified.
Advanced Strategies and Common Pitfalls in CRM and Buyer Intent
Step-by-Step Fix: Build Your Foundation Before Scaling
Successful implementation of crm and buyer intent follows a consistent pattern: start with a clearly defined use case for a single team, measure the baseline, implement incrementally, and scale only after achieving measurable results in the pilot. Avoid configuring everything simultaneously. A phased approach with 30-day review cycles catches configuration errors before they spread.
Measuring Success: KPIs and Review Cadence
Establish three to five quantifiable success metrics before launch: adoption rate, data completeness score, and process efficiency measured as time saved per rep per week. Review these metrics monthly and tie configuration decisions to data rather than opinion.
What are the key benefits of CRM and Buyer Intent?
The primary benefits include improved operational efficiency, better data visibility for management decision-making, and more consistent customer-facing processes. Organisations that implement structured approaches report average productivity improvements of 20 to 35 percent, though results vary based on implementation quality and user adoption levels.
How long does implementation typically take?
Simple configurations for small teams can be live in two to four weeks. Mid-complexity implementations for 20 to 100 users typically take 60 to 90 days. Enterprise-scale projects with custom integrations and data migrations usually require four to nine months from kickoff to full production deployment.
What is the most common reason implementations fail?
Implementations fail most often due to insufficient user adoption rather than technical problems. Systems are configured correctly but teams revert to old habits because training was insufficient, workflows were not simplified, or leadership did not reinforce usage. Executive sponsorship and simplicity of design are the two highest-leverage success factors.
How do you calculate ROI from this type of investment?
Calculate ROI by comparing costs against measurable gains: hours saved per week multiplied by average hourly cost, pipeline increase attributable to improved process, and reduction in revenue lost to poor follow-up. Most organisations targeting a 12-month positive ROI need to demonstrate at least three dollars in measurable value for every one dollar of cost.
Common Problems and Fixes
Common Implementation Challenges to Anticipate
Organisations working on crm and buyer intent frequently encounter three recurring obstacles: inadequate stakeholder alignment during planning, underestimated data migration complexity, and insufficient end-user training budget. Addressing all three before go-live dramatically improves adoption rates and time-to-value. Build a project team with representatives from sales, marketing, and IT rather than delegating entirely to one function.