Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

YPO Technology Network AI Brief

YPO Technology Network AI Brief artwork

Stop Picking Tools. Start Assigning Layers.

Aug 22, 202615 minAudio
ShareXLinkedInFacebookWhatsAppEmail

The same question keeps arriving from Milan, from Singapore, from Chicago. We are paying for Microsoft Copilot and we are paying for Claude. Which one should we standardize on? It sounds like a procurement question and it never is. This weekend edition takes the question apart and replaces it, because the honest answer is that it collapses two completely separate decisions into one: where your people think, and where the work lands. In this episode, Stephen Forte covers: New survey work from Recon Analytics covering more than 150,000 US respondents: where an employee has Copilot and nothing else, 68 percent use it. Where Copilot sits next to two alternatives, it takes 8 percent and ChatGPT takes 70. Same product, same people, and the only variable is whether they had somewhere else to go. Why that is a preference verdict rather than a quality verdict, and why preference is the one thing a policy cannot overrule. The researchers' own conclusion: distribution advantages do not lock in market position. An honest note on what that survey does and does not measure. It covered Copilot, ChatGPT and Gemini. It did not measure Claude at all. Where BuildClub itself sits, stated up front: we use all of them, and most of our heavy lifting runs on Claude. What each tool is genuinely better at. Copilot posts to Teams, attaches files to the emails it drafts, and can start working because an email arrived. Claude does none of those three. Claude writes and runs code. Copilot does not, and that single difference explains most reports of Copilot underperforming. The four-layer architecture that replaces the tool question: the interface, the hands, Teams, and the large population of people who are never leaving Outlook and should not be asked to. The one thing Microsoft deliberately will not let a machine do, and why they were right to draw that line. The workaround, and why it produces better governance rather than worse: a named owner, an accountable human, and nothing pretending to be a colleague. An invented but familiar scenario, a six-hundred-person industrial packaging firm with offices in Milan and Chicago, whose managing director is being asked to standardize by people who have already decided. One honest limitation, stated plainly on air: the moment Claude reads your content, that content has left your Microsoft tenant. Newer architectures keep it inside and are more limited today. You can have one or the other right now. Sources: Recon Analytics, "AI Choice 2026: Why Licenses Don't Equal Adoption," February 2026. Survey of 150,000+ US respondents, July 2025 to January 2026, paid AI subscribers. Microsoft Graph v1.0 reference, "Send chatMessage in a channel or a chat." The application permission is Teamwork.Migrate.All only, with the note that application permissions are supported for migration only. Microsoft Learn, "Copilot Cowork overview," "Use plugins with Copilot Cowork," and "Extend Microsoft 365 Copilot." Anthropic, "Microsoft 365 connector" documentation, for the documented limits on what Claude can and cannot do against Microsoft 365. Referenced: episode 131, "Your AI Tools Don't Share a Brain." The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. AI Vendor Keys: Cursor's Breach And Why Agent Logs Are Sensitive Data

    Nov 20, 20267 minAudio

    Cursor's breach didn't start with a bug in the app. It started with an access key Cursor issued to a vendor, Fireworks. That key opened old coding-agent session logs, some still holding pasted credentials, which led...

    Credit the people on this episode

  2. AI Plumbing: Microsoft Just Ran The Pipes Through Your Tenant

    Nov 19, 20267 minAudio

    Microsoft Ignite's biggest news was plumbing: who each agent is, who it reports to, what it can touch and what it costs, built into the Microsoft 365 tenant you already pay for. Satya Nadella called Agent 365 Business...

    Credit the people on this episode

  3. AI For CEOs: Hear What The Summary Leaves Out

    Nov 18, 20266 minAudio

    Episode 200. Stephen started this show because almost nobody was talking to CEOs about AI: plenty of tabloid headlines and valuations, little on where the technology is going, what a busy CEO needs to know, and how to...

    Credit the people on this episode

  4. AI Always-On Agents: The Real Risk Is They Break Silently

    Nov 17, 20266 minAudio

    On 13 November 2026, Anthropic published a guide on agents that keep working when nobody is in the chat. Always on is the experience, not staying awake all night. The agent sleeps, wakes for a short run, saves what...

    Credit the people on this episode

  5. AI Vendor Risk: When Outlook Goes Down, Your Agents Go With It

    Nov 16, 20266 minAudio

    Microsoft's Outlook and much of Microsoft 365 went down late Thursday 12 November and were not fully restored, by Microsoft's public account, until Saturday morning 14 November. Microsoft says this was a technical...

    Credit the people on this episode