Manifesto Architecture Projects Insights Resources Engage →
All Insights
AI Strategy

AI Stopped Being a Chatbot.
Nobody Sent a Memo.

Something's shifted in the last few months that I don't think has fully landed for most businesses yet, even ones that consider themselves fairly AI forward. The mental model a lot of people still carry is "AI is a chat window you ask questions in." That model was accurate for a while. It's not anymore, and the gap between what people think Claude can do and what it actually does now is wider than most people realize until they see it firsthand.

The honest version of where things are: Claude has quietly moved from assistant toward something closer to a junior operator. Not a replacement for a person, nobody serious is claiming that, but something that can sit inside a real workflow, read what it needs to, act on it, and hand off the part that genuinely needs a human's judgment. With a human still reviewing the important stuff, that's a meaningfully different category of tool than a chat box.

Why this snuck up on people

Partly because each individual improvement looked small on its own. A bit more reliable at coding. Slightly better at sticking with a long task without losing the thread. Web search built in instead of bolted on. None of these sound like headlines by themselves. But stack them and you get something different in practice: a system that can actually carry a multi-step piece of work from start to finish, not just answer a question about it.

"It doesn't show up in a product announcement. It shows up the first time you hand it something genuinely annoying and it just does it correctly, including the boring parts."

What this actually looks like day to day

Market research that used to mean a half day of open tabs now happens inside a single workflow. Draft proposals that used to take a first pass and then a cleanup pass now mostly need the cleanup pass. Debugging that used to mean stepping away from the actual problem to go searching for the error message now happens inline, with the context already loaded. Customer notes from a dozen different calls getting synthesized into one summary instead of living scattered across whoever happened to take notes that day.

None of this is one giant dramatic capability. It's the accumulation of a lot of smaller ones reaching a point where they compound into something that genuinely changes what a small team can take on without hiring ahead of where they actually need to be.

The build versus buy question this reopens

This is the part that matters most for any business trying to decide where to actually spend effort. For years, the safe default was buy. A SaaS tool covers most of what you need, the other slice you just live with, because building your own version of even a small tool was weeks of work that rarely paid for itself.

That math has moved. If a piece of software covers most of your workflow but the missing piece is exactly where your business does something nobody else does, building that piece yourself is no longer the expensive option it used to be. The break even point that used to favor buying nearly everything has shifted meaningfully toward building the specific parts that are actually yours.

What this doesn't mean

Throw out your tools. It means the slice of "things we just accept aren't quite right because building our own would be too much work" just got a lot smaller, and it's worth actually walking through what's sitting in that slice for your business specifically.

Where the human still matters, and matters more

None of this is an argument for full autonomy, and frankly the businesses getting the most out of it right now are the ones who haven't tried to remove the human entirely. The work that benefits most from this shift is the kind that's repetitive but still needs a real decision somewhere in it. The triage, not the verdict. The first draft, not the final word. The system flags what needs attention, a person makes the actual call.

That's the design that holds up. The teams pushing hardest for full autonomy everywhere tend to be the ones who end up walking it back six weeks later, once they've found the one case the agent handled confidently and wrongly. The ones treating this as a genuinely capable junior operator who still checks in on anything that matters, those are the deployments still running cleanly months later.

If your business has spent the last year thinking of AI as a slightly smarter search box, it's worth a second look. The chatbot framing made sense for a while. It doesn't really describe what's available anymore.

Still thinking of AI as a chat window?
Let's find your junior operator use case.

Bring us the workflow that's repetitive but still needs a real decision in it. We'll show you honestly where a system can carry the load and where a person still should.

Start the conversation →