AI News & Strategy Daily with Nate B. Jones

For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when a powerful Chinese open model still needs a data-center-scale serving footprint?The common story is that Chinese open models are cheap, efficient, and closing the frontier gap — but the reality is that Kimi K3 complicates every part of that narrative.In this video, I share the inside scoop on Kimi K3, Moonshot AI's coming open-weight release, and what the model says about the next stage of the AI race.Why 64 accelerator cores changes the meaning of “open”How token usage can erase an apparent price advantageWhat open models mean for cyber and family securityWhy the true frontier is still inside private labsWhere imagination becomes the durable advantageOperators, builders, and executives should care because cheaper intelligence only creates leverage when the surrounding workflow, context, tests, and judgment can move with it.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.

For deeper playbooks and analysis: https://natesnewsletter.substack.com/Clean sensitive documents locally: https://unlock-ai.natebjones.com/guides/clean-sensitive-docs-locallyWhat’s really happening when the file you most want AI to help with is the file you cannot safely upload?The common story is that sensitive work has to stay manual — but the reality is that downloaded models, controlled enterprise systems, and narrow specialist workflows now create several practical paths between “send it to a chatbot” and “do not use AI.”In this episode, I share the inside scoop on how Bayer and Discovery Bank are building private AI specialists, then demonstrates the small version with LM Studio and a synthetic contract on a laptop with the network disconnected.Why model instructions are not the same thing as a secure product boundaryHow a local sensitivity router can flag, mask, and route potentially private materialWhat LoRA changes when a company tunes a specialist for one narrow jobWhere laptop-scale processing ends and managed infrastructure beginsWhy open weights do not automatically eliminate platform dependenceThis matters for operators, builders, security teams, and executives who need useful AI without losing control of confidential files or the learning loop created around them.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.

For deeper playbooks and analysis: https://natesnewsletter.substack.com/p/let-ai-pick-what-to-automateWhat's really happening when you stop telling an AI what to automate and ask it to discover the problem itself?The common story is that AI agents need a tightly specified task — but the reality is that the strongest systems can inspect real work, identify recurring friction, and propose different high-leverage automations.In this video, I share the inside scoop on giving Fable and Codex the same open brief and getting two very different answers.Why picking the problem is becoming part of the agent's jobHow Fable found a strategic editorial preflight opportunityWhat Codex built to validate completed content handoffsWhere human judgment still mattersHow to turn the method into a reusable automation-discovery skillFor operators, builders, and leaders, the shift is from asking which tool to use to asking which recurring problem is worth solving completely.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.

Every time an AI missed something, I added another rule. Eventually, the accumulated skills, memories, system prompts, checks, and permissions became a hidden system of their own—and that system was getting in the models' way.In this episode, I audit the harness around my AI and compare what happens when Fable 5 and ChatGPT 5.6 meet compact versus overloaded instruction systems. The audit found 66 skill routes, 172 instruction assets, repeated governance rules, and a discovery layer far beyond Codex's stated budget.The lesson is not simply to shorten every prompt. It is to give each surviving instruction one owner and one reason, load specialist context when the work needs it, and enforce deterministic requirements with hard checks.Privacy Policy: https://www.acast.com/privacy

For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening as the model race expands into GPT-5.6, Fable 5, Grok 4.5, GLM 5.2, and increasingly complicated model mixes?The common story is that you should pick whichever model tops the latest benchmark — but the reality is that the best model depends on how you think, how you prompt, and what your hardest work requires.In this episode, Nate shares the inside scoop on choosing a model by work pattern rather than hype.Why “dumber” does not mean dumbHow model families develop different working stylesWhy benchmarks are evidence, not the selection heuristicHow Ringer pairs a strong architect with cheaper workersWhat knowledge-work AI still needs beyond coding harnessesFor builders, operators, researchers, and team leaders, understanding your own work is becoming more durable than memorizing every model leaderboard.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.

