To evaluate the GTM automation software company Outreach on intent signals, judge it as an activation layer, not as a source of intent. Outreach does not produce third-party intent data of its own: its intent topics, intent spikes and website-visit signals arrive through a connected provider (ZoomInfo in Outreach's current documentation), and its Buyer Intent Score field holds whatever number a third party writes into it. So the evaluation has two halves. First, check the evidence each signal carries into Outreach: its source, its date and its strength label. Then check what Outreach does with it: whether the account fits your ICP, whether the signal is still current, whether the person contacted is the right one, and whether a person approves the first message before it goes out.

How to Evaluate the GTM Automation Software Company Outreach on Intent Signals: The Short Answer

  • Name the provider behind every signal. Outreach's intent topics article says topics "are currently supported through ZoomInfo", and its signals require "an active ZoomInfo Copilot product". The quality of Outreach's intent layer is, in practice, the quality of your provider contract plus Outreach's handling of it. The Signal Passport below lists what Outreach shows for each signal type.
  • Treat every signal as a reason to look, not proof of purchase intent. Outreach describes website-visit signals as indicating "increased web visit activity", and its intent tiers compare an account's research with its "historical baseline". Demandbase, which sells intent data, puts it plainly: a signal "does not by itself prove that an account is ready to buy."
  • Pass four questions before an automated send. Does the account fit the ICP, is the signal still current, is this the right person, and what is the next action and who approves it? The Four-Question Send Check maps each question to an Outreach setting.
  • Keep a manual first email until your own results say otherwise. Outreach's Revenue Agent guide recommends a manual first sequence step "so your reps can double-check the AI personalized content". Its intent documentation also calls medium-tier intent (60–75) "Suitable for fully automated workflows". Run the Manual-First Trial to decide which advice fits your accounts.
  • Compare Outreach with tools that produce signals, not only with other sequencers. 6sense and Demandbase score company-level research; Leadfeeder, RB2B and Warmly identify website visitors at company or person level; Unify and Outreach act on signals. Lead Seeker, which publishes this page, supplies dated public business events with a verified contact. It is not a visitor-identification tool and does not send email. Prices and plan details are an October 2026 snapshot.

What Outreach Calls an Intent Signal

Outreach describes itself as an "AI Agent Platform for Revenue teams", and its intent features sit inside that platform as inputs to targeting, prioritisation and personalisation. Its documentation describes five routes by which an intent-type signal reaches an Outreach record:

  1. Intent Topics. Topics an account is researching online, pulled from the enrichment provider and shown on the account. Outreach normalises provider scores into two tiers: Medium Intent (60–75), "increased research activity above normal levels", and High Intent (76–100), "strong, statistically significant surges in interest". Scores below 60 "are excluded from the Outreach UI and API". The article lists "Outreach Amplify SKU customers" and ZoomInfo as the provider.
  2. Signals from Smart Data Enrichment. Event and intent signals written to the account: intent spike and intent competitor spike (each with a high, medium or low strength), website visit, G2 visit, anomalous hiring, CXO change, new funding round, senior job postings, new technology and others. Outreach says signals "are refreshed weekly by ZoomInfo and remain valid for 7–90 days depending on the signal type."
  3. Website visit signals. High or medium activity for an account, or for an identified prospect within it. Sellers see "the strength, visited URL, and visited date", and for prospect signals "the visitor's name". The feature "requires that the websites are set up for tracking using ZoomInfo".
  4. The Buyer Intent Score field. A numeric account field that "supports positive, negative, integer, and non-integer values" and can be used in triggers. Outreach says it is most often filled "from an intent data provider (i.e. Bombora, TechTarget, G2, 6Sense) via CRM, or from a generic account intent score in your CRM". Outreach does not define the scale; the provider does.
  5. Integrations and research. G2's Outreach integration maps G2 Buyer Intent signals to Outreach accounts by matching website domains. Outreach's Research Agent builds "custom signals" from conversations, engagements and public sources, and the product page says users can "Hover over each finding to see its source". First-party data such as product usage can be brought in from Snowflake.

The signal type that matters for this evaluation follows from that list. Outreach mostly receives inferred signals (a provider's model says research activity has risen above a baseline) and observed events (a funding round, a senior hire, a page view on your site). The distinction between the two, and the third grade of reported evidence, is set out in the Observed, Reported, Inferred grades in buying signals vs intent data. For a plain definition of the category itself, Percepture's guide to what is B2B intent data covers the basics.

Why a signal is not proof of purchase intent

A surge score says an organisation consumed more content on a topic than it usually does. It does not say who read it, whether they hold budget, or whether they are evaluating a purchase rather than writing a report or studying a competitor. A website-visit signal says traffic from an account rose; Outreach's own wording is "increased web visit activity", not a buying decision. Even a person-level visit tells you someone looked, not why.

The practical consequence is that a signal should change which accounts you look at and when, and never stand alone as the reason an automated sequence starts. The sales-qualification step, where a signal is combined with fit and engagement before anyone calls an account qualified, is covered in Percepture's guide to using intent data to identify sales qualified leads.

Decision Framework: the Four-Question Send Check

Each automated touch triggered by a signal should pass four questions. The table shows the Outreach setting that answers each one and what should happen when it cannot.

Question What it decides Where Outreach answers it When the answer is missing
1. ICP fit: does the account belong in your market at all? Whether the signal is worth reading Account filters and saved smart views in the Revenue Agent's target accounts; firmographic enrichment fields Drop the signal. A surge at a non-ICP account is noise however strong it is
2. Timing: is the signal still current? Whether to act this week Intent date and intent level filters on Intent Topics; signal validity windows of 7–90 days; the visited date on website signals Re-check the account at the next weekly refresh instead of sequencing it
3. Contact relevance: is this the person who would own the problem? Who receives the first touch Revenue Agent prospect filters: department, seniority, location, time in current role, total work experience; known email or phone only Route to a researcher or the account owner as a task, not to a sequence
4. Next action and approval: what happens, and who signs off? Channel, sequence, sender and human review Sequence choice, a manual first email step, "Throttle newly added prospects", mailbox assignment, and triggers that create tasks Default to a task for the account owner, not an automated email

Two Outreach behaviours make questions 1 and 3 more important than they look. When several targeting signals are selected in a Revenue Agent, "an account only needs to match one of them to be included", so a broad signal list widens the target set rather than narrowing it. And when the agent enriches an existing prospect, it "waits for at least one enrichment attempt and then adds the prospect to a sequence, regardless of the enrichment outcome." Fit and contact filters therefore have to be set in the agent itself, because enrichment will not stop a record.

Question 4 is where Outreach's own guidance points in two directions. The Revenue Agent guide recommends a manual first email, and reps see any AI-drafted content "highlighted in purple so that it can be reviewed and adjusted by the rep if needed". The Intent Topics article describes the medium tier as "Suitable for fully automated workflows (e.g., auto-enrollment in automated sequences)" and the high tier as "Ideal for higher-touch plays". Those two pieces of advice can be reconciled: tier decides the play, the four questions decide whether it runs unattended.

Evidence Table: the Signal Passport

The Signal Passport records, for each signal type Outreach can hold, the evidence that travels with it. The last column is labelled "Hypothesis to test" on purpose. It is a guess about what the signal could mean for your accounts, to be confirmed in your own results, not a statement of what it does mean.

Signal in Outreach Source behind it Timestamp Outreach shows Strength or confidence label Level Hypothesis to test
Intent Topic ZoomInfo (the provider must have topics configured and active) Intent date, used as a filter Medium 60–75 or High 76–100 after normalisation; below 60 hidden Account The account is researching the topic more than its own baseline
Intent spike / intent competitor spike ZoomInfo signal Weekly refresh; valid 7–90 days by signal type High, medium or low Account Research on your topic cluster, or on a competitor, rose this period
Website visit (account) ZoomInfo website tracking Visited date and URL High or medium activity Account Someone at the account is reading pages you can name
Website visit (prospect) ZoomInfo website tracking Visited date and URL, plus the visitor's name High or medium activity Person A named person returned to specific pages; does not say why
Event signals: funding, CXO change, senior job postings, new technology, layoffs and others ZoomInfo (several marked "Outreach generated signal based on Account data") Weekly refresh; valid 7–90 days by signal type None stated Account A dated change may have opened a budget or a new owner
Buyer Intent Score Whatever provider or CRM score is mapped in: Outreach names Bombora, TechTarget, G2 and 6sense as typical Not described; depends on the integration The provider's own scale; Outreach accepts any number Account Above your chosen threshold, the provider's model rates the account as more active
G2 Buyer Intent G2, matched to the Outreach account by website domain Set by G2's integration G2's own signal types Account (organisation) Someone at the organisation compared or viewed products in your category on G2
Research Agent custom signal Conversations, engagements and public web sources Not described None stated; source shown on hover Account or person A public event or statement fits a pattern you defined

Three rules follow from the table. First, write the source next to the signal wherever it is stored, because "intent" from ZoomInfo, G2 and a CRM-mapped Bombora score are three different measurements. Second, store the date, so the timing question can be answered without a person opening the record. Third, keep the provider's label and do not convert it into a single blended score until you have checked each input against your own outcomes. The Signal Clock in reducing time between buying signal detection and sales touchpoint shows which timestamps to keep so delays can be measured.

One Rubric for Outreach and the Platforms Compared With It

Outreach is rarely bought on its own for intent. Buyers compare it with platforms that produce signals and with other tools that act on them. The rubric applies the same columns to each. Rows are grouped by role: tools that act on signals, tools that score account research, tools that identify website visitors, and Lead Seeker as the publisher. Inside each group they are alphabetical, and no order implies a ranking.

Platform Role Where its signals come from Level Freshness stated Strength label Contact step Automated next action Human review documented Price published
Outreach Acts on signals Connected providers: ZoomInfo for topics and signals; CRM or partner scores in the Buyer Intent Score field; G2; Snowflake Account; person for identified website visitors Signals refreshed weekly; valid 7–90 days Medium/High tiers on topics; high/medium/low on spikes Revenue Agent filters on existing or newly sourced prospects Sequence enrolment, tasks via triggers, AI-personalised emails Manual first email recommended; rep review of AI content; option for reps to activate prospects first No: "Request pricing"; seats plus AI credits
Unify Acts on signals Website visitors, champions, new hires, lookalike companies; product usage Account and person Website events appear in "one to two minutes" Not described "A play can then find the relevant people and route them to the account owner" Qualification, notifications, sequence enrolment, agentic emails Chat and list enrolments: drafts to "review and approve before outreach starts"; from a person's record, "without separate draft approval" Yes: free plan; paid seats from $20 a month
6sense Scores account research Its own intent model: searches, links clicked, forms, page views Account Intent score "updated daily" 0–100, mapped to buying-stage bands Not described in the documents cited Not described in the documents cited Not described No
Demandbase Scores account research B2B content consumption and production, engagement on your website Account Intent "aggregated weekly" Low, medium or high, relative to similar-sized accounts; Intent engagement points Not described in the documents cited Prioritisation, alerts, audiences and advertising Not described No
Leadfeeder Identifies visitors Website visits resolved to companies Account; individuals only when they identify themselves Companies identified "in real time" ICP fit and automatic lead scoring; no published scale Not described CRM push, email or Slack alerts Not described Free plan and a 14-day trial; paid tiers by companies identified
RB2B Identifies visitors Website visits resolved to people (US) and companies (global, through Demandbase) Person (US-only) and account Not described Not described The identified visitor, filtered by seniority, department and similar fields Push to Slack, Teams, CRM, Clay, webhook; "start automated outreach" Not described Yes: free plan; Starter $79 a month
Warmly Identifies visitors and acts Website visits, chat, Bombora surge, job postings, G2 research, job changes, CRM history Account and person Audiences "refresh daily (or real-time for high-intent triggers)" "Transparent ML" scoring; no published scale AI analysis of org charts, job descriptions and LinkedIn data "Route to reps, let AI send autonomously, or go hybrid" Hybrid mode offered; approval step not described TAM Agent "included in Warmly plans starting at $15,000/year"
Lead Seeker Supplies public-event signals and contacts Public business events: hires, funding, posted roles, tech changes, earnings transcripts Account, with a verified contact per search Lead Compass offers weekly or on-demand refreshes; each dossier shows the date it was last verified None published A verified decision maker returned by a search you run None: it does not send; saved prospects and dossier context sync to Salesforce or HubSpot The user chooses every search; Lead Units are used only then Yes: $99 14-day pilot; Starter $149 a month

HubSpot announced on June 30, 2026 that it would acquire Warmly; Warmly told customers that existing contracts and pricing "remain unchanged" for now.

What the rubric shows

Statement
Fact Outreach, Unify and Warmly act on signals as well as receiving them; 6sense, Demandbase, Leadfeeder and RB2B mainly produce or deliver signals that another tool acts on.
Fact Only Outreach and Unify document a human review step before AI-drafted outreach in the pages cited. Unify's applies to chat and list enrolments, not enrolments started from a person's record.
Fact The strength labels are not on one scale: Outreach normalises provider scores to 60–100 tiers, 6sense uses 0–100 bands, Demandbase grades low, medium or high against similar-sized accounts, and the Buyer Intent Score accepts any number.
Inference A team that already pays for ZoomInfo gets most of Outreach's intent layer without a second data contract. A team on another provider gets the Buyer Intent Score field and integrations, but not the topic and signal filters the Revenue Agent documentation describes.
Inference The same feed can enter Outreach twice: a Bombora score mapped through the CRM and Bombora surge data inside another platform describe one observation, not two.
Our view For an Outreach evaluation, the provider decision and the approval design matter more than the agent's feature list. If those two are settled, Outreach's filters, throttles and manual steps are enough to run the Four-Question Send Check inside the product.

For the provider decision itself, the comparison of the best intent data providers covers sources, refresh cycles and pricing across the producing side of this table.

Implementation: the Manual-First Trial

The Manual-First Trial runs one Revenue Agent play for four weeks with a human-approved first email, then decides from your own numbers whether any tier can run unattended. Four weeks gives four weekly signal refreshes.

  1. Pick one signal and one play. For example, accounts in your ICP with a High Intent topic in the last 30 days, which is close to the example in Outreach's own documentation. Use a dedicated sequence with "AI Agent" in its name, as Outreach recommends, so the Sequence Performance Report can isolate it.
  2. Set the four questions in the agent. Account filters for ICP fit; intent level and intent date for timing; department, seniority and time in role for the contact; a manual first email step for approval. Keep the default throughput (Outreach's default is 30 accounts a day) or lower it so reviewers can keep up.
  3. Log the reviewer's decision. For every first email the rep approves, edits or rejects, record which of the four questions failed when it was rejected. That record is the data the trial exists to produce.
  4. Hold out a matched group. Keep a set of ICP accounts with the same signal out of the agent and work them as you normally would. Without a holdout, a reply rate says nothing about the signal.
  5. Decide at week four. Compare replies, meetings and opportunities by signal tier against the holdout, and read the rejection log. A tier whose first emails are rarely edited and whose results beat the holdout is a candidate for automated first touches. A tier with frequent contact or timing rejections needs tighter filters, not more automation.

A worked example (invented)

The company and every value below are invented to show the set-up. No outcome is reported.

Tallowbrook Payroll Cloud (invented) sells payroll software to US companies with 200 to 2,000 employees. It runs Outreach with ZoomInfo as the enrichment provider.

Four-Question Send Check Setting
ICP fit Smart view: US, 200–2,000 employees, not a current customer, no open opportunity
Timing Intent Topic "payroll software" at High (76–100), intent date within 30 days; or an intent competitor spike at high strength
Contact relevance Finance and HR departments; director level and above; in role for at least six months; known email only
Next action and approval Dedicated "AI Agent" sequence; step 1 manual email reviewed by the account owner; throttle set so reps activate prospects; medium-tier accounts get a task, not a sequence
Holdout One in five qualifying accounts held out and worked by the normal SDR process
Review Week four: replies, meetings and opportunities by tier against the holdout, plus the rejection log by question

The order is the point of the example: the rules for every signal exist before the agent's first send, so no rep has to decide record by record whether a surge justifies an email.

Where Lead Seeker, Pyra and Percepture Fit

Bob Generale, who wrote this page, is President of Percepture and a co-founder of Pyra; Lead Seeker publishes the page.

Lead Seeker fits beside Outreach when the gap is the trigger rather than the sequencer. It supplies a different signal type from Outreach's providers: dated public business events (hires, funding, posted roles, tech changes, earnings transcripts) rather than topic surges or website visits. Lead Seeker does not identify website visitors, does not produce third-party topic intent and does not send email. Lead Compass uses your website, ICP and intent themes to surface opportunity picks and "cite public sources where available", and it does not consume Lead Units until someone runs a search. The buying-signal coverage in the platform lists the event types, and the page on how Lead Seeker works shows the route from ICP to a verified dossier synced to Salesforce or HubSpot. Starter is $149 a month with 75 Lead Units.

Percepture runs B2B intent data services for teams whose constraint is people rather than software. Its service page describes a split of strategy (ICP, signals, messaging, "guardrails, and approval paths"), AI and data execution on Lead Seeker and Pyra, and a human operator who "reviews fit". That is a service around a tool like Outreach, not a rubric row.

Pyra builds AI agents for named workflows, including outreach, as a paid pilot on one workflow, built "on your own data" and run "with your approval gates in place". It is relevant when a team wants a custom agent for a step Outreach's packaged agents do not cover. It is not a data source or a sequencer.

Where Intent-Triggered Outreach in Outreach Falls Short

  • Provider dependence. Topic intent is ZoomInfo-only in the Intent Topics article, and signals require ZoomInfo Copilot. Outreach's data-coverage article also lists an Intent Topic field under SalesIntel. Ask which providers are supported for your contract before you plan around a topic filter.
  • Weekly evidence. Signals refresh weekly. A same-day response to a topic surge is not possible through this route, whatever the agent's speed.
  • Previews that do not show signals. Outreach notes that the Revenue Agent's account preview "does not reflect third-party data (targeting signals)" until enrichment completes. The list you approve at set-up is not the list the agent works.
  • Enrichment does not gate. Existing prospects are sequenced after one enrichment attempt "regardless of the enrichment outcome." Contact filters must do the gating.
  • An undefined scale. The Buyer Intent Score accepts any value. Two providers mapped into it in sequence leave a number with no fixed meaning; record which provider wrote it.
  • Person-level data brings obligations. A prospect-level website signal names the visitor. Whether you can use that name in outreach depends on your jurisdiction, your provider's terms and your own notices, not on Outreach's settings.
  • Package gating. Revenue Agent and Personalization Agent are listed in Amplify Core and above, not in Amplify Essentials, and Outreach publishes no prices. Budget for seats, AI credits and the provider contract together.

Frequently Asked Questions

Does Outreach have its own intent data?

Not as a third-party data source. Outreach's intent topics and signals come from a connected enrichment provider, which its current documentation names as ZoomInfo, and the Buyer Intent Score field is filled by a provider or CRM score such as Bombora, TechTarget, G2 or 6sense. Outreach does generate some signals from data it already holds, such as website visit and new funding round signals based on enriched account data, and its Research Agent builds custom signals from conversations and public sources. Evaluate Outreach on how it uses intent, and evaluate the provider on how it measures it.

Which Outreach package includes intent-signal features?

Outreach's pricing page lists Revenue Agent and Personalization Agent in Amplify Core, Amplify Plus and Amplify Pro, and Data Enrichment in every package including Amplify Essentials. The Intent Topics article applies to "Outreach Amplify SKU customers" with ZoomInfo connected, and signals require an active ZoomInfo Copilot product. Outreach prices by seat plus AI credits and publishes no figures, so confirm package, credits and provider requirements in the same quote.

Should medium-intent accounts go into fully automated sequences?

Outreach's Intent Topics article describes the medium tier (60–75) as "Suitable for fully automated workflows", while its Revenue Agent guide recommends a manual first email so reps can check AI content. A safer rule is to let the tier decide the play and let four checks decide automation: ICP fit, a current signal date, the right contact and an agreed next action. Start every tier with a manual first email, then automate only tiers whose first emails are rarely edited and whose results beat a holdout group.

What is a GTM intelligence platform?

A GTM intelligence platform collects and scores signals about accounts and people so revenue teams can choose whom to contact and when. In practice the category splits in two: platforms that produce signals, such as 6sense and Demandbase scoring account research or Leadfeeder and RB2B identifying website visitors, and platforms that act on them, such as Outreach and Unify enrolling prospects in sequences. Many buyers need one of each, connected through the CRM.

How do you measure whether intent-triggered outreach works?

Compare it with a holdout. Run the signal-triggered play through a dedicated sequence, which Outreach recommends naming with "AI Agent" so its Sequence Performance Report can isolate it, and work a matched set of accounts with the same signal through your normal process. Compare replies, meetings and opportunities by signal tier over at least four weekly refreshes, and record why reviewers reject first emails. Agent activity counts alone do not show whether the signal added anything.

How to Read the Rubric

Each cell restates the vendor's own help centre, documentation, product page or pricing page, and quoted phrases are verbatim. "Not described" means the documents cited for that vendor do not cover the point; it does not mean the capability is absent. Vendor accuracy, productivity and pipeline figures on those pages are vendor-reported and are not repeated. Strength labels are given on each vendor's own scale and should not be compared across rows. Rows are grouped by role and listed alphabetically inside each group. Fact, inference and our view are labelled where they appear side by side, and "Hypothesis to test" marks interpretations that your own data must confirm. The worked example is invented.

Sources

About the Author

Bob Generale is President of Percepture and a co-founder of Pyra AI. He works across SEO, AI search, digital PR, sales intelligence and AI-powered revenue systems, with a focus on connecting visibility, buyer intent and sales action.

Next Steps

Before a demo, ask Outreach and your intent provider to fill in the Signal Passport for your account: which provider writes each signal, the date it carries and the label it uses. Then set one play through the Four-Question Send Check and run the Manual-First Trial for four weeks. For how this rubric applies to Outreach's closest all-in-one competitor, see the Outbound Control Map for evaluating Apollo on outbound sales.