I have been following what Intercom, now Fin, has been building for years. Eoghan McCabe’s willingness to destroy a functioning business to rebuild it around a conviction is rare, and it deserves to be taken seriously.

This analysis exists because one question keeps surfacing when I watch companies at this stage: what business are you actually in? Not what you sell, not what you call the category. What concept do you own in the minds of the people who use you? No one can read their own label. The person inside the bottle cannot see what is written on the outside. That is not a flaw; it is just the geometry of the situation.

I have tried to get the facts right. I used public statements, customer forums, analyst reports, and Eoghan’s own words from interviews and posts. Where I have read the data incorrectly, the intention is not to misrepresent. If anything here is wrong, I would genuinely want to know.

One qualifier worth naming: Eoghan has access to internal data I do not. He can see what customers actually do, what they pay, where they churn, and what they say on calls. A founder reading an outside analysis always holds information the analyst does not. I am reading from the outside. That is the only place this kind of reading can happen from. The entire premise of what follows is one question: what business are you in?

How to read this analysis

The 4-Level Positioning Canvas is the framework on which this analysis runs. Here is a fast orientation before you get into the work. There are four levels. They build in a specific sequence. You cannot skip them.

Level 4 — POSITION (Own the Noun). This is the concept that becomes synonymous with you in customer minds. Volvo owns safety. Tesla owns the future. It takes 5 to 10 years to establish and cannot be claimed explicitly; it has to be proven implicitly, through decisions made consistently over time. The moment you say “we own X,” you weaken the claim. The proof has to precede the words.

Level 1 — FRAME (Articulate). This is how you put the positioning into language: taglines, messaging, narrative. It is the easiest level to develop and the weakest barrier. Anyone can change their words. Most companies live here.

Level 2 — EXECUTE (Prove with Verbs). This is where you validate the positioning with measurable outcomes. Not claims about what you do; evidence of what you have delivered, with a baseline, a result, and a way for customers to verify it.

Level 3 — LIVE (Embed Structurally). This is positioning built into the structure of the business: resource allocation, hiring criteria, partnerships, what you refuse to build. The standard is 70% or more of resources flowing to positioning-critical capabilities. At this level, the positioning survives a CMO change.

The sequence runs Level 4 → Level 1 → Level 2 → Level 3. You start by finding the noun you want to own, then you learn to articulate it, then you prove it with outcomes, then you wire it into the structure of the company so it runs without anyone saying it out loud.

Most companies operate at Level 1 while claiming to be at Level 4. They have the language. They do not have the proof or the structure. The gap between where a company actually is and where it believes it is: that is where this analysis lives.

TL;DR — For Eoghan, directly

You think you built the Customer Agent. You told the market you created a category, invented outcome-based pricing, and built the highest-performing agent in the space. That is the noun you have been fighting for. It is not the noun you own. Your customers own a different one, and they picked it first. After a year of running Fin, the support leader stops being a firefighter who manages a room of humans and becomes an orchestrator of a resolution machine, and then something above the job title: the one who is trusted to judge. The role is orchestrator. The identity underneath it is arbiter, the person the machine defers to on the hard cases. Angelo Livanos at Lightspeed narrates rebuilt career ladders. Kate Leggett at Forrester writes that AI now does the majority of the work while people assist it. Gartner’s Eric Keller tells service leaders to redeploy humans into roles AI cannot replace. A competitor at MyAskAI concedes Fin ranks among the strongest agents available. The register is neither triumph nor safety. On the forums where no one is being sold to, the tone is hedged survival, conditional relevance; the word “liberated” appears nowhere. The one thing they will not say warmly is your bill. The same customers whose judgment your product elevated call your pricing a “resolution tax,” and that tension runs through the whole report.

Resolution-as-outcome has been your operating filter the whole time. You killed roughly $60M of legacy ARR so seat revenue could not protect you. You moved nearly 80% of R&D to Fin while Fin’s revenue was in the single digits. You built Apex and refused to sell it as an API. You priced at $0.99 per resolution and staked $1M on hitting 65%. You renamed a fifteen-year-old company to match the agent. Every one of those decisions is coherent under one noun. None is coherent under any other.

For fifteen years the game was making the support seat more capable. For the next ten it is making resolution a purchasable outcome the vendor takes risk on, and moving the buyer from doer to conductor. The Salesforce deal does not change that game. It puts it in front of a much larger audience, faster.

The filter belongs inside the company: in who you hire, where capital goes, what you refuse. Not on a billboard. The position is what Fin already does, not what it says. Eoghan, your customers became orchestrators, and underneath the role they became the ones trusted to judge. That is the noun.

Part 1: The Story They Tell

Ask Eoghan McCabe what happened at Intercom and he will give you a war story, because that is how he tells it.

He runs a wartime company. He came back as CEO in October 2022 to a business approaching zero net new ARR, and he decided the moment demanded creative destruction rather than caution. He picked a lane on the way in, and he read a rival’s decline as the opening. On Lenny’s Podcast, he described the read plainly: Zendesk “had been acquired a couple years prior. They were strategically, energetically, culturally dead. They were upsetting customers in the market. There’s an opportunity there. We’re doing service.” He calls it founder mode. He swapped out mature directors for startup founders who could stomach risk. He grew the AI team from a handful of people to roughly sixty, hired PhD scientists, and paid them, in his telling, aggressively above the rest of the company. He moved nearly 80% of R&D onto Fin while Fin was still a single-digit percentage of revenue, an allocation most CFOs would have vetoed. He describes a workforce that turned over substantially in the process, and he treats that churn as evidence that the company reset itself for the new fight rather than drifting into it.

