The Model Isn't the Moat

I spent Thursday at AI//FORWARD, and one thesis from the conference has stayed with me since I left the room.

The companies that win the agentic AI era will not be the ones with the best model.

They'll be the ones that built the best harness around it.

That's not a contrarian take for its own sake. It's the operational reality that practitioners are arriving at as they move agentic AI from experiment to infrastructure. The model is increasingly commoditized. Frontier advantage is measured in months, not years, with open source closing fast. The durable value, the thing that's actually hard to copy, is the layer you build around the model: tools, prompts, evals, guardrails, memory, observability, routing, policy enforcement, workflow logic.

That's your IP. Not the model subscription.

The governance problem nobody wants to talk about

Most of the agentic AI conversation is still about capability. The conversation at AI//FORWARD was about control, and the gap between where most organizations are and where they need to be.

Every agent running in production should have a registered use case, a risk tier, a named business owner, a defined review date, and a kill switch. That's not bureaucracy. That's operational hygiene for a system that can act on your behalf, at scale, with real consequences. The teams that skip this step aren't moving faster, they're deferring cleanup to a future incident.

And this is where the leadership problem starts to look like an architecture problem. If jobs are bundles of tasks, then every agentic workflow is also a talent decision. Which tasks are delegated to software? Which tasks stay with people? Which tasks become inspection points, judgment calls, or coaching moments?

The harness has a human side

The companies that build the best harness around AI will also be the companies that rebuild the first rung of career development. AI is absorbing a lot of the low-risk work people used to learn from: summarization, formatting, basic research, routing, first-pass analysis, status updates. None of that work was glamorous, but it gave junior people reps. It taught context, communication, value creation, and what good looked like.

If you automate those reps away without replacing them, you do not just get efficiency. You get a thinner apprenticeship system. The first rung still exists, but it is higher, narrower, and more demanding. That should change how leaders think about AI adoption. The question is not only "how much work can this agent do?" It is "what capability are we still building in the people around it?"

A real enterprise AI harness therefore includes more than tools and guardrails. It includes simulations, manager review, feedback loops, progressive challenge, and enough productive friction for people to develop judgment instead of outsourcing it before they understand the work.

More autonomy is not the goal

This one cuts against the dominant narrative, so I'll say it plainly: the right target is minimum viable autonomy for the use case. More autonomy means lower consistency, weaker process adherence, higher monitoring burden, and cost curves that can quickly outrun the value the agent was built to deliver. Multi-turn agentic workflows can cost 10x to 100x a single LLM call. Poorly designed agents can outspend the humans they were meant to replace.

The enterprise-safe pattern for multi-agent systems isn't autonomous peer-to-peer swarms. It's narrow sub-agents with scoped permissions, defined responsibilities, and logged handoffs. That architecture maps directly to security, audit, and compliance, which means it's the pattern that actually survives contact with the rest of your organization.

The better operating model is task-level decomposition. Stop asking whether AI can replace a job and start asking which tasks it can do, assist, accelerate, or reshape. Then assign responsibility deliberately: what the AI drafts, what a human inspects, what a human decides, and where the workflow should slow down because context is non-negotiable.

AI fluency is not expertise

There is a dangerous mirage of competence around AI. A weak plan can look polished. A shallow analysis can arrive with bullet points, citations, and executive tone. A junior employee can produce something that looks senior before they have the business acumen to know whether it is right.

That is not an argument against AI fluency. It is an argument for treating fluency as the floor, not the ceiling. The scarce asset is still knowing what matters, asking better questions, interpreting weak signals, making tradeoffs, and connecting work to outcomes. AI leverage without that layer is just faster output.

This is also why digital teammates need managers, not just users. Leaders have to learn how to delegate to both people and machines: where to accelerate, where to inspect, where to force reflection, and where accountability can never be handed off.

Vendor lock in has moved

It used to be: which model are you locked into? That's the wrong question now. The new lock in is at the harness layer, agent runtimes, workflow builders, managed memory, tool ecosystems, eval stacks, enterprise control planes. Vendors know the model is a commodity and they're building sticky infrastructure around it.

The strategic response is simple to articulate and hard to execute: keep model optionality, make your prompts, tools, skills, and workflows portable, and treat your harness assets as strategic IP. Don't let a vendor own your operational layer. And do not let the vendor's polish become a substitute for your own expertise. Portability matters for systems, but it also matters for judgment.

Two things I'd add

Start capturing high-quality agent trace data now. The talk made this point about SLMs, smaller language models fine-tuned on your own agent logs, and it's correct. Today's operational data is tomorrow's fine-tuning asset. Teams that aren't logging structured traces are leaving that value on the table.

I would capture the human side of that trace too: what reviewers changed, where agents needed coaching, which judgment calls stayed with people, which tasks became reliable enough to delegate, and where the organization still needed better reps. That is not just compliance data. It is the map of how your expertise formation system is actually working.

Agentic AI is no longer a research problem. It's an operations problem. The infrastructure you build around the model, governance, harness, cost controls, portability, talent development, and human accountability is the work that compounds.

The talent formula is becoming AI leverage plus real expertise plus judgment plus business context plus communication. The companies that win will not simply automate junior work away. They will use AI to manufacture better reps, build stronger digital teammate workflows, and preserve the scarce human capabilities that make the harness worth trusting.