AI Dev Community · Video recap

Intercom bet 90% of the company on a product earning 1% of revenue, renamed itself Fin, and sold to Salesforce for $3.6B. Now 94% of its code is written by Claude

WeAreDevelopers WWC26 · ~33 min incl. Q&A · Watch on YouTube
Note: Des Traynor, co-founder and Chief Strategy Officer of Fin (formerly Intercom), opening day two of WWC26 Berlin. This recap is based on cleaned auto-generated captions, so treat exact numbers with care; all figures are the speaker's own. The acquisition price appears twice in the video with two values ($3.2B in the intro, $3.6B from Traynor); Traynor's own figure is used here.

The short version

In August 2022 Intercom had five straight quarters of slowing revenue growth, and ChatGPT had just made its human help desk product look obsolete. They put 90% of the company on an AI support agent, Fin, that was under 1% of revenue at the time; today Fin makes over $100M of the company's $400M+ revenue, the company renamed itself Fin, and Salesforce agreed to buy it for $3.6B.

On the engineering side: productivity tripled, 94% of code is written by Claude, and the fully loaded cost of shipping a feature keeps falling even at $180k a week in token spend. The idea worth stealing: reliability compounds, so a chain of 99%-reliable agent steps yields an ~85%-reliable product nobody buys, and evals, not UI, are where the engineering work now lives.

Key takeaways

1

Three inconvenient truths

AI will make your product irrelevant (unless it was born after 2023), your real competitors are startups founded today rather than the incumbents you benchmark against, and slow adapters die. Some product categories stop needing to exist at all; his (deliberately fictitious) example is status-update and project management tools, which lose their point once AI connects Slack, GitHub, and the rest directly.

2

Products merge and converge

When the UI becomes "tell us what you want and we'll do it," queries stop respecting product boundaries ("show me which of my best performing sales reps take the most holidays" spans the HR tool and the CRM). Everyone building an agent is suddenly crossing seven or eight product lines. His scoping advice: stop where you hit a different buyer, a different level of data permission, a brand you'd need to rebuild, or a really popular product you don't want to fight.

3

Chat is the end of the usability gap

The old world split people who know what they want from the few who know which menu does it (his example: conditional formatting in Excel versus just asking for negative cells in red). Their product Operator works this way: upload a PDF of a product launch and say "update all the documentation," and it works out which docs change where. He's blunt about the implication for his own former craft, design: it's not obvious what role classic design systems have left.

4

Reliability compounds, and that's the whole game

A single agent step at 99% reliability sounds fine; multiply a realistic workflow of such steps and the agent lands near 85%, which nobody buys. Getting from the 80% an enthusiastic weekend with Claude gives you to the 99.99% a sellable product needs is the hard part, and he sees startups announce the homepage before discovering this. Big companies too: he points to a product announced in 2024 that still hasn't shipped.

5

Most improvement is invisible

Fin resolved about 25% of support conversations at launch; now it's around 75%. Nothing in the UI changed, which leaves marketing with nothing to screenshot: the product simply does what it always claimed, more often. Intercom's famous product principles had to be abandoned wholesale; deterministic build-ship-measure became a messy loop of "what is possible, how reliable can we make it, can we productize it, how do we improve it after we see real-world performance."

6

New muscles

Empirical evaluation, scientific rigor, causality, prompting, and post-training their own models (plus about 15 small language models running alongside them). Design flipped from iterating on one expensive direction to exploring many directions in parallel, then refining the winner.

7

Designers ship to production

A hard rule since last August: everyone learns to deploy. Designers no longer file UI tickets, they fix them; they vibe code the roadmap as interactive prototypes shared with customers; they own the front end entirely. In his words, the decade-long "should designers code" debate is over, "because coders don't even code. Claude codes."

8

Engineering tripled

Their CTO targeted doubled productivity before Claude Code's breakout; they tripled it, measured as features shipped to production and used by real people. They also measure individual engineers' AI adoption against output, which he admits nobody likes.

The numbers

  • Revenue over $400M; Fin over $100M of it; Salesforce acquisition at $3.6B
  • 90% of the company worked on Fin when it was less than 1% of revenue
  • Fin's resolution rate: ~25% at launch, ~75% today, with no UI changes
  • Engineering productivity tripled; backlog halved; 2x user-facing changes shipped; 5x faster merges; code quality up after an initial dip; less downtime
  • 94% of code written by Claude, and 20% of that also approved by Claude
  • ~$180k per week spent on tokens, yet fully loaded cost per shipped feature (salary plus tokens) is monotonically decreasing
  • The Bun anecdote: Jarred Sumner rewrote Bun in Rust in 11 days solo, against an internal estimate of three senior engineers for a year

Caveats

All figures are the speaker's own, from a talk with no external write-up to check against, and this recap is built from auto-generated captions, so treat exact numbers with care (the acquisition price itself appears twice in the video with two different values). Traynor is selling a worldview along with the story: he runs the company whose pivot he's praising, and the talk names no failed bets or costs beyond "some people hated it." In the Q&A he concedes real limits of the say-what-you-want UI: recurring tasks want buttons, Photoshop wants sliders, and "make it slightly darker, again" is nobody's idea of a good interface. He also distinguishes intelligence-hungry use cases (drug discovery), which benefit from every frontier model, from intelligence-full ones (enterprise ticket tracking), where today's models suffice and you should stabilize and post-train rather than chase releases.

Why it matters for Teams AI builders

This is what the AI transition looks like from the C-suite of a company that actually made it through, and the operational details match what this community sees on the ground: evals as the core engineering discipline, invisible reliability work displacing feature launches, designers deploying, and cost-per-feature as the metric that justifies heavy token spend. The compound reliability arithmetic is the most immediately usable piece: before you agentify a workflow, multiply out the per-step reliabilities and see whether the product you'd get is one anyone would pay for. And the "intelligence-full vs intelligence-hungry" split from the Q&A is a sharper way to decide whether to chase every model release or lock in and optimize.

Join the discussion

▶ Watch the full video

Traynor claims measuring per-engineer AI adoption against productivity was controversial but necessary once token spend hit $180k a week. If your org plotted every engineer on that chart tomorrow, would you defend the metric or fight it? And a second one from his Q&A: he splits AI use cases into two groups, those where today's models are already smart enough for the job (his example: enterprise ticket tracking) and those still waiting on smarter models (his example: drug discovery). Which of your products or internal tools are already in the first group, where chasing the next model release buys you nothing?