He funds it on his own terms. In March 2026, he raised $250M from Hercules, and he was pointed about the structure: debt, not equity, because a company throwing off hundreds of millions in gross profit does not need to sell the upside to outside capital. Incumbency, in his frame, is a financing moat.

He killed revenue on purpose, and he did it twice. First on the old model: when he returned, he simplified legacy pricing that customers openly hated, giving away, in his telling on Lenny’s Podcast, “something like $50 million in ARR” because “when people feel like they have far simpler, more predictable, fairer pricing, they’ll stick around longer.” He ties that write-down to a value he installed on his return, that the company would be “customer-obsessed.” Then on the new model: in his own words on X in March 2026, Intercom “actively managed our entire customer base to a new, risky pricing model” and in doing so ended up “killing ~$60M ARR in the process.” He frames both as proof of conviction. Most companies protect legacy revenue. He deleted it, twice.

He says he invented outcome-based pricing. He points to $0.99 per resolution, the model “that everyone in the agent space now talks about,” and to the $1M public guarantee that Fin would hit a 65% resolution rate or Intercom would pay.

He built his own model. Apex 1.0, launched in March 2026, beat GPT-5.4 and Claude Sonnet 4.6 on resolution rate, according to the company’s numbers. He is clear about why it stays proprietary: “Pre-training is kind of a commodity now. The frontier, if you will, is actually in post-training. Post-training is the harder part. You need proprietary data. You need proprietary sources of truth.”

He renamed the company. Fifteen years of Intercom equity, retired on May 12, 2026, because the name had become “baggage” and the agent had become the company. He said the rename was there “to cap our transformation.”

He says he is the biggest and the best. Fin, in his telling, is the leading service agent by any interesting metric: roughly 8,000 to 12,000 customers, resolution rates in the high sixties to mid seventies, around 2M weekly resolutions, net revenue retention that climbed from 112% to 146%, and roughly $100M of Fin ARR inside roughly $400M total. He says Fin beats all competitors regularly in any fair fight, and that Apex is the highest-performing agent precisely because the company runs on its own model.

And he says he created a category. The Customer Agent: one agent owning the full customer lifecycle, “an intimate, warm relationship” with the end customer “from day zero to year ten.” Six weeks before selling, he told VentureBeat that “if you can’t become an agent company, your CRUD app business has a diminishing future,” a line aimed at Salesforce, and named Agentforce as a competitor. Then Salesforce agreed to buy Fin for roughly $3.6B, closing in Salesforce’s fiscal Q4 2027, and McCabe stayed on to run the division. By his own account, the market validated everything at roughly 36x Fin ARR.

The whole telling is a story of things he did and things he built. Verbs and products. He destroyed, he invented, he built, he renamed, he defined. It is the story of a man narrating his own courage, and the courage is real. What is missing from it is anyone on the other side of the transaction. In all of it, there is almost no sentence about what happened to the person who bought the thing.

This is the story Eoghan tells. It is coherent, costly, and largely true. It is also not the position.

Part 2: The Hidden Position

Intercom does not own the Customer Agent. Their customers own something else, and the customers named it first. After a year of a machine resolving the majority of tickets, the support leader becomes an orchestrator of a resolution system, and underneath that role reaches an identity: the one who is trusted to judge. That is the position, and it has two layers. Orchestrator is the role, what the buyer runs. Arbiter is the identity, who the buyer becomes. The noun Fin actually owns in customer memory is resolution, and it arrived wounded. Customers do not say it warmly. They say “resolution tax,” “assumed resolution,” “profit over customer.” The pricing innovation is also the positioning wound, and the wound lands exactly on the identity layer, because the bill charges the arbiter for exercising judgment.

The paradox has a founder’s fingerprints on it. For years, Intercom’s mission was to “make internet business personal,” and McCabe was openly anti-bot; he thought bots were impersonal. Now he argues the opposite, that the machine is the personal thing. On Lenny’s Podcast, he put it this way: “providing a customer with a highly engaged, instantly available expert, consistent, fast, charismatic, funny, friendly, personal agent available for literally every single customer every minute of the day around the clock is so much more personal than making them wait 2, 3, 4 days for a crappy canned response.” The man who refused bots on the grounds that they were impersonal now sells the most personal thing in the category as a bot. He did not stumble into that reversal. He carried the same conviction into a new instrument.

The noun has two layers stacked one on the other. The functional layer is the orchestrator: what a CX leader becomes after living with the machine resolving most of the queue. They stop running a room of humans answering tickets and start tuning, monitoring, and being accountable for a system that does the resolving. Doer to conductor. Firefighter to orchestrator. That is the role, and a role is a functional object any capable rival can produce. The identity layer sits above it. Once the machine clears the queue, the only thing left that is unmistakably the leader’s own is judgment: which case needs a human, when to override the machine, how to redraw the team around it. They become the one who is trusted to judge, the arbiter whose own function they defer to. The transformation happens in place, through the work, not at the moment of purchase, and it is only fully visible at the identity layer, because that is the part the leader feels from the inside and cannot put on a business card.

Nothing changes at the contract signing. The leader who signs is still a firefighter that afternoon. The change happens across the year that follows, as the machine takes the majority of tickets and the leader’s day empties of the things that used to fill it: the scheduling, the escalating, the apologizing for wait times. Another job fills the empty day. The leader watches resolution rates, tunes the knowledge the machine draws on, and redesigns what the human team does now that the queue no longer needs them. By the end of that year, the leader is not doing the old job better. They are doing a different job, and they have a different answer when someone asks what they do.

