UnifyOutbound teardownsFin (Intercom)

How Fin (Intercom) rebuilt reps’ trust in its outbound account list

Company
Fin sells customer service software built around Fin, its AI agent. It was called Intercom until May 2026, and Salesforce completed its acquisition of Fin in September 2026.1,2
Visit Fin ↗
Who ran it
Alexander DeMoulin, director of GTM Ops at Intercom
Headcount
Team size and hiring trends
Fin headcount ↗
This page
The fall 2024 list rebuild; later Fin sources appear only in What it took

TL;DR

Reps worked only 19% of Intercom’s fourth outbound list. Ops then asked them which accounts they would actually work, turned the answers into rules, such as ranking companies with a login button on their website higher, and checked every account against Salesforce. Reps worked 72% of the next list in its first week.

The lesson

Messy CRM data broke the list. Duplicate records hid customers, owners and open deals, so reps couldn’t trust that any account was free to call. Intercom didn’t wait for a clean CRM; it checked every account against every record before a rep saw it.

For your team

Ask reps which accounts they would work, and check each one for CRM conflicts before you tune the score that ranks it.

What Intercom did

The starting point

Intercom bet the company on Fin, and outbound had to find new accounts.

In a May 2024 email to staff, reported by The Irish Times, CEO Eoghan McCabe wrote: “Winning in this game will require aggression on all fronts, not just with our capital.”3

Eoghan McCabe@eoghanMar 2, 2026

Three years ago, our future was looking pretty bleak. I jumped back into the CEO role after a two year hiatus while sick, when we were heading quickly towards negative growth. …

We changed our targets to Fin revenue. … We moved our R&D focus to be nearly 80% on Fin, while that business was still a single digit percent of our revenue.

McCabe’s chart of quarterly growth rates, Q4 2020 to Q4 2026: SaaS growth falls from about 33% to 12%; Intercom’s falls from 37% to 4% in Q3 2023, after the CEO change in Q4 2022 and the Fin launch in Q3 2023, then climbs past the SaaS line to 24% by Q4 2025, with a projection to 37%.
Excerpt; cuts are marked …Read the post on X
Source: Eoghan McCabe, X post, Mar 2, 2026What it shows: McCabe looking back in March 2026 on the bet, with the growth chart he posted. Excerpted verbatim; cuts are marked.

That fall, GTM Ops was launching outbound for the entire sales team, said Alexander DeMoulin, who ran it. Accounts that looked like Intercom’s existing customers had thinned out since 2022, he said, so reps would be calling companies unlike the ones they knew.5,6a

The problem

Sales worked 19% of the fourth list.

DeMoulin was at a chili cook-off in Sausalito one weekend in September 2024 when a Slack message arrived from his boss’s boss. It said the reps seemed to really dislike their new outbound list, and asked what had happened.5b His heart sank, he said, and he drove home to fix it.

It was the fourth list in his four years at Intercom.c The first used whatever data was in Salesforce, the second a cold list imported from outside, and the third good scoring and intent data mapped badly onto Intercom’s own records. Each time, he said, trust fell further.5

By his count, sales worked 19% of the fourth list’s accounts. It counted accounts reps were willing to send a single email.5 By then, sales would only give ops time for work that clearly helped them hit their number.6

In 2025 he said that on earlier lists he had doubted the accounts or the data sources, said nothing, and supported them anyway.6 In 2026 he said he had destroyed trust with the sales team three times in a row.7

The decision

September 2024

DeMoulin stopped perfecting the score and asked reps which accounts they would work.

Every account would be checked against Salesforce when it was assigned, because the CRM would never be clean.

Intercom was good at propensity modeling, DeMoulin said, but after so much lost trust the list had to match what reps thought a good account was. If they only wanted accounts that mention peanut butter on their website, he would find as many as he could.6

GTM Ops asked reps to describe the ideal outbound list as if they had a magic wand. It also sat behind reps on ride-alongs and asked what they look for in the 30 to 90 seconds they spend researching an account.5,6

DeMoulin did not believe Intercom would ever get rid of its duplicate Salesforce records, and would not let that stop the list. He said the trouble came when an account looked great on the list while a duplicate record was already in a relationship with Intercom, and the sales team was strictly monogamous.5

Ops promised reps that, while duplicates still existed, no assigned account would hide one.6

The redesign

Reps wrote the rules, in their own words.

Some rules took an account off the list; the rest ranked what was left.

  1. “Don’t you dare assign me a customer”

    Rules it out

    Already a customer, owned by a relationship manager or in an open Salesforce deal

  2. “We love our competitor’s customers”

    Ranks it higher

    Already paying a competitor

  3. “You’re terminally online and we like that”

    Ranks it higher

    Has a login or “my account” button on its website, checked by an AI agent

Redrawn from DeMoulin’s slides, Sculpt, Sep 2025: what reps said, 5:45, competitors’ customers, 10:50What it shows: what reps asked for, in the words DeMoulin put on his slide, and the rule each line became.

