Share

AI News & Strategy Daily with Nate B. Jones
Claude Design Just Killed the Mockup. Is Your Team Next?
Full Story w/ Prompt Kit: https://natesnewsletter.substack.com/p/claude-design-replaced-a-week-of
What's really happening inside the Claude Design launch when everyone reacted with Figma stock crashes but missed the actual story?
The common narrative is that this is a Figma killer — but the reality is that Claude Design is the third piece in a coordinated Anthropic stack that's quietly retiring the entire mockup-to-production handoff that product teams have used for twenty years.
In this episode, I share the inside scoop on what this launch means for how teams build:
• Why the prototype is no longer an approximation of the thing but actually the thing itself
• How Claude Code, Cowork, and Design fit together into one coordinated motion
• What changes role by role for PMs, designers, engineers, and founders
• Where Google Stitch is already fighting back with design.markdown
Leaders who see this as a design tool replacement are missing that the mockup itself is going extinct — and most team structures are built around a cost that just disappeared.
Subscribe for daily AI strategy and news.
For deeper playbooks and analysis: https://natesnewsletter.substack.com/
More episodes
View all episodes

What to Do When Your Company's AI Tool Is Bad at Your Job
24:47|What's really happening inside corporate AI procurement when everyone on your team knows the default tool can't do the job but saying so makes you sound like the problem instead of the person trying to get work done?The common framing is that you're asking for an exception — but the reality is that your company is expecting frontier tool results from default tool performance, and almost nobody is talking fluently about that gap.In this video, I share the inside scoop on how to actually win this conversation: • Why your argument is landing as preference instead of evidence and how to fix it • How to run a simple test with one recurring job, two tools, and a week of data • What changes when the ask moves from your manager to a director to an exec • How to answer the four objections you're almost certainly going to getLeaders treating AI tools as interchangeable are paying a hidden tax in 30-minute chunks and five-minute corrections — and their best people are already quietly leaving for companies with better tooling.Subscribe for daily AI strategy and news.For deeper playbooks and analysis: https://natesnewsletter.substack.com/
Salesforce Killed The Browser. Every Agent Runs Your CRM Now.
23:07|Full Story w/ Prompt Kit: https://natesnewsletter.substack.com/p/the-5-question-filter-i-run-every?r=1z4sm5&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true___________________What's really happening inside the AI agent market when another launch drops every week and the question is no longer what shipped but which of these actually deserves an afternoon of your team's attention?The common reaction is exhaustion — but the reality is that the agent conversation has quietly moved from model quality to infrastructure, and most launches fail a simple five-question filter.In this video, I share the inside scoop on how to cut through the noise: • Why the best agent news is infrastructure news and the worst is a new destination to migrate to • How Workspace Agents, Headless 360, Copilot Wave 3, Kimi 2.6, and Perplexity Personal Computer score on the filter • What Claude showing up inside Microsoft, Salesforce, and Perplexity tells you about Anthropic's real strategy • Why the switching question is framed wrong and this is actually a layering questionLeaders chasing whichever agent had the loudest launch will fall behind teams that learned to route work across layers based on the shape of the task.Subscribe for daily AI strategy and news.For deeper playbooks and analysis: https://natesnewsletter.substack.com/
GPT-5.5 vs Claude vs Gemini: The Real Difference Nobody's Talking About
32:33|What's really happening inside the GPT-5.5 release when everyone is comparing benchmark deltas but missing that the floor moved?The common story is that 5.5 is a little better than 5.4 — but the reality is that this model changes what you can reasonably ask a model to do, and I put it through three tests designed to make any frontier model fail.In this video, I share the inside scoop on why 5.5 is the strongest model in the world today: • Why the old question was "can the model answer this" and the new question is "can the model carry this" • How Dingo, Splash Brothers, and Artemis II expose where models actually break • What 5.5 caught that no previous model caught and where it still needs validation • Why Codex matters more than ChatGPT for serious work nowLeaders evaluating models on easy tasks will conclude the differences are small — and they'll be right, but only about the wrong category of work.Subscribe for daily AI strategy and news.For deeper playbooks and analysis: https://natesnewsletter.substack.com/
OpenAI Just Gave Every Team a Free Employee. Here's the Catch.
23:13|What's really happening inside ChatGPT's new Workspace Agents launch? The common story is that this is just a chatbot upgrade — but the reality is more interesting.In this video, I share the inside scoop on what Workspace Agents actually replaces and where it fits: • Why this threatens lightweight automation layers, not Claude • How a plain-English build experience changes who can ship agents • What workflow patterns consistently work versus consistently backfire • Where governance becomes the real enterprise unlockTeams that point AI agents at novel, judgment-heavy work will blame the product when it fails. The real advantage goes to operators who match this tool to repeatable, tool-crossing workflows with a clear output and a human reviewer.Subscribe for daily AI strategy and news.For deeper playbooks and analysis: https://natesnewsletter.substack.com/
Apple Just Positioned Itself for the Next Trillion Dollars
20:56|What's really happening inside Apple's AI strategy behind the Tim Cook succession?The common story is a smooth handoff to an Apple lifer — but the reality is more interesting: Apple just restructured the entire company around a race the rest of the industry isn't running.In this video, I share the inside scoop on Apple's hardware-first bet against cloud AI:Why Apple elevated two hardware engineers above everyone elseHow broken cloud AI economics are building a two-class user systemWhat law firms buying Mac Minis reveal about on-device AI demandWhere the trillion-dollar local AI opportunity sits for builders todayFor leaders, builders, and prosumers, the shift from metered cloud AI to owned on-device compute is already underway — and the question isn't whether to pay attention, but how fast to reposition your strategy around it.Subscribe for daily AI strategy and news.For deeper playbooks and analysis: https://natesnewsletter.substack.com/
Your Design Workflow Has Three Steps. ChatGPT Just Made It One.
25:45|Full story w/ prompts: https://natesnewsletter.substack.com/p/what-gpt-image-2-actually-changedWhat's really happening inside AI image generation after GPT-Image 2's 93% win rate?The common story is a better image model — but the reality is more interesting: image generation just joined the reasoning stack, and the workflows, risks, and role changes that follow are nothing like the coverage suggests.In this video, I share the inside scoop on why this is a structural shift, not a product launch: • Why a 26-point benchmark gap signals a rules change, not a rankings change • How thinking mode, web search, and self-verification collapsed three jobs into one prompt • What the forgery risk means for trust, evidence, and every verification workflow • Where Claude Design and GPT-Image 2 diverge — and which one wins for your use caseFor designers, builders, and operators, the bottleneck on visual work just moved from model skill to specification quality — and teams that already think in briefs are about to pull very far ahead.Subscribe for daily AI strategy and news.For deeper playbooks and analysis: https://natesnewsletter.substack.com/
Your Apps Don't Need an API Anymore. Codex Just Proved It.
20:59|What's really happening inside OpenAI's Codex revamp when they shipped a desktop agent that can drive any Mac app in the background while you do other work?The common story is that this is a coding tool update — but the reality is that Codex shifted categories entirely, and the gap to Claude's computer use is wider than I expected after running them side by side for a week.In this episode, I share the inside scoop on what OpenAI is really building and why it looks so different from Anthropic: • Why Codex finishes in two minutes what takes Claude five or six with fumbles and retries • How the Workflow-to-Shortcuts-to-Sky team made background agents actually usable • What Chronicle tells you about training signal for computer use • Where Conway fits into Anthropic's bet that the ecosystem will cooperateLeaders who keep waiting for vendors to ship agent-ready interfaces are missing that Codex doesn't need the software industry to build for agents — the body just uses whatever's already there.Subscribe for daily AI strategy and news.For deeper playbooks and analysis: https://natesnewsletter.substack.com/Full Story w/ Prompt Kit: https://natesnewsletter.substack.com/p/grab-the-workflow-audit-that-tells
Karpathy's Wiki vs. Open Brain. One Fails When You Need It Most.
41:08|What's really happening inside the memory architecture debate when Andre Karpathy's wiki idea got 41,000 bookmarks in a week and everyone is asking if it makes OpenBrain obsolete?The common story is that these are competing approaches, but the reality is that they solve the same AI amnesia problem from opposite directions, and the difference determines whether your AI gets smarter over time or accumulates more stuff to dig through.In this video, I share the inside scoop on the deepest design decision in AI knowledge systems: • Why Karpathy's wiki compiles understanding at write time while OpenBrain synthesizes at query time • How editorial decisions in wiki synthesis can bake errors into your understanding • What breaks at scale for each approach and why teams need different architectures • Where the hybrid solution lives with a graph database over structured dataBuilders who pick a memory architecture without understanding this fork will either lose detail when they need precision or burn tokens re-deriving connections they already made.Subscribe for daily AI strategy and news.For deeper playbooks and analysis:https://natesnewsletter.substack.com/p/your-ai-re-derives-everything-it?r=1z4sm5&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true