Lead enrichment adds fields to a record. Sales intelligence provides data and signals that help sellers understand accounts and contacts. Prospect research uses those inputs, plus direct investigation and judgment, to answer a decision: should this company receive sales time, why, who should be contacted, and what should the first conversation be about?
Why these categories get confused
Modern sales tools increasingly overlap. A contact database may add enrichment, intent and AI research. A CRM may add prospecting agents. A research workflow may use contact data, public filings, professional profiles and website signals. As product boundaries blur, marketers often use sales intelligence, enrichment, prospecting and research as if they mean the same thing.
For a small B2B seller, the labels matter less than the job each activity performs. If you know the job, you can choose tools more intelligently and avoid paying for a large data platform when your real problem is deciding which accounts deserve attention.
The four jobs in plain language
Side-by-side comparison
| Job | Primary question | Typical inputs | Typical output |
|---|---|---|---|
| Lead generation | Who could fit? | Industry, location, size, title, filters | List of accounts or contacts |
| Enrichment | What fields are missing or stale? | Existing CRM/list records | Company/contact attributes |
| Sales intelligence | What data or signals can help us sell? | Contact data, professional networks, intent, news, relationships | Insights and prioritization inputs |
| Prospect research | Should we contact this company, why, who and with what context? | Public sources, intelligence, enrichment, seller's offer, human judgment | Proceed/hold/reject decision and prospect brief |
What enrichment is good at
Enrichment is valuable when the problem is incomplete data. A company name can be enriched with industry, employee range, domain or location. A contact record can be updated with current title or other verified fields depending on the provider.
This can save manual lookup and improve segmentation. It is especially useful for keeping CRM records usable at scale.
But enriched fields do not automatically answer why the company should receive outreach. Knowing that a business has 80 employees, uses a particular CRM and operates in Texas can improve fit assessment. It does not prove a current problem, buying priority or relevant owner.
What sales intelligence is good at
Sales intelligence broadens the context. LinkedIn Sales Navigator, for example, provides account and lead research features, title and seniority filters, professional-network information, job changes and account alerts. HubSpot now combines company data, intent signals and prospecting features in its sales products.
A sales-intelligence platform can therefore surface valuable facts and events before a seller researches them manually. That does not eliminate interpretation. A funding event, job change or intent spike still needs to be assessed against account fit and the seller's actual offer.
What prospect research adds
Prospect research is the reasoning layer. It asks questions that a data field cannot answer by itself:
- What has changed at this company?
- What observable condition might create a problem we solve?
- How strong is the evidence?
- What is fact and what is inference?
- Which function is likely to own the issue?
- Who currently holds the relevant role?
- Is there a suitable contact route?
- What should the first conversation validate?
- Is the account ready for outreach, still unclear or not worth the time?
The research can use enrichment and intelligence as inputs. It should not confuse the existence of those inputs with a completed decision.
Example: the same company through four lenses
Imagine a web automation consultant is evaluating a regional healthcare provider.
Lead generation output
Healthcare provider, 10 locations, target geography, estimated employee range. The account enters the list.
Enrichment output
Company domain, industry classification, headquarters, current CRM field, contact records and job titles are added.
Sales-intelligence output
A new operations executive recently joined. The company is hiring front-desk roles and has announced another location. Several relevant people are identified.
Prospect-research output
The researcher checks the company's booking and contact flow, confirms the expansion announcement, reviews hiring responsibilities and recent customer feedback, and concludes:
The earlier stages supplied useful data. The last stage turned it into a decision and a conversation.
Which one do you actually need?
| If your problem is... | Start with... |
|---|---|
| "We don't have enough target companies." | Lead generation / account discovery |
| "Our CRM records are incomplete." | Enrichment |
| "We need account signals, contacts and relationship context at scale." | Sales intelligence |
| "We have targets but reps waste time deciding whether and how to approach them." | Prospect research |
| "We need all of these at enterprise scale." | A combined stack may be appropriate |
Many teams need more than one category. The mistake is assuming that a broad platform automatically solves the specific research decision.
Why the distinction matters more for consultants and small teams
A large sales organization may justify a wide data platform because thousands of records need enrichment, scoring and orchestration. An independent consultant may only need to research 20 high-value companies deeply enough to choose the five worth contacting.
For that seller, buying more data can make the problem worse. A list of 5,000 contacts creates more possible activity without improving confidence in which account deserves the next hour. A research-first workflow is intentionally narrower: fewer accounts, more context, clearer decisions.
Where AI fits across these categories
AI now appears in all four jobs. It can generate lists, enrich or normalize records, summarize intelligence and synthesize research. HubSpot's current AI sales prospecting materials describe lead identification, contact enrichment and outreach personalization as distinct stages. That reinforces the idea that the word AI does not collapse the underlying jobs into one.
In prospect research, AI is most useful when it accelerates discovery and synthesis while the evidence remains inspectable. An AI paragraph with no source should not be treated as equivalent to verified intelligence.
Intent and signals are inputs, not the final verdict
Intent platforms can provide valuable evidence that an account is researching a topic or engaging with the seller. Trigger events can show timing. Neither one by itself answers every qualification question.
A high-intent account that is commercially outside your target market may still be poor fit. A perfect-fit account with no current trigger may remain a valuable long-term target. Prospect research combines those dimensions instead of forcing all account quality into one score.
A practical small-team architecture
A simple workflow can be:
- Discovery source: directory, referral, CRM, LinkedIn, Google Maps, event list or manual search.
- Optional enrichment: fill core company and contact fields where useful.
- Research: website, public sources, changes, evidence, decision-maker and contact route.
- Review: proceed, hold or reject.
- Brief: concise context for first outreach.
- Execution: email, call, CRM or sales-engagement tool.
- Feedback: record what the conversation confirmed or disproved.
This is also where Noustiq Pro is positioned: between discovery and sales execution, rather than trying to replace every database, CRM, dialer or outreach tool.
Questions to ask before buying another sales tool
- Is our bottleneck lack of companies, lack of data or lack of judgment?
- How many accounts do we actually need to research each week?
- What does a salesperson currently do after receiving a raw lead?
- Which research is duplicated by multiple people?
- Do we know why each account reaches outreach?
- Can we inspect the evidence behind important findings?
- Do we need enterprise-scale data, or a smaller decision workflow?
- Where should the final researched brief go next?
Answering those questions usually produces a more useful software decision than starting with a feature checklist.
Four different jobs that are often sold under one label
The easiest way to separate these categories is by the decision each one supports.
| Category | Primary job | Typical output | Core question |
|---|---|---|---|
| Lead enrichment | Add or normalize fields | Industry, size, title, domain, contact data | What data is missing from this record? |
| Sales intelligence | Provide account/contact context | Org changes, relationships, news, people, company insights | What should the seller know about this account? |
| Intent data | Surface behavior suggesting research/interest | Topic surge, site visits, category interest, engagement | Which accounts appear active around this problem/category? |
| Prospect research | Turn evidence into an outreach decision | Fit, reason to contact, likely owner, evidence brief, unknowns | Should we spend sales time here, why, and how? |
Products can span multiple jobs. LinkedIn Sales Navigator combines people data, account insights, relationship intelligence and buyer-intent features. HubSpot combines CRM records, engagement and buying signals. The distinction is therefore about workflow, not vendor taxonomy.
Lead enrichment: useful plumbing, not a qualification verdict
Enrichment is valuable when your CRM record is incomplete or inconsistent. It can append company domain, industry, employee count, location, role, social profile or contact attributes depending on the provider. It can also normalize values so segmentation and routing work.
The failure mode is treating a completed row as a researched account. “150 employees, healthcare, United States, VP Operations identified” can satisfy a list filter and still provide no reason to contact the company. Enrichment answers who/what is this record? better than why should we reach out now?
Sales intelligence: context at account scale
Sales intelligence platforms can surface company news, headcount trends, job changes, relationships and account insights. LinkedIn's Account Pages, for example, expose company summaries, people, news and employee insights; its Relationship Map is designed to organize buying-committee stakeholders. This reduces the cost of collecting context across many accounts.
The failure mode is context accumulation without a decision rule. A seller can see ten alerts and still not know which one matters to the offer. Intelligence becomes valuable when the workflow translates context into relevance, ownership and next action.
Intent data: behavioral evidence with important boundaries
Intent comes in several forms. First-party intent can include known visits, form submissions, content engagement or product usage on properties you control. Third-party intent can aggregate research activity from external publisher or data networks. HubSpot's 2026 Company Surge documentation, powered by Bombora, describes detecting spikes in tracked-company research activity around topics. LinkedIn Sales Navigator includes buyer intent and category interest signals.
Intent is powerful because it can improve timing. It is not magic. A company can research a topic for competitive analysis, investor diligence, academic reasons, implementation already underway or a project that excludes your solution. Intent should raise priority and shape research; it should not skip fit, ownership or qualification.
Prospect research: the synthesis layer
Prospect research asks the questions the other layers cannot answer alone:
- Does the company fit the market we can serve?
- What observed evidence creates a defensible reason to contact?
- Is the evidence current and material?
- What is fact and what is inference?
- Who likely owns the issue?
- What negative evidence could invalidate the opportunity?
- What should the first conversation validate?
It can consume enrichment, intelligence and intent data, but it can also work from public sources alone. The defining feature is not the input. It is the output: a decision-ready account brief.
How the four layers fit into one prospecting stack
- Discovery.
Find candidate companies through directories, search, maps, lists, inbound activity, referrals or data providers.
- Enrichment.
Normalize identity and append fields required for segmentation, routing or research.
- Intelligence and signals.
Collect current people, relationships, news, hiring, intent and account changes.
- Prospect research.
Evaluate fit, evidence, materiality, ownership and unknowns.
- Qualification.
Proceed, hold or reject.
- Outreach preparation.
Translate the selected evidence into a concise hypothesis and question.
Skipping layers can be reasonable for small accounts. A local business lead may need no paid enrichment at all if the website, Business Profile and public contact route are sufficient. A global enterprise account may justify richer intelligence and buying-committee mapping.
Choose tools by bottleneck, not feature count
| Your bottleneck | Likely priority | What to avoid |
|---|---|---|
| CRM records missing firmographic fields | Enrichment | Buying an intelligence suite you will not use |
| Reps cannot see company changes or stakeholders | Sales intelligence | Adding more static lists |
| Too many good-fit accounts, poor timing | Intent/signals | Treating every fit account equally |
| Reps contact irrelevant accounts despite lots of data | Prospect research/qualification | Appending more fields without a decision framework |
| Research is slow and inconsistent | Research workflow + selective automation | Fully automating unsupported conclusions |
| Wrong people are contacted | Ownership/buying-committee mapping | Title-only contact selection |
Data quality is different from evidence quality
A contact record can be perfectly accurate and commercially irrelevant. Conversely, a strong business signal can be real while the contact attached to it is stale. Track quality separately:
- Identity accuracy: is this the correct company/person?
- Freshness: how recently was the field verified?
- Source provenance: where did it come from?
- Evidence relevance: does it connect to the offer?
- Inference confidence: how much interpretation was required?
This separation is particularly important when AI summarizes enriched datasets. A polished summary can make weak or stale fields look authoritative.
A lean stack for a small agency or consultant
You do not need every enterprise data category on day one. A practical low-cost workflow can be:
- Discover companies through search, Maps, directories or industry sources.
- Use the official website and Business Profile to verify identity and basic fit.
- Use LinkedIn/company pages for current roles and changes.
- Use registries/filings when corporate verification matters.
- Record one or two relevant signals with source and date.
- Identify the likely owner.
- Find an appropriate business contact route.
- Proceed only when the evidence supports a reason to contact.
Paid enrichment becomes valuable when volume makes manual identity/contact normalization expensive. Intent becomes valuable when you have enough good-fit accounts that timing is the bottleneck. Intelligence becomes valuable when account complexity and relationship context justify it.
An enterprise-style architecture
At larger scale, the layers can become a data pipeline:
- CRM/account master;
- firmographic/technographic enrichment;
- intent and engagement events;
- relationship and people graph;
- news/hiring/filing signals;
- research-agent summaries with citations;
- human or policy-based qualification;
- routing and sequencing;
- outcome feedback for model calibration.
The governance challenge is preserving provenance as data flows through the stack. Each material claim should retain enough source context that a human can inspect it. Otherwise “the model says high intent” becomes an opaque decision with no auditable basis.
Where AI fits—and where it should not be trusted alone
AI is useful for extraction, deduplication, summarization, source comparison, classification and drafting a research brief. It is weaker when asked to infer unobservable facts such as budget, internal authority, private technology, hidden pain or purchasing timelines. A safe AI research record contains separate fields for observed, inferred and unknown.
Google's people-first content guidance also offers a useful parallel for research operations: automation should add value rather than mass-produce summaries of what already exists. In sales research, the equivalent is to use AI to reduce collection cost while keeping human commercial judgment and source verification visible.
Three examples showing why the categories matter
Example 1: enriched but not researched
A database provides 500 HVAC companies with owner names, emails, employee count and location. This is enriched lead data. Without current evidence of a relevant problem or opportunity, the list is not yet prospect research.
Example 2: high intent but poor fit
An enterprise account shows repeated research intent around CRM automation. Your consultancy serves only businesses under 100 employees. Intent should not override delivery fit. Reject or route elsewhere.
Example 3: public research without paid intent
A regional clinic group opens three locations, hires scheduling coordinators and publishes inconsistent booking flows. No intent platform is required to justify deeper research. The public evidence creates a plausible timing and ownership question.
Current source note
HubSpot's 2026 buying-signals and Company Surge documentation shows how CRM platforms increasingly incorporate intent and company events. LinkedIn Sales Navigator's current Account Pages, buyer-intent materials and Relationship Map show how sales intelligence blends account data, people, relationships and signals. These examples demonstrate overlap between product categories; the four-job framework here is intended to help buyers select a workflow based on the decision they need to improve.
Advanced field manual: how to quality-control prospect data-stack design
Long-form research is only useful when it improves a decision. The final pass should therefore test whether each data layer is reproducible, current, material and connected to clear separation of enrichment, intelligence, intent and research. The standard is not “did we find a lot of information?” but “could another researcher follow the source trail, understand the reasoning and reach a similar proceed/hold/reject decision?”
A recurring failure mode in this area is that more fields or a larger database automatically creates better prospecting. Avoid that by forcing every important conclusion through a verification question and a counter-hypothesis. If the alternative explanation is equally plausible, lower confidence and turn the uncertainty into a discovery question instead of hiding it.
12 audit questions before the record is sales-ready
- Audit 1: confirm that enrichment fields are separated from research conclusions. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 2: confirm that sales intelligence is treated as a context layer rather than proof. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 3: confirm that intent data is used for prioritization not certainty. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 4: confirm that research preserves source lineage. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 5: confirm that contact verification is not used as a relevance score. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 6: confirm that company identity resolution happens before enrichment. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 7: confirm that field freshness requirements differ by data type. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 8: confirm that AI-generated summaries link back to underlying evidence. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 9: confirm that private CRM engagement is labeled separately from public evidence. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 10: confirm that the team defines which fields actually change a sales decision. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 11: confirm that vendor overlap and duplicate data are measured. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
- Audit 12: confirm that manual review is reserved for ambiguous/high-value accounts. Record the exact evidence that supports this check, the date it was reviewed, and what would falsify the current interpretation. If the answer depends on private information, label it “requires discovery” rather than filling the gap with an estimate. This is especially important when the finding changes who gets contacted or how the opportunity is described.
Counter-hypothesis discipline
For every strong data layer, write one credible alternative explanation. This is not academic caution; it prevents outreach from sounding accusatory or naive. The researcher should be able to answer three questions: what is directly observed, what does it possibly mean, and what evidence would show that the interpretation is wrong? When the counter-hypothesis wins, downgrade or remove the item. A clean rejection is better than a personalized message built on a false premise.
Use calibrated language in the final brief. “Observed” describes a source-backed fact. “Inferred” describes the commercial interpretation. “Verified” should be reserved for a field that has actually been confirmed by a reliable source or human check. “Unknown” is allowed. This vocabulary makes the research usable by sales without pretending uncertainty has disappeared.
Ten edge cases that should change the decision
Edge case 1: two vendors disagreeing on employee count
Treat this as a scope question, not automatic positive evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 2: verified email for an irrelevant contact
Ask whether the condition is intentional or temporary before making a recommendation. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 3: intent spike at a company outside ICP
Lower confidence until the current state can be confirmed from a stronger or more recent source. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 4: enrichment record for a subsidiary mapped to parent
Check whether the apparent opportunity belongs to another team, vendor or buying authority. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 5: contact database showing former employee
Do not let a compelling narrative override contradictory evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 6: AI summary based on stale source pages
Treat this as a scope question, not automatic positive evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 7: company news duplicated by several aggregators
Ask whether the condition is intentional or temporary before making a recommendation. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 8: CRM engagement from an old opportunity
Lower confidence until the current state can be confirmed from a stronger or more recent source. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 9: anonymous visitor intent with uncertain account match
Check whether the apparent opportunity belongs to another team, vendor or buying authority. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Edge case 10: small team paying for enterprise intelligence it never operationalizes
Do not let a compelling narrative override contradictory evidence. Revisit fit, timing, ownership and materiality independently. Then decide whether the record should proceed, remain on hold, be routed to a different owner, or be rejected. If outreach still makes sense, phrase the observation as a question that gives the recipient an easy way to correct the research.
Research handoff standard
Before a salesperson sees the record, compress the research into a small brief: company and source-verified identity; why the account fits; the strongest current evidence; the interpretation and alternative explanation; likely problem owner; what is still unknown; the recommended first question; contact-route status; and the next review date. Keep the raw sources attached but do not force the salesperson to read a 5,000-word article or a 40-field crawl output to understand why the account matters.
For high-value accounts, add a second-source check and a buying-group view. For lower-value accounts, reduce research depth but keep the same evidence rules. This makes the method economical: rigor stays constant while the amount of work scales with expected value.
How to learn from outcomes
After enough outreach, compare research fields with actual conversation outcomes. Which evidence classes most often led to useful discovery? Which were frequently corrected by prospects? Which roles were mapped accurately? Which findings became stale before use? Update the research template from those results. A methodology that never learns from false positives becomes a content exercise rather than a sales system.
Do not optimize only for replies. A sensational claim can produce replies while damaging trust. Better outcome measures include accepted meetings, confirmed problem ownership, opportunity creation, stage progression, data correction rate and the percentage of researched accounts sales considers genuinely relevant. Those metrics keep prospect data-stack design tied to commercial quality rather than volume.
Practical research worksheet for prospect data-stack design
Use this worksheet when the initial research is promising but not yet strong enough for outreach. It deliberately slows the final decision long enough to check source quality, counter-evidence and ownership. Delete rows that do not apply rather than filling them with guesses.
| # | Check | Evidence standard | Decision test |
|---|---|---|---|
| 1 | Enrichment fields are separated from research conclusions | Capture the current source and retrieval date, then state only what the source directly supports. Note any conflicting or weaker source separately. | Write the most plausible alternative explanation and the one question that would confirm or reject the interpretation. Route the question to the likely functional owner rather than the most senior visible person. |
| 2 | Sales intelligence is treated as a context layer rather than proof | Capture the current source and retrieval date, then state only what the source directly supports. Note any conflicting or weaker source separately. | Write the most plausible alternative explanation and the one question that would confirm or reject the interpretation. Route the question to the likely functional owner rather than the most senior visible person. |
| 3 | Intent data is used for prioritization not certainty | Capture the current source and retrieval date, then state only what the source directly supports. Note any conflicting or weaker source separately. | Write the most plausible alternative explanation and the one question that would confirm or reject the interpretation. Route the question to the likely functional owner rather than the most senior visible person. |
| 4 | Research preserves source lineage | Capture the current source and retrieval date, then state only what the source directly supports. Note any conflicting or weaker source separately. | Write the most plausible alternative explanation and the one question that would confirm or reject the interpretation. Route the question to the likely functional owner rather than the most senior visible person. |
| 5 | Contact verification is not used as a relevance score | Capture the current source and retrieval date, then state only what the source directly supports. Note any conflicting or weaker source separately. | Write the most plausible alternative explanation and the one question that would confirm or reject the interpretation. Route the question to the likely functional owner rather than the most senior visible person. |
| 6 | Company identity resolution happens before enrichment | Capture the current source and retrieval date, then state only what the source directly supports. Note any conflicting or weaker source separately. | Write the most plausible alternative explanation and the one question that would confirm or reject the interpretation. Route the question to the likely functional owner rather than the most senior visible person. |
At the end, write a one-sentence decision: Proceed when fit and evidence justify a specific conversation; Hold when the account fits but timing/evidence is weak; Reject when the service, evidence, authority or compliance conditions do not support outreach. The worksheet is complete only when the decision can be defended without reference to a proprietary score.
Sources and further reading
These sources were reviewed on 26 Aug 2026. They support the external facts, legal guidance and platform-specific details referenced in this article. Noustiq's frameworks, examples and decision rules are editorial synthesis unless a source is explicitly named.
- LinkedIn Sales Navigator: How to Use Sales Navigator
- HubSpot: AI Sales Prospecting
- HubSpot: Use intent signals
- HubSpot: Personalization in AI prospecting