The customer is the worst witness to this. Ask them what they bought and they hand back “an AI agent” or “a support tool.” So read the transformation off behaviour, off refusals, off the job titles the industry is minting. Listen to the voices across both textures of the one base, the ones who came through the transformation and the ones for whom it soured:

“It has freed up our agents to focus on so many other areas of impact for our customers and has given us the space to rethink our career progression paths and the roles within our team.” (Angelo Livanos, Lightspeed Commerce)

“Even as a competitor for Fin (My AskAI), I can confidently say that Fin ranks among the strongest AI customer-service agents available… The only drawback is the cost of $0.99 per resolution.” (MyAskAI, on r/intercom)

“The ‘resolution tax’ is pissing people off. Everyone raves about the Fin AI bot itself. It actually works. But that $0.99 per resolution pricing… oof. One review literally called it a trap.” (r/SaaS)

“If a user simply closes the chat without requesting a human, Fin still counts it as resolved, even if the question wasn’t truly answered. Essentially you’re paying for false positives.” (r/SaaS)

“We simply answer the customer’s question before they can click ‘Talk to Human’ because we see it’s wrong. This is counted as an assumed resolution, and this is most definitely being billed.” (@bosbeest, Intercom Community)

“The whole company is very ‘profit over customer’ and so far, Fin has successfully resolved 100% of conversations it has been involved in (go figure).” (Trustpilot)

“Oh no, we finally let go of Fin. It was incredibly expensive and didn’t meet our needs at all.” (r/customerexperience)

The analyst class and the org charts name the transformation from the outside, without ever being sold to. Forrester’s Kate Leggett: “The role of AI and the CSR flips: AI addresses the majority of the work, while CSRs assist AI.” Gartner’s Eric Keller: service leaders must “redeploy human agents into roles that AI cannot replace and that customers value most.” Intercom’s own restructuring created an “AI operations lead, often promoted from support ops.” Salesforce describes managers “no longer just leading people, overseeing a blended workforce of humans and AI agents.” CX Network describes the shift “from observation to orchestration.” The market is minting the noun in parallel, without Fin’s permission and without Fin’s language. That is what an unclaimed but real transformation looks like.

The noun explains every decision. Killing roughly $60M of legacy ARR: seat licenses do not put the vendor at risk for failed resolutions, so they are incompatible with resolution-as-outcome, so they had to go. Moving nearly 80% of R&D to Fin: the machine that produces the orchestrator transformation is the future; the helpdesk seat is not. Building Apex and refusing to sell it as an API: the model exists to deepen the transformation inside Fin’s customers, not to become a commodity someone else deploys. Pricing at $0.99 per resolution: the vendor gets paid only when the customer’s problem is gone, which is the economic shape of an outcome. The $1M guarantee: staking cash on the metric. The rebrand: the company name now reflects what the customer becomes through, not what the company historically sold. The debt over equity: a company confident in the transformation’s cash flows does not sell the upside to outside capital. The board swap and the aggressively compensated AI team: talent and governance re-tuned around the one bet.

The counterfactuals confirm it. Suppose the real noun were “the best chatbot,” a product noun. Then killing $60M of ARR and burning the brand make no sense; you would keep the seats and bolt the bot on top. Suppose the noun were “AI lab.” Then refusing to sell Apex as an API is irrational; an API is exactly how a lab monetizes. Suppose the noun were “concierge,” Decagon’s word. Then the forward-deployed-engineer motion is the right one, and you would embrace it rather than refuse it. Only under resolution-as-outcome, with the buyer becoming an orchestrator, do all decisions line up at once. The refusals matter as much as the moves. He refused the “concierge” noun. He refused to sell Apex as an API. He rejected his rivals’ forward-deployed-engineer consulting motion, calling Fin “a product, not a consulting contract.” He refused to let cost dictate price, saying pricing should come from value and the cost is the vendor’s problem. He refused to keep a fifteen-year-old brand once it no longer matched the machine.

Remove all words.

Delete every tagline, every thread, every press release. What pattern remains? A company that voluntarily destroyed tens of millions in revenue, put the overwhelming majority of its engineering behind a product that was single digits of the business, built a proprietary model it will not monetize directly, priced itself so it earns only on success, staked seven figures on a resolution number, and burned a fifteen-year-old brand to match the agent. A forensic reader of only the P&L and the product decisions would reconstruct resolution-as-outcome without anyone stating it. The one thing that does not survive the deletion is the phrase “Customer Agent.” It lives in the words, not the decisions.

Map the territory through the noun, and every serious rival has aimed their positioning at someone other than the buyer. Decagon owns “concierge,” the white-glove framing where the end customer feels singular; the transformation Decagon implies happens to the shopper, not to the support leader. Sierra frames the brand around the buyer, who becomes a brand steward; the transformation is about the company’s voice, not the leader’s role. Zendesk claims “Autonomous Service Workforce,” a noun about the labour pool, not the person managing it. Salesforce owns “Agentforce,” a brand noun, and “AI elevates human potential,” a slogan about people in general. “Customer Agent,” Fin’s claim, is a noun about the product itself.

Stack those up, and the pattern is loud. Decagon points at the shopper. Sierra points at the brand. Zendesk points at the workforce. Salesforce points at humanity. Fin points at the product. Nobody points at the buyer. “Customer Agent” is genuinely vacant; no rival uses it, but vacancy is not ownership. No customer reaches for it, no analyst ratifies it. Forrester says “conversational AI platforms.” Gartner says “task-specific AI agents.” An empty room with your name on the door that no one has walked into is not territory you hold. The orchestrator transformation is also vacant, and none of the rivals have claimed it, as they have all aimed elsewhere. Fin, with the largest installed base and the deepest workflow embedding, is best positioned to own it, and currently does not name it. The one company whose customers most visibly became orchestrators is the one that names the machine rather than the person.

