Sales intelligence tools that live in their own dashboard are sales intelligence tools that get ignored. The research on tool adoption in B2B sales is unambiguous: reps use what is in front of them in their primary workflow, and their primary workflow lives in their CRM and their sequencing tool. Any intelligence that requires a separate login and context switch will be used by the most disciplined 20% of your team and ignored by the other 80%. Integrating sales intelligence into your CRM is not optional — it is a prerequisite for behavioral change at scale.
What to Integrate: The Essential Data Points
Not everything from your sales intelligence platform needs to flow into your CRM. Being selective about what you surface prevents "dashboard paralysis" — the state where so much information is visible on an account record that reps don't know what to act on. The essential data points to push to your CRM account records are:
- Composite intent score (0–100, updated weekly): The single number that summarizes overall buying signal strength. Should be visible on the account record without clicking through to a detail view.
- Score change indicator (trending up/flat/down): More actionable than the score itself. A score that jumped from 45 to 78 in one week is more urgent than a score that has been stable at 82 for two months.
- Primary signal driver: The one-line description of what is driving the intent score. "Job postings: 3 Revenue Ops roles in the last 14 days" is instantly actionable. A number alone is not.
- Recommended next action: Optionally, push a suggested action into a task or activity field. "Schedule outreach by [date] — account is showing peak intent window" closes the loop between signal and action.
Salesforce Integration: Step by Step
For Salesforce, the recommended integration architecture involves four components:
Step 1: Create Custom Fields. Add three custom fields to the Account object: TavMind Score (Number), TavMind Score Trend (Text: "Increasing/Stable/Decreasing"), and TavMind Primary Signal (Long Text Area). These fields will be populated by the TavMind API sync.
Step 2: Configure API Sync. TavMind's Salesforce connector uses OAuth 2.0 for authentication. Once authorized, configure the sync to match TavMind account IDs to Salesforce Account IDs using your preferred matching logic (domain match, company name match, or manual mapping for complex account structures). Set sync frequency to daily for Growth/Enterprise plans.
Step 3: Build Account List Views. Create filtered list views that surface accounts by TavMind score band: 80+ (Immediate Action), 60–79 (Monitor and Sequence), 40–59 (Watch List). These become each SDR's morning prioritization dashboard, without any additional tooling.
Step 4: Configure Automation Rules. Use Salesforce Flow to trigger automated actions when TavMind scores cross defined thresholds: score reaches 80+ for an unworked account → create a task for the owning rep. Score drops below 30 for an open opportunity → create a manager alert. Score rises by 30+ in a single week → flag for immediate outreach.
HubSpot Integration: Step by Step
The HubSpot integration follows the same logical steps with HubSpot-specific implementation details. Custom properties are created on the Company object. The TavMind HubSpot connector uses the HubSpot API to create and update these properties on a daily sync cadence.
The key HubSpot-specific consideration is workflow automation. HubSpot Workflows can trigger rep tasks, lead rotations, and sequence enrollments based on property changes — including TavMind score changes. A workflow that automatically enrolls companies that cross the 80-score threshold into a high-intent outreach sequence is one of the highest-leverage automations a HubSpot-based team can implement.
Measuring Integration Success
After 30 days of live integration, run these validation checks:
- Are high-scoring accounts (80+) being worked at a higher rate than low-scoring accounts? If not, reps are not using the scores.
- Are outreach response rates for high-scoring accounts measurably better than baseline? If not, either the signal quality needs improvement or the personalization is not leveraging the signal context.
- Are score change alerts triggering rep actions in time? Check the average lag between a score crossing the alert threshold and the first rep outreach activity. Target: under 24 hours.