Every enterprise software stack 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 marketing team has a dashboard nobody opens. The CX team toggles between six tools and none of them tell anyone what to do next. The instinct is to fix this with more discipline — pick one tool, force adoption, build a better dashboard. 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. That is what agents are for. The same architecture works for the GTM gap between ad click and revenue, and for the operations gap that the ERP never closed.
I broke this argument into seven atomic posts. Read them in any order:
- The Mesh of Specialists Pattern — Not one mega-agent. A fabric of small, single-purpose agents coordinating through shared context.
- GTM Mesh: Closing the Gap Between Ad Click and Revenue — Static landing pages cannot fix it. A mesh of enrich, route, content, analytics agents can.
- The ERP Is Dead. The Agent Is Your Operating System Now. — The agent becomes the operating layer on top of every system you already paid for.
- Inspectable Logic, Not Black Box Magic — Agent logic should be permanent, inspectable code. Not a regenerated prompt.
- Start With the Pain, Not the Platform — Pick a model first and you get a demo nobody adopts. Start with the workflow that hurts.
- The Pilot Is the Product — Do not wait for perfection. Pilot with three users. Their complaints are the backlog.
- The Human Is No Longer the Integration Layer — The systems of record are not going away. The human as the operating system between them is.
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 — judgment up, drudgery down, integration handled by software that runs the way software is supposed to run.
— Ry
Sources
Related Essays
The Pilot Is the Product
Do not wait for perfection. Pilot with three or four users. Let them complain. Their complaints are the backlog. The pilot is not a test — it is the first iteration of the production system.
Start With the Pain, Not the Platform
The temptation with agent projects is to start with the technology. That is how you end up with a demo that impresses nobody who actually has to use it.
The Operationalization Gap: Where AI Demos Go to Die
The gap between an AI demo and an AI deployment is called software engineering. Most organizations are not equipped to close it, and that is where all the value lives.
Key takeaways
- The real bottleneck in enterprise software is not missing data — it is humans context-switching across six systems to act on it.
- The same mesh-of-specialized-agents pattern works for GTM (routing between ad click and revenue) and operations (replacing the ERP dashboard).
- In GTM, agents collapse the time between first touch and qualified pipeline from days to seconds by enriching, routing, and personalizing in real time.
- In operations, agents pull from HubSpot, Metabase, and Fathom to deliver a prioritized daily plan in Slack — and write updates back to source systems.
- Agent logic should be inspectable code, not opaque prompts, so the team can challenge and evolve the prioritization algorithm.
- The agent does not replace your CRM or your ERP. It becomes the operating layer on top of them — the interface humans actually use.
FAQ
What is a mesh of agents?
A mesh of agents is a fabric of small, specialized programs that each do one job well and coordinate through shared context. Instead of one mega-agent doing everything, each agent observes state, applies logic, and hands off to the next — with humans reviewing the outputs that matter.
Why should agent logic be code instead of prompts?
Code is inspectable, versionable, and evolvable in ways prompts are not. When a sales leader asks why a lead was routed to self-serve, you need to point at a function — not a regenerated prompt. That transparency is what earns trust and prevents the system from getting ripped out.
How do agents replace the ERP without replacing the CRM?
The agent does not replace the systems of record — it becomes the operating layer on top of them. HubSpot stays the data layer, Metabase stays the analytics layer, and the agent synthesizes both into a prioritized daily plan delivered in Slack. Humans stop being the integration glue between six tools.