The rules that took an account off the list were blunt: a country Intercom never sells to, or too few employees.5 A slide he showed at RevFest in June 2025 also flagged any company whose description mentioned “nonprofit”, “agency”, “consulting”, “acquired” or “now part of”.8

The ranking rules came from the ride-alongs. A login, sign-up or “my account” button on a company’s website meant a customer portal behind the marketing site, where customers raise support tickets.6 GTM Ops had an AI agent visit every account’s website to check, which DeMoulin called a vibe check that ordinary enrichment data could never give.5

Every record on the domain was checked

GTM Ops pooled accounts from Salesforce, data providers and intent sources, and collapsed them to one company per Clearbit domain.5 For each domain it queried every Salesforce account on it. His slides show the checks as columns, in his own labels: Customer?, RM Owned? (owned by a relationship manager), Sales Strategy?, Open Opps? and Recent Churn, and on the podcast he added activity in the last 60 days.5,6

An account that looked clean, with a duplicate record in a deal

Illustrative company and records; the checks are Intercom’s.

What the list showed

Brightwaybrightway.com
Country
United Kingdom
Employees
1,200
Customer?
No records found
Open Opps?
No records found

Looks workable

What the check found

Brightwaybrightway.co.uk, a second record, in another rep’s deal
Open Opps?
1 record found

Not assigned

Every Salesforce record on the domain was checked, column by column: Customer?, RM Owned?, Sales Strategy?, Open Opps?, Recent Churn, plus activity in the last 60 days. Any record found kept the account off the list.

Source: Alexander DeMoulin, Sculpt 2025 talk, Sep 17, 2025; Alexander DeMoulin, OnBase podcast, Jul 17, 2025What it shows: why the checks read every record on a domain; the company is made up, and the check names are DeMoulin’s.

Reps still searched Salesforce for duplicates themselves, which DeMoulin said was right, before reaching out.6

The result

Sales worked 72% of the new list in week one.

The rebuilt list went out less than a week later.

Lists 1 to 3: Salesforce data, a cold import, scoring and intent data

List 4, fall 2024

19%

Number of accounts worked by Sales

List 5, first week

72%

Number of assigned accounts worked by Sales

Redrawn from DeMoulin’s slides, Sculpt, Sep 2025: 19%, 4:38, 72%, 8:50What it shows: accounts worked, before vs. first week of the rebuilt list. DeMoulin counted it as adoption. It doesn’t measure pipeline.

No salesperson had ever told him a list was really good and that they couldn’t wait to cold outbound to it, he said, until this one.6

With bad data no longer the excuse, ops could see reps spending too long on low-propensity inbound deals, cold email copy that wasn’t landing, and buyer personas that no longer fit an AI buying committee.5 When accounts sales had picked sat untouched, ops asked why, and sometimes a rep simply had too many inbound deals.6

What it took

A weekend of ops work started it, and keeping it right became an engineering job.

The loop DeMoulin’s team ran on the list

PrototypeA weekend in September 2024FeedbackReps worked 72% andtold ops what failedIterateBatches went monthly, thenquarterly, then twice a yearOperationalizeA systems team by Sep 2025;his team’s first GTM engineer,Sep 10, 2025; a staff dataengineer role, Aug 2026
  1. PrototypeA weekend in September 2024
  2. FeedbackReps worked 72% and told ops what failed
  3. IterateBatches went monthly, then quarterly, then twice a year
  4. OperationalizeA systems team by Sep 2025; his team’s first GTM engineer, Sep 10, 2025; a staff data engineer role, Aug 2026
Redrawn from DeMoulin’s slides, Sculpt, Sep 2025: the loop, 6:20What it shows: step names are DeMoulin’s; the dated notes are ours, from the sources below.

The first rebuild ran on GTM Ops time and data Intercom already had. Batches went from monthly to quarterly, and by September 2025 to twice a year, as a systems team took over the website enrichment ops had prototyped.5,6

On September 10, 2025, DeMoulin posted that he was hiring the first GTM engineer onto his team in San Francisco, to improve GTM processes with AI.9

In August 2026 Fin posted a Staff Data Engineer, GTM role in its Data group. It owns account identity, hierarchy, deduplication, sourcing, enrichment and data-quality monitoring, the same problems the weekend rebuild worked around.10

Check every account against your CRM.

Leave out customers, open deals and owned accounts before an account reaches a rep.

What to borrow

  1. Track how much of the list reps actually work. Check it before meetings or pipeline. Intercom went from reps working 19% of the accounts to 72%.
  2. Ask your reps what makes an account worth calling, and turn the answers into rules. Intercom asked reps to describe their dream list and sat with them while they researched accounts. That’s how it learned a login button on a company’s website was a good sign.
  3. Check the CRM before a rep gets an account. Rule out anything already a customer, owned by someone else or in an open deal. Intercom’s CRM was never fully clean, so it ran this check on every account, every time.

