Saturday, October 24, 2026 AI news, turned into opportunities PDF newsletter
AI Opportunity Daily
Subscribe
Healthcare AICybersecurityJobsAI agents

AI beats GPs on hard cases, AI agents hit a supply chain, and Amex cuts 5% for AI

A peer-reviewed study in Science says Microsoft's diagnostic AI solved far more hard medical cases than generalist doctors, Microsoft says a China-aligned group used an AI hacking framework to move at 'machine speed' through an IT vendor, and American Express is cutting about 5% of its staff to get ready for automation. The common thread: AI is now strong enough to change how expert work, attacks and org charts are designed, and the people who prepare the ground around it are the ones who get paid.

Key takeaways

  • Microsoft's MAI-DxO solved about 83% of 304 hard simulated cases against 36% for generalist doctors with references, but most of the gain comes from the underlying model and real-patient trials have not started.
  • Microsoft says Storm-0940 used the ARTEX AI framework to abuse trusted ConnectWise app identities and attempt sign-ins to more than 2,250 Microsoft 365 tenants, with some breaches taking under three hours.
  • American Express is cutting about 5% of its workforce with a $336 million charge to flatten management before automating, and will only let outside AI agents in through approved API or MCP channels.
Story 1 of 3Research5 min read

Microsoft's diagnostic AI solves 83% of hard cases in a Science study, versus 36% for generalist doctors

A peer-reviewed paper in Science reports that Microsoft's MAI-DxO, a panel of cooperating AI agents, correctly diagnosed about 83% of 304 complex New England Journal of Medicine cases, against about 36% for generalist physicians using reference materials. The tests were simulations, and specialists were not in the comparison.

Microsoft's AI unit has published its diagnostic system, MAI-DxO, in the journal Science. The paper, "Sequential diagnosis with language models", appeared on 22 October. MAI-DxO is an orchestrator: it makes several AI agents behave like a panel of doctors with different roles, deciding what to ask a patient, which tests to order and when to commit to a diagnosis. On 304 difficult case records from the New England Journal of Medicine, turned into step-by-step simulated encounters, the system reached the correct diagnosis about 83% of the time. Primary care doctors and general internists working alone with reference materials got about 36% right, according to TechCrunch and other coverage of the paper.

The study also tested 325 emergency department cases from Beth Israel Deaconess Medical Center in Boston, where reports put MAI-DxO at about 80% against roughly 47% for physicians. The benchmark, called SDBench, gives the participant a short summary and makes them pay, in estimated dollars, for every question and test. The best results came when MAI-DxO ran on OpenAI's GPT-5 and GPT-5.5. With GPT-5.5, complex-case accuracy rose from about 72% for the model alone to nearly 87% with the orchestrator, at slightly lower estimated cost. A weaker model, Gemini 2.5 Flash, jumped from 46.4% to nearly 69%.

This is the peer-reviewed version of work Microsoft first released as a preprint in June 2025, when it claimed up to 85% accuracy. The figures have changed, so the Science numbers are the ones to use. Microsoft is not alone: Google and OpenAI have also claimed their systems can match or beat doctors on some tasks, and Google's AMIE was separately studied with Beth Israel in real urgent-care visits. Mustafa Suleyman, who runs Microsoft AI, called the result a step towards "medical superintelligence" and said he expects healthcare models to get an order of magnitude better within 24 to 36 months. Microsoft is also building a healthcare foundation model with the Mayo Clinic.

The caveats are large. These were simulations built from published past cases, not live patients with vague symptoms and missing records. Complex cases like these are normally handled by specialists or teams, who were not compared. All 15 authors work for Microsoft. And the paper's own data suggests most of the improvement comes from the stronger underlying model, not the orchestration: on emergency cases, GPT-5.5 scored about 85% with or without MAI-DxO. Cost savings are estimates from a uniform price list, not measured hospital spending, and one independent analysis found the emergency-case cost was higher than the physicians'. No product or release date has been announced.