That is category transcendence available and unclaimed. “Customer service software” is a product category. The orchestrator is not a category; it is the role the buyer grows into, and the one who is trusted to judge is the identity underneath it. When the position lives in the buyer’s identity rather than in the product spec sheet, competitors can match the feature, even match the role, and still lose, because they cannot match the judgment the customer earned through years of running the machine.

Owning a category and owning a transformation differ in one mechanical way. A category can be entered by anyone with a comparable product; the moment a rival ships a bot that resolves as well, the category is contested. A transformation is entered only by the vendor whose machine the customer actually reorganized around. That is why the strongest position Fin could hold is neither “the best customer service software” nor “the Customer Agent.” It is the quiet fact that its customers became a kind of leader they were not before, and that this happened inside Fin’s product, on Fin’s data, over years the customer cannot get back by switching.

The three horizons are distinct, and collapsing them is the easiest mistake to make here. The destination is the thirty-year frame McCabe talks about: the Customer Agent owning the full lifecycle from marketing to success. That is a bet, founder-articulated, market-unadopted. The position is the ten-year noun the customer is becoming today: orchestrator of resolved outcomes at the role layer, and above it the one who is trusted to judge, freed from the queue, accountable for a machine, and reached for on the cases the machine cannot settle. That is happening now, evidenced by behaviour and by the job titles the industry is minting. The proof is what is already true and costly: Apex, $0.99 pricing, the destroyed ARR, the R&D reallocation, the guarantee, the rebrand, the exit. Destination is where he is pointing. Position is what the customer lives, role and identity together. Proof is what he has already spent to get there. They are three layers, not one.

That gap between what the customer becomes and who the customer already is leads to the next question.

Part 3: The Identity Layer

The buyer is not a demographic. The buyer is an identity under threat. For a decade, the CX or support leader has run a cost center. Theirs is the department that gets cut first, the queue that never empties, the team measured on ticket volume and CSAT while permanently understaffed. The role carries a quiet insult built into it: customer service as a stepping stone, a place you pass through on the way to something that matters more. The Lightspeed VP rejects exactly that framing when he talks about rethinking career progression paths. He is refusing the old identity out loud.

Choosing Fin says something about that leader. It says: I am a modern operator, I run AI, I stopped being a cost center and started being accountable for a system. It is an identity claim disguised as a procurement decision. The status upgrade is real, and for a while it looks like the emotional core of the whole thing. Not relief from work, though that is real too. Ascension from the person who runs the room that never empties to the person who runs an operation. But status is a stage on the climb, not the summit, and the independent evidence is precise about where the climb actually ends.

The claim is aimed at an internal audience. When the support leader walks into the executive meeting where budgets get defended, the old script was apologetic: we are understaffed, the queue is backed up, we need more headcount to hold CSAT. The orchestrator has a different script. Resolutions are automated, cost per contact is falling, and the human team has been redeployed to the accounts that move revenue. That is a leader speaking the language of the people who allocate capital, not the language of the people who get their budgets cut. The purchase buys a seat at a table the role was historically kept away from. This is why the transformation is felt as a status shift rather than merely as efficiency. Efficiency is a number in a report. Status is who gets listened to in the room, and the leader who runs the machine gets listened to differently than the leader who runs the queue.

The reverse is also true, and it is the fear the purchase quiets. The leader who does not make this shift watches it happen to them. Their headcount gets reallocated by someone above them, their queue gets automated by a decision they did not make, and their role gets redesigned around a machine they did not choose. The identity threat is not abstract. It is the specific dread of being the last cost-center manager in a company that has decided cost centers are legacy. Fin is the instrument that puts the leader on the deciding side of that line rather than the receiving side. That is a large emotional payload for a procurement line item, and it is precisely the payload the language never names.

Gartner’s own survey of service leaders reads like a field report on this identity in motion. Eighty-five percent are adding new responsibilities to frontline roles, seventy-five percent are shifting agents into entirely new roles, sixty-three percent are reducing frontline headcount through attrition while reallocating to higher-value work. Those are not numbers about a tool. They are numbers about a role changing shape underneath the people who hold it. The leader who buys Fin is buying a way to be on the right side of that shift, the one redesigning the roles rather than the one whose role gets redesigned away.

Read the register of the people living this, because it corrects a tempting error. The easy story says the buyer feels triumphant, future-proof, safe. The independent voices do not sound safe. On public forums where no one is being sold to, the dominant tone is hedged survival, not liberation. A support leader in the role writes that in the past year and a half the nature of the position has changed more than in the previous five, and that AI now handles a significant portion of what used to fill the day. A leader running AI initiatives reports no layoffs and, in the same breath, a hiring freeze across the whole department. A twenty-year veteran of the field, freshly laid off, asks whether the roles are coming back. A frontline worker says plainly that job loss feels inevitable. The word “liberated” appears nowhere. What appears instead is conditional relevance: I am on the right side of this for now, and I know the ground is still moving. That is the true emotional register, and it is quieter and more anxious than status alone.