AI made it cheap to build almost anything. Most companies still ship at the old pace, and it isn't because their AI is worse than Anthropic's or OpenAI's. The real difference is what they've moved out of meetings and documents and into working code.Full post: https://natesnewsletter.substack.com/p/ai-native-company-rules?r=1z4sm5&utm_campaign=post&utm_medium=web&showWelcomeOnShare=trueMy Links 🔗 👉🏻 Newsletter: https://natesnewsletter.substack.com/ 👉🏻 X: https://x.com/natebjones 👉🏻 TikTok: https://www.tiktok.com/@nate.b.jones 👉🏻 Instagram: https://www.instagram.com/nate.b.jonesWhat's really happening inside the companies that ship AI features every week? The common story is that they just have better AI. The real question is what they rebuilt underneath the model to make that speed possible.In this video, I share the inside scoop on the 15 rules I use to move a company from tool adoption to real AI-native speed:Why moving repeatable coordination into code is now an operator's jobHow 15 commandments work together as one operating systemWhat changes first: roadmaps, meetings, documentation, and designWhere partial adoption fails, and why every rule has to move togetherMoving this fast is real, but only if you treat these as one system instead of picking off the rule that feels easiest to adopt.

Most people bought AI agents and never figured out what to point them at. This is the one-minute test that tells you whether a task belongs in a chat, a single agent, a team of agents, or nowhere near AI.My Links 🔗👉🏻 Newsletter: https://natesnewsletter.substack.com/👉🏻 X: https://x.com/natebjones👉🏻 TikTok: https://www.tiktok.com/@nate.b.jones👉🏻 Instagram: https://www.instagram.com/nate.b.jonesWhat's really happening inside the AI agent economy?The common story is that you need more agents. The real question is which tasks are worth any agents at all.In this video, I share the inside scoop on how to spot agent-shaped work: - Why buying more thinking now beats hiring or waiting - How four estimates sort any task in about a minute - What a 40-tool audit surfaced and what it cost to run - Where human judgment still beats every frontier modelThe agents already work. The scarce skill now is knowing which tasks to hand them and which to keep for yourself.

Multi-agent AI systems just went from research project to recipe. I ran 20+ AI agents across 4 model families to rebuild a website in one afternoon for about $8 — and the system caught every hallucination, every shortcut, and even the boss model's own bug without me lifting a finger.Full post:https://natesnewsletter.substack.com/p/trust-ai-agents?r=1z4sm5&utm_campaign=post&utm_medium=web&showWelcomeOnShare=trueMy Links 🔗👉🏻 Newsletter: https://natesnewsletter.substack.com/👉🏻 X: https://x.com/natebjones👉🏻 TikTok: https://www.tiktok.com/@nate.b.jones👉🏻 Instagram: https://www.instagram.com/nate.b.jonesWhat's really happening inside multi-agent AI systems?The common story is that hallucinations make AI agents too untrustworthy for real work — but the real question is whether trusting the agent was ever the right design in the first place.In this episode, I share the inside scoop on running a verified agent swarm: - Why one frontier boss plus cheap workers beats frontier-only pricing - How executed checks caught a hallucination, a cheat, and the boss's bug - How to audition new models before trusting them with real work - What a written constitution does that task-by-task prompting can'tHallucinations aren't solved — but with verification built into the structure, delegating big work to AI agents becomes a design question instead of a trust question.

For deeper playbooks and analysis: https://natesnewsletter.substack.com/What's really happening when AI execution gets cheaper but everything starts to feel the same?The common story is that cheaper models make advanced work a commodity, but the reality is that value moves toward the people who can imagine better work, bring context to it, and give themselves permission to run the experiment.In this episode, I share the inside scoop on why imagination x execution is becoming the operating question for AI teams.Why the $9 model test and the $40 model test mean very different thingsHow cheap open execution becomes an engine, not the whole strategyWhat the porch-mailer example reveals about new work no task list had capturedWhere context, permission, and technical imagination meetWhy the Stripe migration story is really about prepared infrastructureIf you are building with AI, managing a team, or trying to understand where frontier spend still matters, the question is not just which model is cheapest. The question is whether your task list has changed.Subscribe for daily AI strategy and news.Hosted on Acast. See acast.com/privacy for more information.