The practical takeaway is that structured, step-by-step clinical reasoning by AI is now strong on paper, and the next phase is proof in real hospitals. Beth Israel will run a study in which consenting patients receive normal care and also interact with MAI-DxO, so its recommendations can be compared with clinicians'. For health systems in places with few specialists, including much of Africa, the promise is obvious, but so is the risk of deploying tools validated on US case records. Until local trials and regulators catch up, the safest near-term uses are in training, case review and decision support where a qualified clinician stays in charge.

Why it mattersIt is the strongest peer-reviewed evidence yet that AI can reason through hard diagnoses step by step while tracking test costs, and it shows the base model matters more than the wrapper around it.

👀 What to watch

Results from the Beth Israel hospital study, any regulator guidance on diagnostic AI, and whether Microsoft turns MAI-DxO into a product through its existing clinical tools.

3 opportunities from this story

1

A case-based diagnostic reasoning tutor for medical and clinical-officer students

Medium⏱ 4–8 weeks💰 Monthly student subscriptions plus annual institutional licences for colleges and exam-prep providers.

Build a practice tool that walks students through cases the way SDBench does: a short summary, then questions and tests that each carry a cost, then a final diagnosis with feedback. Medical schools and colleges training clinical officers and nurses need far more practice cases than their tutors can run. Microsoft's paper shows the sequential, cost-aware format works well for AI, and frontier models can now play the patient and grade the reasoning. This is education, not patient care, so the regulatory bar is much lower.

Best for
Doctors and clinical officers who code or can partner with a developer, ed-tech builders, medical student associations.
First step this week
Write 10 practice cases based on common local presentations (with a clinician co-author) and run them through a frontier model as a simulated patient to see where it fails.
Open the full playbook
Launch steps
  1. Recruit one or two clinicians to write and review cases relevant to local disease patterns.
  2. Build a simple flow: case summary, question and test ordering with a running cost, final diagnosis and scored feedback.
  3. Pilot free with one class or study group and track whether scores improve.
  4. Add exam-style modes and a tutor dashboard before pitching colleges.
Tools
Claude or GPT APIA no-code app builder or Next.jsGoogle Forms for pilot feedbackStripe or M-Pesa payments
Risks

AI can state wrong medical facts confidently, so every case and answer key needs clinician review and a clear 'for education only' label. Colleges buy slowly; start with students directly and use results to win institutions.

2

Local test sets to evaluate health chatbots before they reach patients

High⏱ 2–4 months💰 Fixed-fee evaluation projects, with repeat fees when the client updates its model.

Health startups, NGOs and hospitals are rolling out symptom checkers and clinical assistants validated mostly on US data. Offer to build SDBench-style evaluation sets from properly anonymised local cases, then score their tools on accuracy, safety and cost of tests ordered. Microsoft's study made this kind of structured benchmark respectable, and funders increasingly ask for evidence before scaling a health AI pilot. You sell the measurement, not the medicine.

Best for
Health data scientists, public-health researchers, monitoring-and-evaluation consultants.
First step this week
Draft a one-page evaluation offer and ask three health-tech startups or NGOs what evidence their funders want before they scale.
Open the full playbook
Launch steps
  1. Partner with a hospital or research group that can grant ethics approval and access to anonymised case notes.
  2. Convert 50–100 cases into step-by-step scripts with agreed correct diagnoses.
  3. Build a harness that runs a client's chatbot through each case and logs answers, tests and red flags.
  4. Publish a short methods note to build credibility, then sell evaluations.
Tools
PythonSpreadsheet or REDCap for case curationClaude or GPT API for simulated patientsA secure cloud workspace
Risks

Patient data rules are strict: you need ethics approval, data-protection compliance and true anonymisation. Projects take time to set up; secure one anchor client before investing heavily.

3

AI-use policy and training packages for private clinics

Low⏱ 2–3 weeks💰 Fixed fee per clinic for policy plus workshop, optional quarterly refresher.