The noun that sits above the role has to carry that register. “Orchestrator” names what the buyer runs. It is a job title, and a job title is a functional object; any competent machine produces one. The emotion above it is neither pride nor safety, because the evidence rejects both. The state the buyer actually reaches is narrower and more human: they become the one who is trusted to judge. Before Fin, they were trusted to clear a queue, an execution mandate anyone could measure by volume. After a year of the machine clearing it, the only thing left that is unmistakably theirs is judgment, which case needs a human, when to override the machine, how to redesign the team around it. They became the judgment layer of their own function. You can read it off behaviour without asking them: they intervene on the hard cases, they tune what the machine knows, they redraw the career ladders, they defend the customer against the machine’s mistakes. Every one of those is an act of discretion. The role is orchestrator. The identity is arbiter. Unlike status, which can be granted in a meeting, being trusted to judge is a state the buyer feels from the inside and cannot put on a business card, which is exactly why it sits above the functional layer.

The word carries its own precarity, and that precarity is accurate. Trust is provisional by nature. It can be withdrawn. “The one who is trusted to judge” holds the standing and the fragility at the same time, which is why it fits a buyer who feels chosen and expendable in the same year. It does not overpromise safety the market has not granted. It names the one thing the transformation genuinely confers: discretion, and the quiet authority of being the mind the machine defers to rather than the labour the machine replaced. Personally, it reads as relief from obsolescence. Professionally it reads as authority in the room. They are the same claim seen from two sides of the same person.

McCabe’s own identity built this without his noticing. He is a wartime founder, a creative destroyer, a man who thinks in costly verbs: killed, destroyed, invented, cannibalized, rewrote. That instinct is why the proof layer is so strong. He does the expensive, irreversible things because that is who he is. It is also why he names what the company did and what the product is, and almost never names what the customer becomes. The blind spot is not carelessness. It is the same identity that produced the strength.

Watch how the three lock together. His identity is destruction and conviction. The position that fell out of it is the buyer moving from firefighter to orchestrator. The product delivers exactly that. Identity, position, and product are aligned in the doing. The only misalignment is linguistic. The language names the machine.

This is the founder’s characteristic error, and it is common among the best builders. A founder who thinks in verbs describes the company by what it did. A founder who thinks in product describes it by what it built. Neither instinct reaches for the harder noun, the one that names what happened to the person on the other side. McCabe can tell you, in vivid detail, that he destroyed $60M of ARR and built a model that beats the frontier. He cannot as easily tell you that the buyer who lived with that model stopped being a firefighter. The proof is loud in his mouth. The transformation is silent. That silence is not a gap in the business. It is a gap in the language pointed at the business.

The cognitive picture is split, and this is where the wound lives. For the product, customers hold procedural knowledge: they have operated Fin, they can describe it, they concede it works. That is Hebbian learning happening cleanly, repeated experience wiring “resolves my tickets” into memory. For the category noun “Customer Agent,” knowledge is declarative only and weak. Customers can be told the phrase but do not reach for it. No wiring forms, because no lived experience corresponds to it.

Then the pricing, and here the wound is deeper than a billing complaint. The product triggers System 1 approval, fast and positive: it actually works. The pricing triggers System 2 defence, slow and suspicious. Customers audit billing logs, model cost curves at scale, coin a pejorative. “Resolution tax” is a textbook triggered-skepticism marker, and the sarcasm (“100% resolution rate, go figure”) is the defence fully activated. The defence does not aim at the product. It aims at the bill and at the definition of “resolved.” The transformation is ambivalent by construction. The same metered resolution that produces relief also produces the anxiety, because the better it works, the more it costs.

Read the loudest independent complaint closely, and the wound relocates from the wallet to the identity. On the community forum, a customer who praises the product in the same post objects to being charged when they step in: stepping in, because they know what is best for their customer, should not be penalized. Decode that. The new identity is the one who is trusted to judge. The meter bills the buyer for exercising exactly that judgment. When the customer overrides the machine to protect their own customer, the system reads the override as an “assumed resolution” and charges for it. The product makes the buyer the arbiter; the pricing tells the arbiter their judgment is a billable event to be managed. That is not a complaint about cost. It is the buyer’s core professional identity being overruled by a billing rule, month after month. The pricing does not merely tax the relief. It taxes the discretion the whole transformation is built on, which is why the objection carries a heat that a simple price gripe never would. A customer who resents the price shops around. A customer whose judgment is being priced feels disrespected, and disrespect is remembered longer than expense.

The shared identity extends across both base textures. The native-Intercom customer with high switching costs and the standalone-Fin customer layered onto another helpdesk undergo the same transformation: from firefighter to orchestrator. The texture changes only the depth and durability, how locked in they are, how satisfied. It does not change what they become. That single-noun consistency across the base is the strongest evidence the transformation is real.

There is a defence mechanism the strong positions avoid, and Fin has tripped. Explicit claims invite scrutiny. When McCabe says Fin is the biggest by every metric, or that he invented the category, the buyer’s System 2 wakes up and starts checking the claim against the bill. The quiet proof, the destroyed ARR and the guarantee, would not have triggered that. The loud claim does. This is why the product earns love, and the pricing earns audits. The customer trusts what Fin does and distrusts what Fin says about itself, and the pricing sits exactly on the seam between the two.

Which is why the tactics that built the company were never really tactics.

Part 4: The Success Mechanics

McCabe did not choose tactics that created the position. The position determined which tactics would work.

Start with distribution, because this is the one everyone gets backwards. Intercom had 30,000-plus support operations already installed. That made Fin’s deployment near-zero-CAC: the machine dropped into workflows customers already lived in, sometimes in under an hour. The reflex is to say the distribution enabled the position. It runs the other way. Because the position is resolution-as-outcome delivered into an existing operation, the installed base was the natural channel and no other channel would have proven the noun as cleanly. The position chose the distribution, not the other way around. A rival selling forward-deployed engineers and multi-month custom builds is proving a different noun, “we will consult with you,” and that is why McCabe refused that motion.

