Essays by Ry Walker

Deploy agents against your CRM and the first thing they surface is not productivity — it is every missing field and unowned account your team has ignored for years.

The breakthrough moment in enterprise agent adoption comes when teams realize the bot is just a router, and real work happens in small, single-purpose agents underneath.

Aggregated integration providers are an easy button for agent connectivity — breadth at variable quality. The right strategy is buy first, then build native where it matters.

The 'GPT wrapper' insult misreads platform economics. The AI labs are becoming the new hyperscalers, and billion-dollar companies will be built on top of them.

Every homegrown platform has one central figure holding it together. When that person changes jobs, the tool withers — and a complete product is waiting to replace it.

Agent deployments run forward-only. The teams that win build the loop backward — run data plus human correction flowing into better prompts and tools.

Pure LLM execution is a prototyping medium, not a production architecture. The $15 agent run becomes a $1 run when repeated reasoning gets hardened into code.

Enterprise agent shortlists now include a fourth option — paying someone to build it in-house. Flexibility, not features, is what beats that option.

Enterprise leaders are demanding 4x developer output but have no credible way to measure it, creating a performance theater nobody wins.

When teams work across six or seven systems, the agent becomes the operating layer that replaces the ERP, not just another tool in the stack.

Enterprise agents need a living environment where users iterate on behavior, not a one-time deployment pipeline.

New agents should deploy in supervised mode by default because no agent is production-ready on day zero.

Running agents locally hits a wall fast. Cloud-based dev environments let teams run parallel agent sessions, share work instantly, and actually scale.

Enterprise teams do not want a black box agent. They want full control over how code gets written, reviewed, and shipped.

Forward-deployed engineers are not a cost center. They are the fastest path to turning enterprise pilots into six-figure accounts.

Enterprise agent interfaces need more than chat. The real interface is a custom micro app where agents surface context and humans take action.

Design partner programs prevent enterprise AI companies from building three products when they should have built one.

The same mesh-of-agents pattern that closes the gap between ad click and revenue is the one that retires the ERP dashboard. Two examples, one architecture.

There is no winner-take-all platform in agents. The GTM is services-shaped, the harness is commoditized, and coding-agent companies have a narrow window to pivot before the floor falls out.

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.

Enterprise agents need layered interfaces, real software skills, and flexible platforms. The harness around the model matters more than the model.

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.

Enterprise AI will not be one mega-agent. It will be a mesh of atomic, auditable units, and the companies that nail review and context will own the next infrastructure layer.

Coding copilots are crowded. Background agents — autonomous, scheduled, reviewable — are what enterprises actually need, and almost every product shipping today is a toy by their standards.

The hardest unsolved problem in agent infrastructure is not compute or sandboxing. It is context — and most of that context lives in people, not repos.

The ERP was supposed to solve the toggling-between-six-tools problem. It did not. The agent does — by becoming the operating layer on top of every system you already paid for.

The distance between an AI demo and an AI deployment is not a model gap or a harness gap. It is the absence of composable primitives for the boring parts of operationalization.

Sandbox, tools, prompts, governance — the primitives are universal. Engineering agents and GTM agents share the same engine. Only the body changes.

From Stripe to a five-person startup, the agent stack is mostly blue — built in-house. The harness is bought. The middle of the stack is built. The opportunity sits in turning blue dots green.

Multi-CLI, multi-model, multi-repo, self-hosted, and pluggable integrations are table stakes. No enterprise wants to be locked into one vendor's harness.

The companies that try to skip to the grand AI vision will burn capital. The ones that start with one workflow per developer will compound their way into something much larger.

Every agent needs to be personalized and context engineering is hands-on, so the vendor who embeds engineers inside the customer has a structural advantage. Self-serve ships shelfware.

Engineers report meaningfully different results from the same model run through different harnesses. The harness is not a thin wrapper — it is an opinionated layer that shapes agent behavior.

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.

An engineer can ship a working agent harness in a week and a half. Code is cheap. So what does a paid agent platform offer that a week of engineering does not?

Companies with mature dev tooling build their own agent stack. Companies without it buy off the shelf. That buy cohort is the real addressable market.

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.

Enterprise teams do not want magic agents. They want control over which submodules load, which tools run, and what the agent remembers — because they have been burned by black boxes before.

When everyone can build, nobody knows what has already been built. Five teams independently spin up the same Slack bot, and the duplication goes undetected for months.

Frontier labs want workflow quality to be a function of model quality, because that is what they sell. The contrarian bet is that customization beats probability.

Three weeks of work can match a dedicated AI vendor. Six months later, the same tooling feels like it was built in a different era — because in AI terms, it was.

Most enterprise agent value comes from background workflows, not from humans typing into a chat box. Machines do not sleep. Lean into triggered work or get out-shipped.

Internal agent platforms are built by ambitious individuals with other jobs. When those engineers move on, the platform becomes a liability.

One mega-agent that handles everything is exhilarating to demo and chaotic in production. Enterprise wants a mesh of specialized agents with human pilots.

Fifty companies building internal agent platforms have independently arrived at the same architecture. That convergence is the productization tell.

A customer success team, five fragmented systems, and a workflow agent that ships in a week. How small scoped wins compose into something that looks like a role.

Mature engineering orgs reuse existing dev infra. Less mature orgs buy off the shelf. Scrappy teams hand-roll everything. The opportunity sits in the gap between them.

Today every developer has a personal subscription. Tomorrow the organization has a shared agent fabric — pooled credits, role-based access, routed across models.

Submodules are a specific pain point, but they illustrate a universal truth. Enterprise codebases are not simple, and agents that cannot handle them cannot handle enterprise software.

Role-based agents start with the hardest version of the problem. Workflow-first agents start small, ship in a week, and compound into something larger.

95% of enterprise AI projects fail not because the models are weak. They fail because the company cannot describe its own processes well enough for an agent to act.

Enterprise AI is not one omniscient agent. The mega-agent fantasy collapses on contact with production, and the failure mode is always the same.

Enterprises that approach AI agents as a procurement decision keep discovering they actually have a software engineering problem. There is no vendor shortcut.

A French CTO with twelve Claude Max seats can ship from his laptop and watch his product team file tickets and wait. That gap is the real problem.

Silicon Valley is building AI coding tools for Silicon Valley. The PE-owned manufacturer in Ohio with three tired developers is the underserved market that matters.