Clinicians are already pasting cases into general chatbots, and studies like this one will make that more common. Small private clinics rarely have written rules on which tools are allowed, what patient data can be shared, how to record AI-assisted decisions or how to get consent. Offer a short package: a policy template, a staff workshop on safe use and verification, and a simple log for AI-assisted decisions. It reduces risk for the clinic without anyone claiming the AI is a doctor.

Best for
Health administrators, clinicians with management experience, compliance and data-protection consultants.
First step this week
Draft a two-page clinic AI-use policy covering approved tools, data sharing, verification and record-keeping, and show it to two clinic managers for feedback.
Open the full playbook
Launch steps
  1. Review your country's data-protection law and any medical council guidance on digital tools.
  2. Write the policy template and a one-hour workshop with real examples of AI errors.
  3. Run one discounted pilot and collect a testimonial.
  4. Sell through clinic networks, insurers or professional associations.
Tools
Google DocsCanva for slidesClaude or ChatGPT for draftingA simple logbook template
Risks

You are not giving legal or medical advice; partner with a lawyer for the data-protection section. Guidance from regulators may change, so date your templates and update them.

Story 2 of 3Security5 min read

Microsoft: China-aligned hackers used the ARTEX AI agent framework to breach a supply chain at 'machine speed'

Microsoft says Storm-0940, a China state-aligned group, used ARTEX, an open-source multi-agent AI penetration-testing framework, to take over trusted ConnectWise cloud app identities and attempt sign-ins to more than 2,250 Microsoft 365 tenants. In several cases it reached privileged cloud access in under three hours.

Microsoft published a report on 21 October attributing the recent compromise of ConnectWise's Cloud Backup service to Storm-0940, a China state-aligned group active since 2021. What makes the case stand out is the tool. Microsoft says the group ran its operation through ARTEX, an open-source penetration-testing framework in which multiple AI agents handle reconnaissance, password attacks and privilege escalation with little human input. Microsoft says ARTEX let the attackers "accelerate the activity to machine speed". In multiple cases, less than three hours passed between first targeting an organisation and gaining privileged access to its cloud infrastructure.

The numbers in Microsoft's report are specific. Between 10 and 14 October, infrastructure linked to the group ran an automated password-spray campaign against 327 accounts at eight organisations, generating more than 151,000 failed logons and peaking at 2,900 failures a minute on 11 October; Microsoft saw no successful logins from that spray. The real damage came through ConnectWise. The attackers gained control of the identities of several ConnectWise cloud applications, which customers had already trusted inside their Microsoft 365 tenants, then tried to sign in to more than 2,250 tenants. One chart shows over 200 sign-ins in under four minutes using four app credentials.

Because the attackers logged in as trusted applications rather than as people, no interactive user sign-in was needed, so the usual user protections such as login prompts were not in the path. Inside some tenants, Microsoft says, the agents ran reconnaissance through Microsoft Graph, added new app credentials for persistence, changed groups and privileged roles, read secrets in bulk from Azure Key Vault, and in one case had an app grant itself Global Administrator. ConnectWise published its first advisory on 16 October and suspended several services, including Cloud Backup, according to SecurityWeek. Security firm Huntress reported access to hundreds of tenants.

Some details are still unclear. Reports differ on how many customers were actually compromised, as opposed to targeted: the 2,250 figure is sign-in attempts, and ConnectWise has not given a final count. Coverage also disagrees on whether ARTEX remains openly available. Microsoft's attribution has not been independently confirmed, and China typically denies such claims. Microsoft says multiple threat actors in different regions are using ARTEX, and SecurityWeek notes that CrowdStrike, Zscaler and Recorded Future had earlier linked similar AI-powered activity to attacks on South Korean financial institutions. Zscaler published its own technical analysis of the tooling.

The lesson for everyone else is that supply-chain apps are the soft spot, and AI makes exploiting them fast. Most small and mid-sized firms have dozens of third-party apps with standing permissions in their Microsoft 365 or Google Workspace accounts, and few ever review them. Microsoft's advice is concrete: keep affected ConnectWise connections disabled, preserve logs before deleting anything, inventory apps by application ID, review service-principal sign-ins back to 1 October, revoke unneeded permissions, rotate credentials and monitor for new credentials or role changes. That is ordinary hygiene, but at machine speed there is no time to do it after the fact.