The time-to-value gap is the tell. Fin can be live on an existing helpdesk in under an hour; the consulting-led rivals take weeks or months. A founder optimizing for revenue would happily sell the long, expensive deployment, because it books larger contracts. A founder proving resolution-as-outcome cannot, because a deployment that takes months to resolve the first ticket contradicts the promise that the vendor gets paid when the problem goes away, fast. The fast deployment is not a convenience feature. It is the position enforcing itself on the go-to-market. Speed to first resolution is the go-to-market shape of the noun.

Pricing is proof, and it is the clearest costly signal in the business. $0.99 per resolution says “we get paid only when your problem is gone,” and you cannot fake that with a slogan. The number came from value, not cost. McCabe is explicit that the economics were his problem to solve, not the customer’s: “I always believe that that pricing should come from value and not from costs. The cost is our problem.” Early on the arithmetic was brutal; at launch it cost the company more to resolve a ticket than the dollar it charged. He set the price against the human baseline it replaced, roughly $20 to $30 per ticket resolved, and then against a threshold of conviction: “if someone is not prepared to pay 99 cent for us to rapidly and elegantly perfectly and excellently solve their customer’s problem, we need to wrap this up. We don’t have a business here.” That is a founder pricing the outcome and betting the model would get cheaper underneath it. Anyone can say they are aligned with customer success. Staking revenue on it, and adding a $1M guarantee on a 65% resolution rate, is costly signaling, not cheap talk. The same pricing is the wound. It punishes the relief it creates. The prouder the proof point, the louder the objection it generates, because a bill that scales with success feels like a tax to the person paying it.

The data flywheel runs through the noun. Every resolved conversation improves Apex, which raises the resolution floor, which deepens the transformation, which produces more conversations. The moat is not that the flywheel exists. It is what it feeds: the customer’s embedded operating model, the workflows and team structures reorganized around Fin.

The refusal to sell Apex as an API belongs in the same logic, and it is not merely a monetization choice. An API sale would let a competitor deploy the same intelligence into a different operation, severed from Fin’s workflows. That would turn the model into a commodity and detach it from the transformation. Keeping it product-bound keeps the intelligence and the embedding fused in one object. The refusal costs revenue today and protects the moat for the decade. That trade is only obvious once you see the noun.

The most important sentence in the evidence base is not McCabe’s. Chief AI Officer Fergal Reid wrote that intelligence is no longer the limiting factor, and noted that only a small fraction of Fin’s resolution gains came from raw model IQ. If model intelligence is commoditizing, the durable moat cannot be Apex’s cleverness. The moat is the customer’s reorganized operating model, the 30,000 support operations that have already restructured around the machine. Reid, more than anyone, has named where the position actually lives. It lives in the buyer’s transformation, not in the vendor’s IQ.

The IQ/EQ read is a high-IQ company serving the right emotion without naming it.

The capability is elite and defensible: proprietary model, evaluation and orchestration infrastructure, a decade of conversational data, installed-base distribution. The emotion the buyer needs is neither triumph nor safety; the independent voices refuse both. It is the quieter thing underneath the role: to be the one whose judgment still matters after the machine takes the queue, to be trusted to judge rather than made redundant. The product delivers exactly that. The words name the product’s identity, “Customer Agent,” not the buyer’s, “what you become.” The intersection is real in the product and absent in the language. And the pricing actively punishes the emotional payoff, billing the buyer for the very judgment the new identity is built on, turning relief into audit anxiety. That is the central misalignment, and it sits at the pricing layer, not the product layer.

That kind of misalignment is unusual. Most companies with a positioning problem have a capability that does not match the emotion; they promise something the product cannot deliver. Fin has the opposite problem, which is rarer and easier to fix. The product conveys the emotion fully. The language simply fails to name it, and the pricing ends up taxing it. Neither of those is a limit on what the machine can do. Both are choices about how the transformation is described and billed. A company can change a word and a fee. It cannot easily change what its product can do. Fin’s misalignment lives entirely in the layers that are cheapest to move.

Position strength, honestly scored. The proof layer is as strong as any company in the category, because you cannot counterfeit a voluntary revenue write-off or a proprietary model you refuse to sell. What is working accidentally is that the market is minting the orchestrator role for free, in analyst reports and job titles, doing part of the naming Fin has not done; the identity underneath it, the one trusted to judge, no one is naming at all. What is missing is Level 4: the linguistic and perceptual ownership. Fin operates at Level 3 decisively and claims Level 4 through “Customer Agent,” but the intended noun is not in any customer’s mouth, and the owned noun (“resolution”) is wounded. The proof runs ahead of the perception, and the intended noun runs ahead of both.

There is a second thing missing: the pricing wound. The strongest proof point, metered resolution, is also the mechanism that converts relief into anxiety. A customer whose bill rises because the machine works is being taught, month over month, to distrust the metric that defines their spend. That is Hebbian learning too, wiring the wrong association: success equals a bigger invoice. And the wound goes deeper than the wallet. The product makes the buyer the one trusted to judge; when they override the machine to protect their own customer, the meter reads the override as an “assumed resolution” and bills them for it. The product builds the arbiter; the bill teaches the arbiter that their judgment is a billable event to be managed. Both patterns strengthen with repetition, and they point in opposite directions. This is the one crack in an otherwise coherent position, and it is not a product crack. It is a pricing crack, meaning it is fixable without changing what the machine does.

