Every enterprise has the same dirty secret. The systems they paid millions for are half-adopted, inconsistently updated, and quietly hated by the people who use them. The CX team toggles between HubSpot, JIRA, Airtable, Metabase, Intercom, and Outlook, and none of them tells anyone what to do next.
The ERP was supposed to solve this. It did not. The dashboard everyone was supposed to live in is the dashboard nobody opens. The instinct is to fix this with discipline — pick one tool, force adoption, run training. That instinct is wrong. The problem is not which tool. The problem is that humans should not be the integration layer between their own systems.
What works is an agent that pulls from every tool the team touches, synthesizes the state of the world, and delivers a prioritized daily work plan where people already live. For most teams that is Slack. Every morning at 9 AM each team member gets a message — here are your priorities, here is why, here is what is overdue, here is what is escalating. Not a notification. A reasoned work plan built from the actual state of their accounts, tickets, and revenue data.
Then the team member works. They make calls, resolve tickets, have meetings. Instead of toggling back into HubSpot — which is where adoption dies — they tell the agent what happened. The agent writes it back to the source systems. The touch gets logged. The ticket gets closed. No context switching.
This is the same mesh of specialists running in a different domain. Data-collection agent. Prioritization agent. Delivery agent. Capture agent. Each one inspectable, each one composable. HubSpot stays the data layer. Metabase stays the analytics layer. The agent becomes the operating layer — the thing that turns data into action and action back into data. The ERP is not going away. The human as the operating system between six systems is.
— Ry
Sources
Related Essays
The Human Is No Longer the Integration Layer
The ERP is not going away. The CRM is not going away. The landing page is not going away. But the human as the operating system between them is. The agent takes that job now.
The Mesh of Specialists Pattern
One mega-agent does not work. A fabric of small, single-purpose agents — each doing one thing with high confidence — coordinating through shared context does.
The Unit of AI Consumption Is the Organization
Today every developer has a personal subscription. Tomorrow the organization has a shared agent fabric — pooled credits, role-based access, routed across models.
Key takeaways
- The ERP failed not because the data is wrong but because humans are the integration layer between six systems.
- An agent that pulls from every tool and synthesizes a prioritized daily plan in Slack is what the ERP was supposed to be.
- When the agent listens to the human and writes back to source systems, adoption stops dying at the data-entry step.
- HubSpot stays the data layer. Metabase stays the analytics layer. The agent becomes the operating layer.
FAQ
Does this replace HubSpot or Salesforce?
No. Systems of record stay where they are. The agent sits on top, pulls from each system, applies logic, delivers prioritized work to humans, and writes results back. The CRM keeps being the database. The agent becomes the interface humans actually use.
Why does adoption die at the dashboard?
Because dashboards are read-only. They tell you what is happening but not what to do next. And updating them after a customer call requires toggling back into a tool nobody likes. The agent inverts that — it tells you what to do, then captures the result conversationally.