Why it mattersIt is one of the clearest documented cases of a state-aligned group using an AI agent framework to run a real supply-chain intrusion, and it targeted the trusted third-party apps most businesses never audit.

👀 What to watch

ConnectWise's final count of affected customers, whether ARTEX stays publicly available, and whether Microsoft and Google tighten default permissions for multi-tenant apps.

3 opportunities from this story

1

Fixed-price Microsoft 365 third-party app permission audits

Low⏱ 1–2 weeks💰 Fixed fee per tenant sized by user count, plus paid remediation hours and an optional quarterly re-check.

Most small businesses have never looked at which outside apps hold standing access to their email, files and directory. Offer a fixed-price audit that inventories every enterprise app and service principal, flags excessive permissions and stale consents, and delivers a short fix list. The Storm-0940 case gives you a concrete, well-documented story to open every sales conversation. The work uses free admin tools and Microsoft's own published checklist.

Best for
IT freelancers, Microsoft 365 administrators, small IT support firms.
First step this week
Run the audit on your own or a friendly client's tenant using Microsoft Entra's enterprise apps view and write up the findings as a one-page sample report.
Open the full playbook
Launch steps
  1. Build a checklist from Microsoft's mitigation list: app IDs, permissions, consent grants, credentials, role assignments.
  2. Script the export with Microsoft Graph PowerShell so each audit takes hours, not days.
  3. Create a plain-English report template with red, amber and green findings.
  4. Offer it to existing clients first, then to accountants, law firms and clinics.
Tools
Microsoft Entra admin centerMicrosoft Graph PowerShellExcel or Google SheetsClaude for report drafting
Risks

You need admin access, which requires trust and a written scope; use a simple engagement letter. Removing the wrong app can break workflows, so recommend changes rather than making them without sign-off.

2

App-identity monitoring alerts as a monthly service for IT providers

High⏱ 6–10 weeks💰 Per-tenant monthly subscription sold to IT providers, with volume discounts.

Microsoft's report says the warning signs were new credentials on apps, privilege changes and unusual app-only sign-ins. Build a lightweight monitor that watches client tenants for exactly those events and sends a clear alert. Managed service providers handle many tenants and would pay for something simpler and cheaper than a full security operations centre. This is a product that grows with each tenant you add.

Best for
Developers with Microsoft 365 or security experience, small managed service providers.
First step this week
Write a script that pulls Entra audit logs for one tenant and flags new app credentials or role assignments from the last 24 hours.
Open the full playbook
Launch steps
  1. Define five high-signal alert rules based on Microsoft's guidance.
  2. Build log collection through Microsoft Graph with secure, least-privilege access.
  3. Send alerts by email, Teams or WhatsApp with a one-line 'what to check' note.
  4. Pilot free with one IT provider for a month and tune out noisy alerts.
Tools
Microsoft Graph APIPython or Node.jsA small cloud databaseTeams or WhatsApp webhooks
Risks

Your tool itself becomes a privileged app and a target, so secure it carefully and request minimal permissions. Large security vendors already offer this, so compete on price, simplicity and local support.

3

'AI-speed attack' tabletop exercises and log-readiness setups

Low⏱ 2–3 weeks💰 Fixed fee per exercise, plus a follow-on fee for implementing log retention and playbooks.

Many firms only discover during an incident that their logs were not kept long enough or that nobody knows who can disable a vendor app. Run a half-day tabletop exercise built around the ConnectWise scenario, then fix the gaps: log retention, an app-disable playbook and a contact list. Microsoft's advice to preserve evidence before deleting apps is exactly the kind of step teams get wrong under pressure. It suits boards and managers who want assurance without a big project.