Now the financial logic that funds the horizons, because no one has named it cleanly. The present-state position pays for the destination. Resolution-as-outcome revenue, compounding through the data flywheel and the near-zero-CAC installed base, is what funds the bet that one agent will someday own the full lifecycle. The transformation of the buyer, from firefighter to orchestrator to the one trusted to judge, is the cash engine underneath the Customer Agent dream, not a detour from it. Every dollar a customer pays for a resolved ticket is a dollar that funds the machine that might, eventually, own marketing and sales and success too. Get the present-state noun right, and the destination becomes affordable. Lose it, and the destination has nothing to run on.

The net revenue retention numbers, if the company’s figures hold, tell the same story from the accounting side. Retention climbing from 112% to 146% means existing customers spend more each year, with no new logos added. Under resolution pricing, that is what deepening transformation looks like in the ledger: the more resolutions a customer routes through Fin, the more they pay, because they reorganized more of their operation around it. The expansion revenue and the embedding are the same event seen twice, once in the customer’s org chart and once in Fin’s ARR line. The position and the P&L are one subject recorded in two ledgers.

That distinction, between what funds the decade and what could end it, is where the coaching begins.

Part 5: The Coaching Moment

I. What the filter validates and refuses

Eoghan, the noun has two layers, and you should hold both. The role your customers picked is orchestrator, and they picked it before you did; they named it in rebuilt career ladders and in the roles they redesigned around the machine. Underneath the role is the identity they actually became: the one who is trusted to judge, the arbiter their own function defers to on the cases the machine cannot settle. You earned both by doing the expensive things. The filter that produced all of it is one question you have been asking without writing it down: does this deepen resolution-as-outcome, and does it move the buyer from firefighter to orchestrator, and finally to the one trusted to judge? That question has been load-bearing since October 2022, and arguably since 2011 when you started making the support seat more capable.

Walk the decisions through the filter. Returning as CEO in 2022 to a company at zero net new ARR and refusing to defend the status quo: passes, because comfort would have protected the seat model that cannot bear resolution risk. Moving nearly 80% of R&D to Fin while it was single digits of revenue: passes, because the machine is what produces the transformation. Killing roughly $60M of legacy ARR: passes, because seat revenue is incompatible with getting paid only on outcomes. Pricing at $0.99 per resolution and staking $1M on 65%: passes, because it puts the vendor’s money on the metric. Building Apex: passes, because a proprietary model deepens the transformation you can deliver. Renaming the company to Fin: passes, because the company name now matches what the customer becomes through.

Now the refusals, which prove the filter harder than the moves. You refused to sell Apex as an API, leaving real revenue on the table, because an API turns the model into a commodity someone else deploys and severs it from the transformation. You refused the “concierge” noun, because it names the end customer’s feeling, not your buyer’s identity. You refused the forward-deployed-engineer consulting motion, because a consulting contract sells hours, not resolved outcomes. Every refusal is coherent under the one noun and incoherent under any other.

State the boundary plainly. This filter belongs inside the company. It governs who you hire, where capital goes, what the roadmap builds, which partnerships you take, and what you say no to. It does not belong on a billboard. The moment you put “orchestrator” on external copy, you invite the System 2 defence you already fight on pricing. The identity layer, the one trusted to judge, is more internal still; it is felt from the inside by the buyer and cannot survive being said back to them as a slogan. The filter is an internal instrument. Keep it there.

The reason this matters now is that the filter has been unconscious. You applied it by instinct, because it is who you are. Instinct is fragile at scale and fragile through an acquisition. What was obvious to a founder-led team of a few hundred is not obvious to a division inside a company of tens of thousands. Making the filter conscious does not mean announcing it. It means being able to say, in a roadmap review, that a feature was cut because it deepened the seat model rather than the resolution outcome. It means a hiring panel that can name why one candidate fits the orchestrator thesis and another does not. The filter survives contact with scale only if someone can articulate it in the room.

II. The connection most readers miss

The second-order consequence, the one you may not have said out loud: the durable moat is not Apex.

Reid already told you this: intelligence is no longer the limiting factor. If he is right, and the resolution gains that came from raw model IQ were a small slice, then the thing competitors cannot copy is not your model’s cleverness. Frontier Labs will keep closing the IQ gap. What they cannot close is that 30,000 support operations have already reorganized themselves around Fin. The career ladders were redrawn. The org charts sprouted an AI operations lead. The reporting shifted from agent occupancy to resolution economics. That reorganization is the asset. The customer’s transformation is the moat.

This is why the flywheel matters more than it looks. Every resolved conversation is not just training data. It is another increment of a customer operating model that is now shaped around your machine and expensive to unwind. The near-zero-CAC installed base was never only cheap distribution. It was the fastest possible path to embedding 30,000 operating models before anyone else could.

Think about what a rival would need to reproduce to catch up to you, and in what order. They could license a frontier model tomorrow and match Apex on raw resolution within a year, because that is the layer that commoditizes. They cannot reorganize 30,000 support operations around themselves on any timeline they control, because that transformation runs at the speed of the customer’s own change management, not the vendor’s engineering. You have already paid that time. It is spent and banked. A competitor starting today is 30,000 org-chart redesigns behind, and those redesigns happen inside companies the competitor does not own.

And it is why the financial logic holds. Resolution-as-outcome revenue funds the lifecycle bet because the revenue and the moat are the same object. You do not spend on customer acquisition to feed the flywheel, and you do not spend on a model you then give away. The money the customer pays for resolved tickets funds the machine, and the machine deepens the embedding that produces the next dollar. A competitor with a better model and no embedded base has the IQ and not the moat. You have both, and only one of them is copyable.

The reader who runs a support org already knew this half-knew it. They felt the switching cost in their bones and called it lock-in. What they were feeling was the transformation, hardened into an operating model.

