Sales · Specialized agent role

Sales Research Agent

The Sales Research Agent prepares a source-linked view of an account, its stakeholders, recent signals, and relevant internal history for a specific sales decision.

Get StartedReview the workflow

Best for

  • Sellers preparing for first outreach, discovery calls, executive meetings, or opportunity reviews
  • Account teams that need repeatable research structure and clear separation of internal and external sources

Typical inputs

  • Account name, website, known contacts, opportunity context, research question, and meeting purpose
  • Approved public sources, CRM history, prior communications, product relevance, and freshness requirements

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Clarify the sales question, account identity, audience, and time horizon

2

Gather context

Gather permitted internal context and current public sources with dates and links

3

Prepare the work

Organize company, stakeholder, trigger, relationship, and risk findings by relevance

4

Review and hand off

Deliver a concise brief that labels facts, interpretations, unknowns, and follow-up questions

Actions it can perform

  • Research company direction, leadership roles, public priorities, market context, and relevant events
  • Summarize CRM activity, identify stakeholder gaps, compare sources, and surface questions for discovery

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • A source-linked account brief, stakeholder map, signal timeline, and tailored discovery questions
  • Known-unknown list, source freshness notes, relationship summary, and meeting preparation checklist

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • sales-research
  • linked-view
  • stakeholders-recent
  • recent-signals
  • relevant-internal
  • internal-history
  • specific-sales
  • sales-decision
  • decision-give
  • give-sellers
  • sellers-concise
  • concise-evidence
  • evidence-aware
  • aware-account
  • without-conflating
  • conflating-unverified
  • confirmed-customer
  • facts-account
  • account-name
  • name-website
  • website-known
  • known-contacts
  • contacts-opportunity
  • research-question
  • meeting-purpose
  • history-prior
  • prior-communications
  • communications-product
  • product-relevance
  • freshness-requirements
  • requirements-clarify
  • sales-question
  • question-account
  • account-identity
  • identity-audience
  • time-horizon
  • horizon-gather
  • gather-permitted
  • permitted-internal
  • current-public
  • links-organize
  • organize-company
  • company-stakeholder
  • stakeholder-trigger
  • trigger-relationship
  • risk-findings
  • relevance-deliver
  • concise-brief
  • labels-facts
  • facts-interpretations
  • interpretations-unknowns
  • questions-research
  • research-company
  • company-direction
  • direction-leadership
  • leadership-roles

Human approval and escalation

Approval boundary

A seller reviews identity matches, sensitive findings, personalization choices, and any inference before using the brief in customer communication.

Escalation rule

Conflicting identities, weak sources, private-person data, rumors, legal issues, and potentially sensitive events are excluded or sent for review.

What remains under human control

  • Sales leaders define acceptable sources, privacy boundaries, research depth, retention, and how internal history may be used
  • The account owner interprets relevance, validates sensitive context, and decides what should influence the customer conversation

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

ApolloReview integration scopeHubSpotReview integration scopeSalesforceReview integration scopeNotionReview integration scope

Example workflow

Before an executive meeting, the agent combines current company announcements with CRM history, separates sourced facts from hypotheses, and proposes discovery questions.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

SDR Agent

See the responsibilities, controls, and handoffs for this related specialist role.

Explore SDR Agent

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible Sales Research Agent workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started