Best for
Security consultants, IT trainers, risk and compliance professionals.
First step this week
Turn Microsoft's timeline into a 10-step exercise script with decision points and test it with one small team.
Open the full playbook
Launch steps
  1. Write the scenario with timed injects: spray alerts, vendor advisory, suspicious app activity.
  2. Prepare a scorecard on detection, decision speed and evidence preservation.
  3. Deliver the session and a short gap report.
  4. Offer a fixed-scope fix package for the top three gaps.
Tools
Google Slides or PowerPointMicrosoft Purview audit settingsA shared playbook documentClaude for scenario drafting
Risks

Exercises without follow-through feel like theatre; always end with a concrete fix list. Avoid overstating the threat to sell work, and keep the scenario tied to published facts.

Story 3 of 3Business5 min read

American Express cuts about 5% of staff with a $336 million charge to 'prepare for AI', and sets rules for outside agents

American Express will eliminate about 5% of its global workforce, roughly 3,500 jobs according to CEO Stephen Squeri, and take a $336 million restructuring charge. Its CFO says the aim is to remove management layers so processes can be automated later, and the company will only let third-party AI agents in through approved API or MCP channels.

American Express disclosed on Friday, with its third-quarter results, that it expects to eliminate about 5% of its positions worldwide and take a $336 million pretax restructuring charge. CEO Stephen Squeri put the figure at about 3,500 jobs, according to reports citing Bloomberg; outlets that applied 5% to the nearly 77,000 staff Amex had at the end of 2025 estimate closer to 3,800. Chief financial officer Christophe Le Caillec told CNBC the goal is to make the company "leaner, more agile, and also to prepare for AI." Part of the cost is funded by the gain from selling its stake in Global Business Travel Group.

The explanation is more specific than the usual 'AI took the jobs' framing. Le Caillec said Amex wants to reduce management layers and widen spans of control first, because "you don't want to automate processes that are not optimally structured." In other words, the cuts are groundwork for automation rather than a direct swap of people for software. The results themselves were solid: revenue rose 9% to about $20.1 billion, adjusted earnings per share were $4.68 against analyst expectations of $4.48, and Amex raised its full-year earnings guidance. Gen Z cardholders' US spending grew 35% in the quarter. Shares still fell 2–3% in early trading.

Amex also laid out how it will treat outside AI agents, a growing question for every company that handles payments or bookings. Squeri said the company is "not going to let assistants run rogue through our system" and will only allow agents that come through approved API or MCP channels; MCP is the open protocol many AI assistants use to connect to tools. Agents will not be allowed to repeatedly query its Resy restaurant booking service in ways that disadvantage other cardholders. Amex says it is developing purchase-intent authentication and protections for cases where registered agents make mistakes, and it is working with OpenAI on an Amex Offers plugin.

There are reasons for caution in reading this as pure AI disruption. Squeri presented the cuts as an efficiency move taken from strength and did not attribute the whole reduction to automation, and companies often give several reasons for layoffs at once. The exact job count differs between sources. Agentic payments are still small, Squeri said, and he called it too early to judge how AI will affect costs. Gartner has predicted that half of companies that cut staff because of AI will rehire by 2027, often under different job titles. Amex is also not alone: Barclays confirmed this week that it plans to cut about 5,000 jobs, roughly 5% of staff, in a technology-driven cost programme.

For workers and small firms, two signals matter. First, large employers are now restructuring before they automate, which means demand is shifting towards people who can map, simplify and document processes, and away from layers whose job is mainly passing information along. Second, big merchants are drawing hard lines on how AI agents may interact with them: approved APIs and MCP connections in, scraping and uncontrolled bots out. Any business that wants AI assistants to book, buy or query on its customers' behalf will need a proper, permissioned interface, and many smaller businesses have no idea how to build one.

Why it mattersA highly profitable company is cutting staff explicitly to prepare for automation, and one of the biggest card networks has set a template for how AI agents must connect to merchants.

👀 What to watch

Which roles Amex actually cuts, whether other banks and card networks adopt similar API-or-MCP-only agent rules, and how its purchase-intent authentication works in practice.

3 opportunities from this story

1

'Fix it before you automate it' process redesign for SMEs

