Company Buying Intent Is Not the Same as a Contact Wanting a Sales Call
TL;DR: A company-level signal identifies activity associated with an account, not the identity, preferences, or purchase authority of a particular employee. Use it to choose which account to research. Then verify the account match, CRM relationship, relevant role, and person-level engagement before deciding how direct the outreach should be.
Signal-based selling is useful because it helps teams decide where to investigate first. The mistake is treating a company-level observation as a personal invitation. If a website visit resolves to an account, the observation is about that account. It does not establish who visited, why they visited, whether they represent a buying group, or whether a named person wants a sales call.
Our Signals and Intent product brings together first-party engagement, third-party data, and AI-derived signals. Those inputs are not interchangeable. A public hiring announcement, account-level web activity, and an email reply have different subjects and different levels of attribution. Treat each according to what its underlying record can support.
Separate observation, identity, relevance, and permission
A careful outbound decision has four gates. First, identify the observed event and its source. Second, determine whether it belongs to a company, person, or another entity. Third, assess whether a real person’s role relates to the problem. Fourth, check contact permissions, exclusions, and existing ownership. Passing one gate does not imply the others.
| Evidence level | What it supports | What it does not support | Appropriate next action |
|---|---|---|---|
| Account-level activity | This company may be worth investigating | A named contact took the action | Check fit, CRM status, and relevant roles |
| Verified person-level activity | This person performed a recorded action | They have budget or buying authority | Review the action and conversation context |
| Direct response | This person communicated a preference or question | All colleagues share that preference | Assign the response to the right owner |
| Confirmed project and owner | A concrete evaluation may be underway | Every signal is attributable to that project | Coordinate next steps with the owner |
This ladder is an editorial decision aid, not a vendor score. It does not imply that any platform resolves every visitor to a person. Our Turn Website Visitors Into Outbound use case distinguishes the company associated with site activity from the role-based contact selected for follow-up. The sample accounts and metrics on that page are illustrative, not a verified customer result.
Read the event at the correct entity level
A domain match can join multiple employees, shared networks, subsidiaries, and locations under one account. A product-usage signal can represent one user, a team, or an account depending on how the event was instrumented. A job posting describes an organization’s hiring activity, not necessarily the priorities of the employee you intend to contact. Before writing copy, ask what entity the source record actually names.
- Company record: Check legal name, domain, parent relationship, and whether the signal belongs to the target unit
- Event record: Retain the raw event, its date, source, and any confidence or resolution limits
- Person record: Verify current role and that the person owns or influences the problem being discussed
- Relationship record: Check customer status, open opportunities, existing conversation, suppression, and account owner
- Message record: Mark each statement as observed, inferred, or proposed, and remove unsupported personalization
Data quality matters because a correct event attached to the wrong entity becomes a wrong outreach decision. The UK Government Data Quality Framework is not a sales-specific standard, but its dimensions of accuracy, completeness, and consistency provide a useful way to inspect matching and ownership records. An unknown person match should remain unknown; an empty CRM field should not be silently interpreted as “no existing relationship.”
Write to the problem, not to an invented visit
When you have account-level evidence only, write a message that opens a relevant question without claiming private knowledge of the recipient. “I saw you visited our pricing page” is inappropriate if the system identified only a company. “Teams evaluating this workflow often need to reconcile CRM ownership with site activity; is that relevant to your team?” is a question rather than an assertion about the person. Even this should be sent only after contact and eligibility checks.
If the evidence is a public hiring post, name the verified hiring initiative but do not infer budget, urgency, or system failure. If it is a named person’s direct reply, respond to that person’s actual words rather than an account-level script. If an account is already in an active evaluation, coordinate with the opportunity owner before launching a new outbound sequence. Our Salesforce integration guide covers how mapped CRM context can inform exclusions and Plays, while keeping read access, write settings, and field permissions as separate controls.
Choose a contact by role, then verify the handoff
The best contact is not necessarily the person behind the signal. Select a role that plausibly owns the problem, verify the person currently holds it, and check whether another teammate already has an active relationship. A signal can raise an account’s research priority while the contact selection remains independent. For parent companies and subsidiaries, preserve the event’s original business unit; outreach to the parent may be irrelevant or misleading if a subsidiary generated the activity.
Make the handoff explainable in one record: source, observed entity, reason the company fits, reason the person fits, uncertainty, current owner, and recommended action. The receiving rep should be able to disagree without reconstructing the entire research trail. If the source cannot be reopened, if the account match is disputed, or if the recipient’s role is stale, pause the action until the ambiguity is resolved.
Use a proportional outreach policy
A signal alone may justify research or a low-pressure question. A direct person-level request can justify a specific response. The level of message specificity should not exceed the level of evidence. This rule protects both relevance and trust: it prevents teams from presenting a probabilistic account match as a fact about a human being.
| Available evidence | Do now | Do not say |
|---|---|---|
| Company-level site activity only | Research account fit and identify a relevant role | You personally viewed our site |
| Public company event | Check source date and business-unit match | Your team now has budget or urgency |
| Named person engagement | Review the actual action and current relationship | Your whole company is evaluating |
| Direct reply with request | Assign owner and answer the request | Assume a meeting is desired unless requested |
The policy is intentionally conservative. A CRM record may show a customer or open opportunity that makes new prospecting inappropriate. A person-level reply may also be an opt-out, referral, or request for later timing. Our Task Management supports reply classification and a shared inbox; your team must still decide what each classification means for its playbook and verify that the intended follow-up was actually applied.
Avoid five signal-to-person errors
- Writing as though a named employee personally visited a page when only the account was resolved
- Turning a hiring announcement into an unsupported claim about budget or technology failure
- Ignoring subsidiaries or shared domains when assigning the event to an account
- Contacting someone already in an active opportunity without coordinating with the owner
- Treating a direct objection, referral, or opt-out as another generic intent signal
Glossary
- Account-level signal: An observation associated with an organization, not necessarily a known person
- Person-level signal: An action attributed to an identified individual with a traceable source
- Entity resolution: The process of matching an event or record to a company or person
- Buying hypothesis: A testable reason an account may have a problem, distinct from a confirmed project
To put the relevant workflow into practice, sign up for Unify and review the proposed actions before enabling live outreach.
Frequently asked questions
Does company buying intent mean a specific contact wants a meeting?
No. Company-level activity can prioritize research, but it cannot by itself establish a person’s identity, preference, or authority.
Can website intent identify an individual visitor?
That depends on the particular signal and resolution method. Confirm whether the underlying record names a person or only a company before attributing the visit.
Who should an SDR contact after an account signal?
Choose a role relevant to the observed problem, verify the current person and CRM relationship, and coordinate with the account owner.
How should copy refer to account-level activity?
Use it as internal context. Avoid saying the recipient personally performed an action unless person-level evidence supports the claim.
What if the signal belongs to a subsidiary?
Preserve the subsidiary or business-unit identity, then check ownership and relevance there. Do not automatically assign the behavior to the parent.
When is a direct call appropriate?
A call is more defensible when the person’s role, eligibility, relationship, and specific reason to contact them are verified. A signal alone is not consent or a request.
Sources
- Unify Signals and Intent
- Turn Website Visitors Into Outbound
- How to integrate Unify with Salesforce
- Unify Task Management
- The Government Data Quality Framework, GOV.UK
Written by Austin Hughes, Co-founder and CEO of Unify.
