Sales intelligence is the practice of gathering, organizing, and acting on information about target accounts and contacts to improve sales efficiency and conversion rates. Most teams have tools. Fewer have workflows. This handbook builds the workflow layer: how to take the data available from your CRM, intent platforms, and enrichment tools and turn it into repeatable daily and weekly actions for reps.
Sales intelligence is a broad term. For this handbook, it covers four categories of actionable information:
Account-level intelligence: What is happening at the company? Firmographic data (size, industry, funding), technographic data (what tools they use), organizational changes (new hires, departures, reorgs), and financial signals (funding rounds, earnings news, acquisition activity).
Contact-level intelligence: Who are the people involved in a buying decision? Their role, tenure, past employer, LinkedIn activity, and any prior interaction history with your company.
Intent intelligence: What is the company actively researching? Third-party intent signals from keyword research activity and first-party behavioral signals from your own website and product.
Relationship intelligence: What is the current state of your relationship with this account? Past meetings, email exchange history, the content they have engaged with, and any deals previously won or lost.
Each category has different sources, different update frequencies, and different use cases in a sales rep's daily workflow.
The most practical output of a sales intelligence workflow is a brief: a concise summary of the most relevant information about an account that a rep can review before an outreach or meeting.
An effective account intelligence brief covers:
This brief should be available in the CRM on the account record, not in a separate platform. If a rep needs to open three tools to assemble this information before making a call, it will not happen consistently.
Firmographic data (company size, industry, geography):
Source from your CRM enrichment layer (tools like Apollo, Clearbit Reveal, or your ABM platform's enrichment). Update quarterly or when a manual flag indicates something has changed. Firmographic data moves slowly; frequent automated updates waste API credits.
Technographic data (tech stack):
Source from technographic data providers or platforms that scrape job postings and website code. Update quarterly. Technographic data has a decay rate; tools get added and replaced. Flag any technographic signal change (new CRM adoption, departure from a competitor's platform) as a high-value trigger for outreach.
Organizational news (hires, departures, reorgs):
Source from LinkedIn and news monitoring. A VP of Marketing joining a target account is often a high-signal buying trigger: new leaders frequently evaluate and replace tools. Monitor LinkedIn job changes for your Tier 1 accounts weekly. Many intent platforms include news and hiring signals as part of their alert layer.
Financial signals (funding rounds, IPO, acquisition):
Source from Crunchbase, news monitoring, or your CRM enrichment platform. Funding events are particularly valuable: a target account announcing a Series B or Series C is likely to expand headcount, add tools, and increase marketing spend. Flag funding events as immediate outreach triggers.
Intent signals:
Source from your third-party intent platform and your first-party website identification layer. Update daily. Intent signals are the most time-sensitive data in the intelligence stack: a company spiking on your category topics today may not be spiking next week.
Contact and relationship data:
Source from your CRM and email sync. Update in real time as activities are logged. Relationship intelligence is only as good as your CRM hygiene: if calls and emails are not being logged, the intelligence is incomplete.
Data is not actionable until it is formatted for the way reps actually work. Build three rep-facing workflow outputs:
Daily signal digest:
A daily automated report (delivered via email or CRM notification) that shows each rep:
The daily digest should take less than five minutes to review and result in two to three prioritized tasks for the day.
Pre-call research package:
Before any scheduled call or meeting, the rep should have access to a compressed intelligence brief on the account and contact. Build this as a CRM view that automatically populates from the account's intelligence fields. The rep should be able to pull this up in 90 seconds before a call, not spend 20 minutes assembling it from multiple tabs.
Weekly account review queue:
For Tier 1 accounts without recent activity, generate a weekly review prompt: "No activity on [Account Name] in the past 14 days. Last touchpoint: [date, type]. Intent status: [current]. Suggested action: [recommended play based on current signals]."
This prevents valuable accounts from going dark by default and surfacing only when a rep happens to remember them.
A sales intelligence workflow lives in the CRM. If your CRM is not configured to support it, the workflow breaks down at the data layer.
Required account fields:
Required contact fields:
Automation requirements:
Intelligence without action prompts: A CRM full of data that does not tell reps what to do with it produces no behavior change. Every intelligence update should have an associated recommended action.
Too many alerts, not enough signal: Reps tune out notification systems that fire too frequently. Set alert thresholds so that only genuinely significant signals generate notifications. An account visiting your blog post once is not an alert-worthy event. An account visiting your pricing page for the third time in a week is.
Stale data that teams trust anyway: If your CRM shows firmographic data from 18 months ago, reps may be working from outdated information without knowing it. Add data freshness timestamps to all enrichment fields. Flag data older than six months for review.
Intelligence not reaching reps before customer conversations: If a rep enters a call without knowing that the account spiked on intent signals last week, the opportunity to reference that context is lost. Build the pre-call package into the standard meeting workflow, not as an optional step.
Sales intelligence is the operational layer underneath ABM execution. The account tier decisions that define your ABM program rely on intelligence data to be accurate. The outreach plays that your ABM program runs require intelligence context to be personalized.
Build the integration so that intelligence updates automatically affect account status:
This keeps your ABM program responsive to market signals rather than running against a static account list that was defined three months ago.
Workflow design and tooling create the conditions for intelligence use. Culture sustains it. Even the best-designed system will underperform if the team does not consistently apply the intelligence it provides.
Build intelligence use into the sales team's operating rituals:
Pre-call intelligence review as a standard: Make reviewing the account brief before any outreach call a standard practice, not an optional step. This is not about policing rep behavior; it is about making the brief so useful that skipping it is obviously costly.
Intelligence sharing in team meetings: Create a 5-minute slot in weekly sales team meetings for reps to share a signal they acted on and what happened. Positive examples (a rep used a funding signal to time their outreach perfectly and got a meeting) spread intelligence-driven behavior faster than any training.
Recognition for intelligence-driven wins: When a deal closes where the rep clearly used account intelligence to personalize their approach, make that visible in the team. "This deal closed partly because the rep saw a relevant hiring signal and referenced it in the opening email" is a story worth telling.
Intelligence accuracy feedback culture: When reps find errors in the intelligence (wrong tech stack, outdated contact information, stale news), they should feel comfortable flagging it and confident that the flag will result in an improvement. A culture where reps distrust the intelligence tools and work around them defeats the purpose of the workflow.
Manager coaching on intelligence use: Managers reviewing call recordings should note whether reps are using account intelligence in their conversations. Intelligence that was visible in the brief but not used in the call is a coaching opportunity: "I saw the account had this signal last week. How could you have incorporated that into your approach?"
For more on how Abmatic surfaces account intelligence across identification, scoring, and personalization, see a product walkthrough. For strategic context on account tiering, read the account tiering guide.
How do we prioritize which intelligence signals to act on when there are too many?
Use a signal priority hierarchy: first-party signals (pricing page visit, demo request, product trial) always take priority. Second-priority: organizational triggers (funding, executive hire at a Tier 1 account). Third-priority: third-party intent spikes above threshold. Everything else enters a review queue rather than triggering immediate action.
What is the minimum viable sales intelligence setup for a small team?
At minimum: an enrichment integration that populates firmographic and technographic data in the CRM, a first-party website identification layer that surfaces account visits, and a daily digest of new intent signals from your target accounts. This can be assembled from a single ABM platform rather than multiple point solutions.
How do we get reps to actually use the intelligence tools we have invested in?
The workflow must require minimal context switching. If reps need to log into three separate platforms to assemble the intelligence they need, adoption will be low. Bring the intelligence to where reps already work (the CRM) and format it for the specific action the rep needs to take. Then track adoption metrics and coach to the gaps.