
This episode offers Amazon sellers crucial strategies to dramatically cut AI operational costs without sacrificing productivity. It highlights how to manage AI spend for teams, switch models effectively, and utilize platforms like OpenRouter and Kimi K3 to turn multi-pound tasks into penny-cost operations. The discussion reframes AI expenditure as an investment, demonstrating how to maximize ROI and optimize workflow for enhanced efficiency.
Danny McMillan and Sim on model switching, OpenRouter cost hacks and whether AI spend for Amazon teams is actually worth it. A quick solo show this week — Dorian's out sick, Matt's unavailable, so it's just Danny and Sim covering how to control AI spend without gutting output. Sim walks through the real cost pressure of a 25-person team on Claude: five figures a year, uncapped Fable usage, and no way to see per-person burn. Danny counters with the setup he's built to fix exactly that — routing grunt work through OpenRouter and Kimi K3 without preloading tools, which took one job from £4-5 down to 35p. They land on a practical split: Fable 5 for planning, a cheaper model for the build, staged "cascade" plans to keep context windows under control. Sim also shares a genuinely wild same-day case study — a 100-video yoga app build for about £300 — and Danny pushes back on the whole framing: stop looking at AI as a cost line and start looking at what it's generating. Key Topics Picking one AI provider and sticking with it - the cost of switching a trained team, and why Astra being better than Fable isn't reason enough to move Why teams actually burn tokens - heavy browser automation, parallel video work, and vibe-coders scaling far past their job description The OpenRouter cost hack - Kimi K3 without preloaded tools, cutting one job's cost by roughly 90% Cascade planning - staging big builds across multiple sessions to control context window burn Chinese model options - GLM 5.3 and LM Studio AI as free-to-cheap alternatives Grok as a low-friction accessory - personal automation for AI-hesitant team members ROI framing - weighing AI spend against what it actually produces, not just what it costs Timestamps [00:01] Quick solo show - Dorian ill, Matt unavailable, flight to Mallorca later [01:02] Wishing Dorian a speedy recovery, back next month [01:17] Kicking off: token costs, Astra's