Low⏱ 1–3 weeks💰 Fixed fee per process mapped, with optional implementation of the first automation.

Amex's CFO said the quiet part out loud: automating a messy process just makes a faster mess. Offer small and mid-sized firms a short engagement that maps one core process, removes unnecessary hand-offs and approvals, documents the clean version, and then identifies which steps AI can safely take over. Owners hear about AI daily but rarely know where to start, and a process map gives them a concrete, low-risk first move. Your deliverable is a clear map and an automation shortlist, not a promise of savings.

Best for
Operations consultants, business analysts, freelancers who have worked in finance or customer service.
First step this week
Map one process you know well, such as invoice approval or customer onboarding, and turn it into a before-and-after sample to show prospects.
Open the full playbook
Launch steps
  1. Create a one-page intake questionnaire and a standard mapping template.
  2. Interview the staff who actually do the work, not just managers.
  3. Deliver a simplified process, a list of steps to remove, and a ranked automation shortlist.
  4. Offer to build the first automation or refer it to a trusted developer.
Tools
Miro or WhimsicalGoogle DocsClaude or ChatGPT for drafting SOPsZapier or Make for first automations
Risks

Staff may fear the work signals job cuts, which can make interviews guarded; be clear about scope with the owner. Avoid promising specific cost savings you cannot measure.

2

Build MCP connectors that make small businesses agent-ready

Medium⏱ 3–6 weeks💰 Setup fee plus a monthly hosting and maintenance fee per business.

Amex will only let AI agents in through approved APIs or MCP, and other large companies are moving the same way. Smaller merchants, from restaurants and salons to tour operators and shops, have no structured way for an AI assistant to check availability, prices or bookings. Build and host simple, permissioned MCP servers that expose a business's catalogue and booking system safely, with rate limits. As more customers ask assistants to book or buy for them, being reachable this way becomes a new kind of visibility.

Best for
Web developers, agencies that already build sites for small businesses, booking-system resellers.
First step this week
Build a read-only MCP server for one business's menu or price list and test it from Claude Desktop or another MCP-capable assistant.
Open the full playbook
Launch steps
  1. Learn the MCP specification and build a read-only demo using an open-source SDK.
  2. Add authentication and rate limits so bots cannot flood the business.
  3. Connect to common booking or inventory tools your clients already use.
  4. Sell to existing website clients as an add-on, with a live demo.
Tools
MCP TypeScript or Python SDKCloudflare Workers or a small VPSClaude Desktop for testingThe client's booking or POS API
Risks

Consumer use of AI agents for local bookings is still early, so demand may lag; position it as a cheap add-on rather than a big project. Poor security could expose customer data, so start read-only.

3

Reskilling cohorts for back-office and middle-management staff

Low⏱ 2–4 weeks💰 Per-seat cohort fees, plus private cohorts sold to companies.

Amex and Barclays are removing layers whose work is coordination and reporting, and smaller firms will follow. Run short, practical cohorts that teach these workers to become the people who design and supervise AI workflows: process mapping, prompt-based automation, checking AI output and documenting controls. Sell to individuals worried about their jobs, and to employers who would rather retrain than fire. Keep it hands-on, with each participant automating one real task by the end.

Best for
Trainers, HR consultants, experienced managers who already use AI tools daily.
First step this week
Design a four-session outline around one capstone project and pre-sell five seats through LinkedIn or a professional association.
Open the full playbook
Launch steps
  1. Define the outcome: each participant documents and automates one task from their job.
  2. Build four sessions with templates and live practice.
  3. Run a small pilot cohort at a reduced price and collect before-and-after examples.
  4. Package a corporate version for HR teams planning restructuring.
Tools
Zoom or Google MeetChatGPT or ClaudeZapier or MakeNotion for course materials
Risks

Courses do not guarantee jobs, so never promise placement or income. The market is crowded; differentiate with a real capstone and local, sector-specific examples.

Get these as a PDF every 3 days

Free. One email every 3 days. Unsubscribe any time.

More editions