Microsoft's new Copilot looks just like Claude. That's not the part that matters.

Microsoft relaunched Copilot with Home, Code and Autopilot. It looks a lot like Claude, but the real story is distribution: Microsoft is already inside the business.

Microsoft's new Copilot looks just like Claude. That's not the part that matters. — title card, livain.com

Microsoft relaunched Copilot on Friday, and my first reaction was that it looks as though they've copied Claude. There's a Home tab where Chat and Cowork live side by side, a Code tab where you build apps by describing them, and an Autopilot tab for an agent that keeps working when you don't. If you've spent the last year in Claude or ChatGPT, you'll recognise every screen.

I read the announcement, watched Microsoft's launch video and recorded my take. Here's where I land, and why I think the resemblance is the least interesting part of the story.

What Microsoft actually launched

In Microsoft's own words, the new Copilot has three parts. Home is the starting point where Chat and Cowork come together, with Word, Excel and PowerPoint built right into Copilot. Code lets non-developers build dashboards, workflows and internal apps in plain language, on the same technology as GitHub Copilot. Autopilot is a persistent agent with its own identity, memory and workspace inside your tenant, and you reach it with an @mention in Teams or Outlook.

Home and Code roll out to Microsoft's Frontier program first, and Autopilot goes to private preview at the end of the month. The agentic parts are billed on usage rather than a flat seat price.

Yes, it looks like Claude

The resemblance isn't a coincidence. Earlier this year Microsoft said it was bringing the technology platform that powers Claude Cowork into Microsoft 365 Copilot. And Microsoft's Copilot chief Jacob Andreou acknowledged to CNBC that adding coding to the app is Microsoft playing catch-up.

I don't see that as a weakness. It's a very Microsoft move: arrive later than the market, rebuild what everyone else already built, and make it feel native to the tools people use all day. Anyone who has been trying Claude or ChatGPT over the last year now finds the same patterns inside the suite their company already pays for. The learning curve will be short.

One thing I'd still change. Microsoft keeps Chat, Cowork and Autopilot as separate modes, and you have to switch between them. I'm still looking for the one tool that takes whatever I type and works out on its own whether it's a quick question, a job for Cowork or a routine for my assistant. I wrote about that same friction when Claude merged Chat and Cowork, and the line between chat and agent is still the hardest part of these products to get right.

Autopilot is the part I'd watch

Of the three, Autopilot is the one that excites me most. It's an assistant that works on your behalf even when your laptop is closed: the weekly report, the monthly review, the follow-up nobody remembers to send. Microsoft's own example is running a supplier review.

That example says a lot. It's not a writing prompt or a coding demo. It's procurement, the kind of process that runs through the middle of real businesses.

The moat isn't the product

This is where Microsoft is far ahead of everyone else. They are already inside the business. They sit in supply chains, in procurement, in finance, in the email and calendars of most large companies. Try convincing a company that runs on the Microsoft suite to move everything to Anthropic or to OpenAI. That's a hard sell, no matter how good the other product is.

And there's the part people underestimate: Microsoft's sales force. Its account managers already own the relationship with these companies and can position Copilot as a core product that plugs into their systems. It's the same logic I wrote about in why a me-too product can still win if you already own the customer.

The opportunity is large. According to CNBC, fewer than 7% of Microsoft's 450 million commercial Office 365 seats pay for Copilot today. That's not a product problem you solve with features. It's an adoption problem, and adoption is exactly where Microsoft's reach does the work.

As Tim Brown puts it in Change by Design: new products may be doomed for all sorts of reasons, from uneven quality and unimaginative marketing to unreliable distribution or unrealistic pricing.

Microsoft has the distribution covered. What decides this launch is the rest of that list.

The organisational work nobody mentions

Rolling this out in a large company isn't a licence switch. Code gives everyone the power to build their own tools. That's great until you have thousands of people building little apps across the business, each on whatever data they happen to have access to. Without training and clear ownership, you get a sprawl of tools that nobody maintains and numbers that don't match. I've seen the lighter version of this with documents already: polished AI output that shifts the work onto whoever opens it.

This is where experience matters more than the tool. The companies that get value out of Code and Autopilot will be the ones where someone with real domain knowledge decides what gets automated, on which data, and who owns it. The tool makes building cheap. It doesn't make judgement cheap.

Would I switch?

Not anytime soon. I haven't tried the new Copilot yet, and that's the big caveat on everything above. I work on the Google suite, my business runs on Claude, and Claude already works well with PowerPoint and Excel. Switching would be a steep move for me.

But I'm not the target customer. For the many companies already running on Microsoft, this could be a real game changer. Microsoft rarely ships something half done, and if they execute well, they have a winner on their hands.

The product looks like Claude. The distribution doesn't look like anyone else's.

Sources & further reading

External

Related posts

Subscribe to Remco Livain

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe
Work with me →×