The runway is larger than the category label suggests, and you have said as much. On Lenny’s Podcast, you argued that “CX is deceptively large given it’s hidden behind just two words,” that it is really “service success, sales and marketing,” and that it is “the biggest part by headcount of any business.” Read that against the orchestrator noun and the decade opens up. The transformation you have already produced in support leaders is the same transformation available in every adjacent function where a human currently runs a queue of repetitive work. The filter that moved the support leader from firefighter to orchestrator moves the same way in success, in sales operations, in any role built around a backlog. That is not a new bet. It is the existing noun with more rooms to enter.

There is a sharper version of the point, and it is uncomfortable. The “Hotel California” complaints, the customers who stay because leaving costs more, are not a flaw in the moat. They are the moat showing its brittle side. A customer who reorganized around Fin and now resents the bill is still embedded, still reorganized around the machine, still expensive to unwind. That is loyalty by lock-in rather than loyalty by love, and it holds until a rival offers the same transformation without the resentment. The embedded operating model is the asset. The resentment is the liability sitting on top of the same asset. Both come from the same pricing mechanism, which is why pricing is the one thing within your control that determines whether the moat compounds or erodes.

III. The Salesforce acquisition is not a marketing moment

Salesforce agreed to buy Fin for roughly $3.6B on June 15, 2026, and you stay on as CEO of the division. This acquisition is where positioning becomes most structural. Get it right and the decade gets easier. Get it wrong, and it gets more expensive.

Get it right and three things happen. Fin defines the Customer Agent category on its own terms inside the world’s largest CRM distribution engine, at a scale you said yourself you could never reach alone. The 30,000 reorganized support operations stay the moat, because Salesforce protects the embedding rather than flattening it. And “Customer Agent” survives as the concept Salesforce paid a category premium for, roughly 36x Fin ARR, a multiple that priced a concept and not a revenue line.

Get it wrong, and three things happen. Fin dissolves into Agentforce as a SKU, a fast-time-to-value module inside someone else’s platform. “Customer Agent” fades into Benioff’s language and the premium erodes into a footnote. And the orchestrator transformation goes unnamed and undefended, so the moat quietly decays as the embedded operating models start to feel like a feature toggle rather than the machine accountable for their outcomes.

The irony is instructive. Six weeks before the deal, you said that if you can’t become an agent company, your CRUD app business aimed at Salesforce has a diminishing future, and you named Agentforce as a competitor. The competitor became the owner. That only becomes a defeat if the concept dissolves inside the acquirer.

The base rate here is not friendly. Acquired products usually get absorbed into the acquirer’s language, because the acquirer’s language is what the sales force already knows how to sell. Salesforce framed Fin as the packaged, fast-time-to-value complement to the deeper, customizable Agentforce platform. Read plainly, that framing describes a feature, not a category. The gravity of a company that large pulls everything toward its own noun. Resisting that pull is an operating discipline, not a marketing exercise: which team owns the resolution metric, which roadmap decisions stay bound to outcome pricing, whether the 30,000 embedded operations keep being served as operations or start being served as seats inside a bigger suite.

Apply the discipline hardest here. The moment is not when Fin starts saying the noun externally. Nothing about this acquisition should make you put “orchestrator” on a slide, and less still the identity underneath it. The moment is when the implicit proof you already built becomes legible to a much larger audience that did not have to be told. Benioff’s press-release line, that Fin will “complement Agentforce,” is the erasure risk written in plain sight. The thing Salesforce paid $3.6B for was never the code. It was the 30,000 support leaders who reorganized around Fin and became the ones their own operations trust to judge.

IV. The diagnostic, handed back

The distinction to hold is between the label and the transformation. If “Customer Agent” the phrase fades and the 30,000 support operations keep being served as accountable resolution machines, you have lost a word and kept the moat. If the phrase survives on a slide but the operations get flattened into an Agentforce module priced by seat, you have kept a word and lost the moat. Guard the transformation, not the vocabulary. The vocabulary was always the least durable layer.

You do not need me to answer these. You need to ask them this quarter about your executive team and your Salesforce counterparts.

Does our hiring filter for orchestrator-fit, for people who deepen the buyer’s standing as the one trusted to judge, or are we hiring people who will optimize for revenue mix and quietly protect the seat model we already killed once?

Does the pricing model still punish the relief it creates, and if a customer’s bill rises precisely because the machine works, what stops “resolution tax” from following us inside Agentforce?

What protects the 30,000 embedded operating models when Fin sits inside Salesforce, and who owns defending that moat when the integration pressure is to make Fin a module?

Is “Customer Agent” structurally internal, governing what we build and what we refuse, or is it a press-release term we stopped applying as a filter the day it went into the announcement?

Who, by name, owns the resolution metric inside the combined company, and does that person have the authority to refuse a roadmap decision that would deepen a seat model at the expense of the outcome?

Those questions are not rhetorical, and they are not for a marketing team. They are for the people who set headcount, allocate capital, and approve the roadmap. If the answers are clean, the filter is alive and the decade is yours to keep playing. If they are fuzzy, the filter has already started to fade, and the fade is invisible until a competitor names the transformation you left unnamed.

Eoghan, your customers became orchestrators, and underneath the role they became the ones trusted to judge. Resolution-as-outcome is the filter that made them. Keep it inside the company and keep applying it.

Uncover your position

Every founder can read another company’s label. No one can read their own. That is what this analysis does: it names the noun your customers already live, and the filter you have been using without writing it down. If you want to run this on your own company, the CEO Clarity Starter Kit and Monopoly walk you through finding the noun you own, the level you operate at, and the transition that carries the next decade.

Read more Gravity Reports.