How to build a version of this in Unify

Build it in Unify

Everything above is what Intercom did. From here on, this is our suggestion for a version in Unify.

Intercom’s GTM Ops joined its data itself: Salesforce, data providers, intent sources and a website scrape. Unify combines your CRM, warehouse and product usage data with enrichment from 40+ sources, with warehouse data synced in through a sync tool or the API. A rep working the list would see an account like this fictional one.

One account, from signal to next step

Account
Tidewell Pay, a payments app in Dublin with 900 employeesIn the workable Audience: right country and size, and no CRM record on its domain is a customer, owned, in a deal, recently churned or recently worked.
Signal
A customer login on every page, a 30-day free trial, and two support roles posted in SeptemberFrom AI Agent qualification questions written from the reps’ checks.
Why it matters
Its customers log in to accounts, so they raise support tickets, and the team answering them is growingAI Research on the rep’s task says why it qualifies and why it is safe to call.
Next step
Maya Collins in Dublin confirms there is no duplicate in the CRM, then approves an email to Nora Quinn, Head of SupportFrom the Play: owner assigned by territory, three support leaders found, and a Sequence the rep approves.
Example data: the company and people are fictional. Features are Unify’s as documented, October 2026.

This week, run the session with reps and list the CRM fields that make an account unworkable. The Audience, the AI Agent qualification questions and the Play are built from that session.

did this
Our version in
Rules from repsMagic-wand calls and ride-alongs
A person, before any setupRevOps sits with reps and their manager and writes each exclusion and each rep check as a yes or no question
One company per domainDuplicates collapsed to one key
A list of unworkable fieldsFrom the same session, the CRM fields that mark an account unworkable. A duplicate record can still hide a deal, so the rep’s first Sequence step checks the CRM for another record on the domain
Rules out: can sales work it?Country, size and six Salesforce checks
Audience filters and exclusionsCountry and employee range on the Audience, with exclusions on synced CRM fields for open opportunities, current revenue, churn within 90 days, an owner or strategy, and activity within 60 days
Ranks the rest: how much do we want it?A login button and other rep checks
Agent qualificationEach rep check as an AI Agent qualification question, such as “Does the website have a login or ‘my account’ link?”. Accounts that pass go forward
Assigned in batchesMonthly, then quarterly, then twice a year
A reviewed batch, then one PlayRevOps reviews the results and marks the approved batch in a CRM field. A Play triggers when an account enters that batch Audience, assigns an owner and finds 1 to 10 people per company across up to five personas
Reps check, then reach outSearching Salesforce themselves
SequencesThe first step is an action item to confirm the account is workable. Manual emails, calls and LinkedIn action items follow, each approved by the rep, with delays in days
Feedback both waysRules change before the next batch
Two-way CRM sync and a reviewReps record failure reasons in a CRM field, and RevOps and sales managers edit the Audience and Agent questions at each review. Opportunities are created by reps in the CRM, and Unify reads them
Left: Intercom’s list as Alexander DeMoulin described it in 2025. Right: our suggested version, using Unify features as documented in October 2026, with CRM configuration and people where noted.

Unify product demo, October 2026, in one conversation. Our suggested version of Intercom’s approach, built from Unify features.

Give reps a list they will work, in Unify

Accounts that clear your CRM checks, the reason each one qualified, and Sequences your reps approve.

Frequently asked questions

How did Fin (Intercom) build an outbound list its reps would work?

In fall 2024, after sales worked only 19% of the accounts on its fourth outbound list, Intercom’s GTM Ops asked reps to describe their ideal list and watched them research accounts. It collapsed duplicate records to one company per domain, removed any account that broke a hard rule or had a conflicting Salesforce record, and ranked the rest by the reps’ own checks, such as a login button on the company’s website. Sales worked 72% of the rebuilt list in its first week.

What did Intercom check in Salesforce?

Every Salesforce record on the account’s domain. DeMoulin’s slides label the checks Customer?, RM Owned?, Sales Strategy?, Open Opps? and Recent Churn, and on a podcast he added activity in the last 60 days. One record found kept the account off the list.

Why didn’t Intercom start with a better score?

Reps trusted the fit. They doubted that an account was safe to call, because a duplicate record could already be in a deal, paying or being worked. DeMoulin said Intercom was good at propensity modeling, yet he built the rebuilt list around what reps would accept.

Did it work?

Reps worked it. On DeMoulin’s slides, sales worked 19% of the fourth list’s accounts and 72% of the rebuilt list’s in its first week, which he counted as adoption. Neither figure measures pipeline.

How do I run a version of this in Unify?

Start with a session where reps write the rules and list the CRM fields that make an account unworkable. An Audience then excludes accounts with CRM conflicts, and Agent qualification questions check the rest against your reps’ rules. After RevOps approves a batch, one Play assigns owners and finds people. Each rep confirms the account before approving their Sequence, and their CRM feedback shapes the next batch.