All posts

Intercom Built a Manager for Its AI Agent. You Should Build the Whole Layer.

Fin Operator is the back-office brain for Intercom's customer-facing agent. That second-layer problem, how to supervise AI at scale, is where founders should start building next.

May 16, 20262 min read
A raw black-and-paper punk-style illustration of a large control tower supervising multiple AI agents in sequence, with thick arrows and radiating lines showing a management layer.

The Front-Line Agent Was Just the Start

Intercom just rebranded itself as Fin and announced something that sounds small until you think about it. Fin Operator is an AI agent whose entire job is to manage Fin, the customer-facing AI agent. While the industry obsesses over the large language model that talks to users, Intercom is quietly building the layer behind it. That layer is where the real product work lives.

Most builders are still wiring up a single chatbot and calling it a day. But once that bot is live, someone has to configure it, watch it for drift, and fix it when it starts giving wrong answers. Fin Operator is essentially back-office software for your own software. It is a new product category that most people have not named yet, and that makes it a wide open space for founders.

Every AI Product Needs a Control Room

The real work of running AI in production is not the demo. It is the operations. Human support teams already write playbooks, review tickets, and adjust workflows. AI agents need the same supervision. Fin Operator is an admission that the chat interface is only half the product. The other half is the control room that keeps it from going off script.

For indie hackers and small teams, this is an opening. You do not need Intercom's budget to build a management layer. You need a backend that can track agent runs, store conversation traces, and let a human or another agent step in. A reactive database with real-time queries and durable workflows handles this out of the box, which is why we built Botflow on Convex. The control plane is a full-stack problem, and it is one you can ship in days.

Think about what Fin Operator actually does. It configures the front-line agent, monitors its behavior, and improves it over time. Configuration means routing rules and prompt versioning. Monitoring means real-time dashboards and alerts. Improvement means feedback loops and retraining triggers. Each of those is a distinct feature set you could build and sell this weekend.

Build the Layer Beneath the Hype

The enterprise fight is moving from model benchmarks to orchestration. Anthropic, OpenAI, and Microsoft are all racing to own the agent control plane. But they are building general infrastructure. Specific industries need specific control rooms. A healthcare AI needs compliance monitoring. A fintech AI needs audit trails. A logistics AI needs exception handling. None of those are one-size-fits-all, and that is the gap.

This is exactly where founders should look. Instead of wrapping another API call in a chat interface, build the tooling that keeps an agent honest. Ship a trace viewer for customer support bots. Build a goal-checker that stops an AI from marking a task done before it actually compiled the code. Create a human-in-the-loop dashboard for appointment setters. These are narrow, urgent problems with real budgets attached.

Intercom's move proves that the next job to automate is managing the automations themselves. Someone has to steer. If you want a product idea with real momentum, stop building the bot that chats and start building the cockpit that flies it.