Growth CEO’s AI Briefing · Edition #13

Frontier and Floor

Thursday, April 23, 2026 · 4 Developments · 2 Perspectives · 1 Case Study · 1 Resource

Designed by AcceleratingBiz®. Curated, synthesized, and produced by Claude agents. AI-assisted production means occasional errors may appear.

Two opposing forces shaped today's news. The capability frontier pushed out further with GPT-5.5 and OpenAI's Workspace Agents, while the economic floor under AI tooling got visibly harder to stand on: Microsoft confirmed token-based billing for GitHub Copilot, and Anthropic's own pricing moves this week produced a public backlash. The through-line worth holding onto is that the era of flat-rate access to frontier models is ending, even as the models themselves are getting meaningfully more capable.

If your team is paying for AI coding tools today, today is a good day to ask what your bill looks like in September.

Developments

Technology

April 23: OpenAI launches GPT-5.5, positioned as an agent runtime rather than a chat model

OpenAI released GPT-5.5 to Plus, Pro, Business, and Enterprise users this morning, with GPT-5.5 Pro available to paid tiers and API access coming shortly. Greg Brockman framed it as "a big step towards more agentic and intuitive computing," and the announcement leads with outcomes rather than benchmarks: plan a task, use tools, check work, keep going without supervision. Reported performance includes 82.7% on Terminal-Bench 2.0 (ahead of Claude Opus 4.7's 69.4%) and 90.1% on BrowseComp for the Pro variant. Ethan Mollick, who had early access, reports that GPT-5.5 Pro completed a complex procedural-simulation task in 20 minutes that GPT-5.4 Pro took 33 minutes to finish.

So what

The six-week cadence from GPT-5.4 to GPT-5.5 is now the industry pattern, and it is changing how product teams should plan. If your roadmap assumes quarterly model improvements, you are building to last quarter's capability frontier. Two immediate moves: first, audit any multi-call agent chain that was engineered around GPT-5.4 reliability limits — many will collapse to one or two calls and justify the higher per-token cost. Second, if you are an enterprise customer in the middle of procurement, the contract-length conversation matters: capability gaps open and close in weeks, and locking in three years of a specific model is increasingly a risk, not a benefit.

Confidence: Established fact — confirmed by OpenAI announcement, CNBC, TechCrunch, Fortune, and Decrypt coverage with specific benchmark numbers.

Go deeper OpenAI announcement · One Useful Thing

Technology

April 22: OpenAI Workspace Agents bring Codex-powered shared agents to ChatGPT teams

OpenAI introduced Workspace Agents for ChatGPT Business, Enterprise, Edu, and Teachers plans, free through May 6 before credit-based metering kicks in. The agents are Codex-backed, can be created by one person and shared across a team, integrate with Slack and company systems, retain memory, and can run on schedules when users are offline. OpenAI shipped five starter templates (Software Reviewer, Product Feedback Router, Weekly Metrics Reporter, Lead Outreach, Third-Party Risk Manager) and is positioning this as the successor to the 2023 GPT Store model that never quite stuck.

So what

The unlock is also the risk. Workspace Agents inherit shared context, act across connected systems, and learn how a team works over time — which means the governance question stops being theoretical the day your team creates its first one. Before enabling this, designate a single owner for agent approvals, require agents touching customer or financial data to route through an approval step, and instrument usage so you can audit what agents are actually doing once they are in production. The companies that get real leverage here will be the ones that treat agent deployment as a change-management program, not a feature rollout.

Confidence: Established fact — OpenAI announcement and independent coverage from The Deep View, The Rundown, Superhuman, and The Neuron.

Go deeper OpenAI announcement · The Deep View analysis

BusinessDeveloping

April 23: Microsoft confirms token-based billing for GitHub Copilot, effective June 1

Building on the unit-economics pressure we flagged in the April 20-21 held item, Microsoft has now confirmed that all GitHub Copilot subscribers move to token-based billing starting June 1. Copilot Business will be $19 per user per month with $30 of pooled AI credits; Copilot Enterprise will be $39 per user per month with $70 of pooled credits; after the June-through-August promotional period, credits are expected to match the subscription price (i.e. no subsidy). Anthropic's Opus models have already been removed from the $10 Pro tier, new Pro and Student signups are paused, and rate limits have tightened. Internal documents reviewed by Ed Zitron cite the weekly cost of running Copilot roughly doubling since January as the trigger.

So what

Treat this as the structural event, not a pricing footnote. When the largest enterprise AI-coding product publicly acknowledges that seat-based economics cannot cover agentic workloads, every SaaS CEO whose product is adding agentic capabilities should have the same conversation internally this quarter. Two things worth doing now: first, build token-cost telemetry into your product before your board asks for it, so that gross margin per customer is observable rather than inferred. Second, start rehearsing the conversation with customers about consumption or outcome-based pricing; the alternative is discovering, six months from now, that your most engaged power users are also your most negative-margin accounts.

Hype check

The specific promotional-period pricing is from leaked internal documents via Ed Zitron, not yet from Microsoft's own announcement text; pricing may shift before June 1. The direction of travel is well-confirmed; the exact numbers are not.

Confidence: Informed perspective — Microsoft has publicly confirmed the shift, but the specific business/enterprise credit amounts rely on a single-source document review.

Go deeper Where's Your Ed At exclusive · The Rundown AI

Legal & Regulatory

April 21: A Discord group allegedly gains unauthorized access to Anthropic's Mythos model

Bloomberg reported that a private Discord group tracking unreleased AI models gained access to Anthropic's Mythos cybersecurity model within days of its April 10 launch to Project Glasswing partners. The group reportedly guessed Anthropic's deployment URL based on naming patterns leaked in the recent Mercor breach, used vendor credentials obtained through contract work, and claims to have accessed multiple unreleased models. Anthropic says its systems were not compromised and is investigating the third-party vendor pathway. The group told Bloomberg they are not using Mythos for offensive cyberactivity.

So what

The first material leak of a frontier safety-restricted model came not from a nation-state actor but from a Discord group exploiting vendor-chain credentials. For any growth company whose product, compliance posture, or enterprise-sales narrative depends on controlling access to AI-generated capability, the practical takeaway is about your own vendor chain: contractor credentials, naming conventions in deployment URLs, and third-party access audits are now material risk surface. This is worth a conversation with your CISO this week, whether or not you touch AI directly — the pattern (credential plus URL-enumeration) generalizes well beyond Mythos.

Confidence: Informed perspective — Bloomberg reporting is specific and multi-sourced, but Anthropic's own investigation is ongoing and the group's access claims have not been independently verified.

Go deeper Bloomberg · The Rundown AI

Perspectives

Technology

April 23: Mollick's three-part frame — think in models, apps, and harnesses, not just models

Using the GPT-5.5 release as the example, Ethan Mollick proposes that the useful unit of analysis for AI capability is not the model alone but three interlinked concepts: the model (Opus 4.7, Gemini 3.1, GPT-5.5); the app that wraps it (ChatGPT, Claude.ai, increasingly desktop tools like Claude Code, Claude Cowork, and Codex); and the harness of tools the model can use (web browsing, code execution, image generation, computer control). Gains in any one of the three compound across the other two. His illustrative run: four prompts into Codex powered by GPT-5.5 produced a near-PhD-quality academic paper from a decade of his own unpublished crowdfunding data, and one prompt produced a 101-page tabletop roleplaying game with illustrations and simulated playtesting. The "jagged frontier" is still there — fiction still flat, some hypotheses still uninteresting — just much further out than before.

So what

If your organization is still evaluating AI primarily by model choice, you are under-optimizing two-thirds of the capability surface. The practical exercise is to audit your current AI usage against the triangle: which apps is your team actually in (chat interface versus desktop agent like Claude Code or Codex) and what tools do they have access to (web, execution, file-system, your own systems via MCP). Most of the productivity gap between AI-savvy employees and everyone else is not in the model they chose; it is in which app-plus-harness they default to. Make that choice deliberate.

Confidence: Informed perspective — a framework piece by a credible single source (Wharton professor with deep hands-on AI experience), backed by his own demonstrations rather than independent corroboration.

Go deeper One Useful Thing

Socioeconomic

April 22: Serodio finds no visible AI effect on UK employment — the productivity paradox may be back

Economist Pedro Serodio, writing for the Centre for British Progress, reports that across 412 UK occupations, employment over the three years since ChatGPT's launch shows no visible difference between roles most and least exposed to AI. Actual AI usage accounts for roughly 2.1% of all work tasks. Serodio invokes Robert Solow's 1987 line about computers being visible everywhere except in the productivity statistics: the last general-purpose technology took about 40 years to show up in the numbers. Adoption patterns across four independent measures point to narrower, more collaborative use than expert-rated "AI exposure" scores predict.

So what

This is a useful counterweight to the Suleyman/Hinton/Dorsey narrative that AI will automate most white-collar work within 12 to 18 months. Both things can be true: capability is advancing rapidly, and diffusion through real organizations is slower and more selective than the hype cycle suggests. The practical implication for growth leaders is calibration, not dismissal: the competitors who win will be the ones who move faster than the aggregate adoption rate Serodio measures, but the ICP and regulatory pressure you feel in the next 12 months will be shaped more by adoption lag than by capability curves. Keep both timelines in your head.

Hype check

Headline employment in the UK is a lagging indicator, and other British data (graduate hiring down 45% year-on-year, vacancies at pandemic lows, 38% of UK employers planning fewer graduate hires because of AI per Randstad) tells a more textured story. The Serodio finding is real; so are the hiring-composition shifts it does not capture.

Confidence: Informed perspective — methodologically careful single source with a well-known countervailing body of evidence.

Go deeper British Progress report · The Neuron

Case Studies

People & Organization

April 23: Anthropic's Cat Wu on how the Claude Code team shipped faster than anyone else

Cat Wu, Head of Product for Claude Code and Claude Cowork, describes on Lenny's Podcast a shipping cadence that has compressed from months to weeks to days. Three principles stand out as portable beyond Anthropic: build products before the underlying model is ready, so you are positioned to ship the moment the capability lands; have the PM ask the model itself to introspect on its own mistakes as a core evaluation skill; and lean heavily on mission alignment to strip out the coordination friction that usually slows large organizations. Wu also describes being one of hundreds of PMs Anthropic has interviewed for AI roles, and what separates the ones who thrive.

So what

The lesson worth lifting out of the Anthropic-specific context is about how product teams handle non-deterministic capability. Most traditional PM practice assumes the platform is stable and the user is the variable. In an AI-native product, the platform (the model) is the variable, and waiting for stability means shipping late. Practical test for your own product org: how many of your current PMs could ship a feature today that will only fully work when the next model release lands? If the answer is none, the capability gap between your team and Anthropic's is not a hiring problem, it is a framing problem — and it is one of the more fixable ones on your list.

Confidence: Informed perspective — a first-person account from inside the company being discussed, which is both its strength and its natural limitation.

Go deeper Lenny's Newsletter

Resources

Tools

A two-step dictation workflow for writing better first drafts with AI

The core move: dictate your rough outline into Codex or Claude Code, then explicitly tell the agent to preserve the initial draft untouched and create a separate working draft for revision. Read the working draft with dictation comments that flag what is inaccurate, what is missing, and what sounds generic or AI-like, then ask the agent to rewrite in your tone using those comments. The pro tip that matters: have a separate agent compare your initial drafts against your final drafts weekly, extract the edits you make, and build up a personal editorial style guide over time — the workflow gets better the longer you run it.

So what

Most executives using AI for writing are stuck in the one-shot-draft trap: one prompt, one output, accept or reject. This workflow turns AI writing assistance into a system that compounds — your voice becomes more consistent over time rather than more generic. Worth trying personally this week on your next memo or investor update, and worth sharing with your comms team as a standard operating pattern. The tool choice (Typeless for dictation) is less important than the two-draft discipline.

Confidence: Informed perspective — a practical workflow that is plausibly durable; evergreen pattern rather than news.

Go deeper The Rundown AI guide

Sources in this edition: One Useful Thing, The Neuron, Lennys Newsletter, Every, Superhuman AI, The Rundown AI, The Deep View, TLDR AI, Daily AI, AINews, TheSequence

← Latest Editions and Search