Discover
Seller Sessions Amazon FBA and Private Label
Seller Sessions Amazon FBA and Private Label
Author: Danny McMillan
Subscribed: 853Played: 55,662Subscribe
Share
© Seller Sessions 2024
Description
Seller Sessions is the largest Amazon FBA and Private Label podcast for Advanced Amazon Sellers. It is the first of its kind, in terms of being raw, non nonsense and straight to the point. A lot of Amazon podcasts that came after has followed by example... Seller Sessions is published 4 times per week and often breaks new trends first in the industry.
Host Danny McMillan, is a world renowned public speaker and veteran Amazon Seller, Danny is also the co-founder of DATAbrill. DATAbrill manages Amazon PPC and advertising automation for 6, 7 & 8 figure Amazon brands.
Danny also works with Amazon in the UK to provide webinar content for their 3rd party sellers.
Each year he hosts Seller Sessions Live the annual conference for Amazon Sellers in the UK, bringing the worlds best speakers on the cutting edge of marketing on and off Amazon.
He is also the founder of SellerPoll, the official annual awards for Amazon Sellers and Brands.
Host Danny McMillan, is a world renowned public speaker and veteran Amazon Seller, Danny is also the co-founder of DATAbrill. DATAbrill manages Amazon PPC and advertising automation for 6, 7 & 8 figure Amazon brands.
Danny also works with Amazon in the UK to provide webinar content for their 3rd party sellers.
Each year he hosts Seller Sessions Live the annual conference for Amazon Sellers in the UK, bringing the worlds best speakers on the cutting edge of marketing on and off Amazon.
He is also the founder of SellerPoll, the official annual awards for Amazon Sellers and Brands.
1164 Episodes
Reverse
Conversion Monthly is back with Danny McMillan, Dorian and Sim, and this month the theme is clear: for Amazon sellers using AI, infrastructure matters more than the latest model. The team look at what has really worked in their businesses since the last show, and what has burned time, tokens and money. Sim explains how giving key staff the right tools doubled their off-Amazon marketplace sales, and how he gets the most out of a $20 assistant plan by having it run Codex for image generation. Dorian makes the case for building infrastructure and evaluations before solutions, and shows how he gives teams safe, limited access so they can build tools themselves. Danny demonstrates a routing and index file that took one workspace from more than 700,000 tokens to under 6,000, and argues that the real value now lies in the systems that run your business, not in software that the next model can replace. Key Topics Off-Amazon growth - B&Q, Debenhams and other UK marketplaces, and what a short account suspension taught Sim about risk Infrastructure before solutions - why bad input data, such as out of date landed costs, makes AI answers wrong Building evals - how to check that the numbers your AI gives you are actually correct Usage maxing - using a GrokBot assistant to spend a ChatGPT Codex allowance on image sets and TikTok slideshow ideas Routing and index files - the Jake Van Clief folder system and how one file cuts token burn The abstraction layer - why your business architecture is harder to replace than any software you launch AI for teams - read-only data access, tracking outcomes, and cutting a thousand alerts down to three priorities Multi-model setups - Claude desktop, separate cloud servers, open source orchestrators and Claude mods Timestamps 00:02 - Welcome back: Danny, Dorian and Sim 00:19 - Sim: new UK marketplaces and doubling off-Amazon sales 02:10 - A short account suspension and spreading risk across seller accounts 04:23 - Dorian: infrastructure first, wrong profit numbers and building evals 06:42 - Simple wins: WhatsApp updates and why the model is not the point 07:32 - Sim's stack: Opus 5.5, Fable 5.2 and automated image generation 09:42 - Usage maxing with GrokBot, Codex and ElevenLabs voiceovers 12:09 - Token burn and the Jake Van Clief folder system 14:01 - Demo: from over 700,000 tokens to under 6,000 with a routing file 16:27 - The abstraction layer: why AI software goes out of date so fast 20:04 - Return on AI spend and what routing saves on each plan 21:58 - Dorian: input, instruction, output, and defining the workflow 26:28 - Why Sim uses ChatGPT for images alongside Claude 28:35 - Dorian: rolling out automation to larger teams 30:58 - Tracking results and focusing on three things, not a thousand 33:26 - Workflows compared: Claude desktop, parallel sessions and separate servers 36:41 - Open source orchestrators: pros, cons and setup 38:00 - Claude mods: a session status mod that shows when you are needed 40:17 - Markdown agents versus deterministic scripts 41:56 - Final words: API connections and the Solscope MCP 44:58 - Fable 5.2, a cloned Excel and whether software is solved Key Takeaways Start with infrastructure, not solutions - clean, current data and clear inputs decide whether AI output can be trusted. Evaluate everything - check the input, check the output, and only automate once the results are consistently right. One routing file can slash token use - point Claude to a routing and index file first so it reads only what the task needs. Build the business, not disposable software - the architecture that runs your brand is the asset AI cannot copy. Give teams controlled access - limited, read-only data lets your best people build their own tools safely. Prioritise ruthlessly - automation should surface the three things that matter today, not a dashboard of a thousand. Notable Quotes "You give the key players in your business tools like the ones that are available now and great things happen." - Sim "You don't start with building solutions, you start with building infrastructures." - Dorian "It's not the models... It's basically everything ahead of it." - Dorian "What it can't replace is your mechanism and your architecture that runs your business very efficiently." - Danny McMillan Resources Mentioned Claude - Opus 5.5, Fable 5.2, Claude desktop, Claude Code and Claude mods ChatGPT Codex CLI - Sim's engine for main images and image stacks GrokBot - personal assistant Sim uses to run Codex and manage usage ElevenLabs v4 - voiceovers for TikTok slideshow content Jake Van Clief folder system - routing and index files that cut token burn n8n and Trigger.dev - automation platforms Dorian's teams build on Hetzner - cloud servers Dorian uses to keep big projects separate 3T quote - open source orchestrator for multiple models, accounts and token tracking Paperclip - open source tool for building teams of AI agents Solscope - Amazon research tool with a strong MCP and API Matthew Berman - YouTube creator who rebuilt Excel with Fable 5.2 Connect Sim - LinkedIn, reach out for a Solscope discount code Dorian - LinkedIn, drop him a message Danny McMillan - [email protected] Seller Sessions is the leading podcast for advanced Amazon sellers, hosted by Danny McMillan.
Danny McMillan reveals 10 hidden costs of automation for Amazon sellers: upkeep, stacked failures and lost judgment, plus a simple equation for true benefit. Automation looks like a pure time saver for Amazon sellers, but Danny McMillan explains why the true cost of automating your business is higher than most brand owners price in. In this solo Conversion Monthly show, he shows how automations that work fine alone can fail together once they are stacked on top of each other. You'll hear ten blind spots, from failures that arrive all at once during a product launch or account suspension, to the problem of remembering how a workflow you built three months ago actually works. The core idea: automation does not remove the work, it shifts it from execution to maintenance, and most people price the build but never the upkeep. Danny finishes with a rule of thumb for what to ask at 1, 5, 10, 20, 50 and 100 automations, a refinement loop, and a hidden cost equation you can use to check what each automation really gives back. Key Topics Stacked failures - why several automations breaking at once during a launch or suspension costs far more than each one saves Execution versus maintenance - how automation moves the work rather than removing it The 10 blind spots - from forgotten setups to lost judgment and unchecked results The scale test - the question to ask yourself at each size of automation estate The refinement loop - build, run, find the exception, add the rule, test, monitor, repeat The hidden cost equation - time saved minus the cost of keeping the system alive The 10 Blind Spots 1. Failures can arrive together - with 45 automations, ten falling over on launch day makes the time each one saves matter less 2. Before you fix it, you have to remember it - did you leave yourself clear notes on why and how you built it? 3. You become the bottleneck - if only you understand the automations, every repair and every team question comes back to you 4. One broken link can create several problems - a stock report that feeds a reorder reminder that feeds another task spreads one failure down the chain 5. The setup ages while you run the brand - a new supplier, marketplace or stock process can leave an automation running on assumptions that are no longer true 6. Every workaround adds something to remember - small fixes for a missing SKU or a special stock figure pile up across a dozen automations 7. You can automate the task and lose the judgment - a person questions an odd order, a workflow passes it straight through unless a check was built in 8. You still have to check the result - a workflow can run successfully and still produce a wrong report that drives a stock or spending decision 9. The repair is only part of the work - after a fix you may need to clear duplicate tasks, missed updates and incorrect records 10. The interruption can cost more than the task saved - the real cost includes the important work you could not do while maintaining the system The Scale Test 1 automation - can I keep this working? 5 automations - can I remember what each one does? 10 automations - can I see the failures and identify the owners? 20 automations - can I change one without breaking another? 50 automations - can I manage the testing, the dependencies and the recovery? 100 automations - am I running my business, or maintaining my automation estate? Key Takeaways Price the upkeep, not just the build - automation moves your work from execution to maintenance, it does not remove it. Stacked failures hurt most when you are busiest - a launch or account suspension is exactly when several automations may need you at once. Leave breadcrumbs - clear notes and maps of how automations connect make a repair possible three months later. Keep human judgment in the loop - a workflow that runs is not the same as a workflow that is right, so build in checks and test the result. Watch where your time goes - at scale, you can end up maintaining workflows instead of doing the work only a brand owner can do, like the product pipeline. The Hidden Cost Equation Time saved minus monitoring, fixes, testing, recovery and ongoing refinement equals the actual benefit. Notable Quotes "Automation does not remove the work. Effectively, it shifts some of the work from execution to maintenance." - Danny McMillan "The time each one saves matters less when all need attention at once." - Danny McMillan "The first version automates the process you thought you had. Maintenance adapts it once you know what you actually have." - Danny McMillan "The trap is counting the hours each automation saves whilst ignoring the hours it takes to keep them alive." - Danny McMillan Resources Mentioned Claude, or your favourite AI - paste this episode's transcript in and prompt against it to find the blind spots in your own setup Maps of how your automations connect - a way to see how they integrate and overlap before you change one Breadcrumb notes - short records of why each workflow was built the way it was Seller Sessions is the leading podcast for advanced Amazon sellers, hosted by Danny McMillan. ```
Adam can't make it this week, so Danny takes the Broadmatch show solo with a method for anyone buried under a long list of problems. It started when a friend who uses Claude heavily could not see the wood for the trees: a hundred issues, each needing its own fix, and no way to review them all. Perplexity gave the approach a name, collaborative upstream problem solving. You'll hear how it combines systems thinking, affinity mapping, root cause analysis and collaborative validation, and why the person holding the domain knowledge has to stay in the loop. In this real example, it turned roughly 10 days of work into 2 to 3 hours. Danny walks through a five-step process, a Claude example about forgotten decisions and stale documents, and a one-paragraph summary you can drop into Claude to build your own skill. Key Topics Collaborative upstream problem solving - fixing the shared conditions behind many problems instead of each problem one by one The four-part method - systems thinking, affinity mapping, root cause analysis and collaborative validation Leverage points - the smallest set of changes that makes many problems disappear Why domain knowledge still wins - the human in the loop checks that the right problems were solved A Claude example - forgotten decisions, contradictory outputs and stale documentation as one shared context problem Turning the method into a skill - reverse engineer the transcript in Claude Timestamps 00:00 - Danny goes solo, Adam out this week 00:25 - Perplexity names the method: collaborative upstream problem solving 00:46 - The problem: a friend buried in Claude issues 01:36 - How do you turn 100 problems into a few? 01:58 - The combined approaches: systems thinking first 02:20 - Affinity mapping and root cause analysis 02:43 - Collaborative validation: domain knowledge wins 03:26 - Leverage points, not faster fixes 03:57 - Why domain knowledge matters: avoiding the wrong problems 05:03 - Clusters and markdown handover: 2 to 3 hours versus 10 days 05:18 - The five-step practical approach 06:22 - Claude example: forgotten decisions and stale documents 07:06 - Avoiding fixes that break other outputs 07:25 - A hypothesis, not a diagnosis 07:44 - Turning this into a Claude skill 07:55 - The method in one paragraph 08:23 - Wrap-up Key Takeaways Solve the conditions, not the problems - look for the shared causes generating a long list of issues. Cluster before you fix - affinity mapping turns 100 items into a handful of meaningful groups. Treat drivers as hypotheses - validate them with the person who holds the domain knowledge before acting. Test one intervention first - make a small change and check whether several related problems improve. AI executes, you think - the human in the loop and domain expertise decide whether the fixes are right. The Five Steps 1. Capture examples - the problems, plus the outcome the person wants 2. Cluster the symptoms - group problems by meaningful relationships using affinity mapping 3. Propose underlying drivers - recurring conditions that might explain each cluster, held as hypotheses 4. Validate together - check the groupings, exceptions, constraints and what is fixed 5. Test one intervention - a small change, then check whether related problems improve Notable Quotes "I'm not trying to solve a hundred problems faster. I'm trying to find the smallest set of changes that could make many of these problems disappear." - Danny McMillan "AI isn't just your assistant. You're driving the process yourself. It's you who's doing the thinking." - Danny McMillan "I solve the conditions creating the problems, not the problems themselves." - Danny McMillan Resources Mentioned Perplexity - used to find a concise name for the thinking approach Affinity mapping - the established technique for grouping many issues into meaningful clusters Claude - used to organise the material and build the markdown handover files Cron job checks - a scheduled way to keep documentation current and replace stale information Connect Questions on the method? Email Danny McMillan at [email protected]. Seller Sessions is the leading podcast for advanced Amazon sellers, hosted by Danny McMillan.
Danny McMillan and Ritu Java cover AI remote control, token-saving skills and burnout resets so you can step away from the desk and keep projects moving. Ritu Java is back for the monthly Go With The Flow show, fresh from Accelerate and a lot of conversations about how fast AI adoption is moving. Her problem will sound familiar: chat is faster than she is, so she has become the bottleneck on her own projects. This episode is about AI on the move, running your work from your phone so you can walk, hike or cook without losing control. You'll hear how Claude remote control and Codex remote work in practice, what the catches are, and where Gemini Spark fits in for anything that lives in the Google ecosystem. Danny shares a plan-reading tip that cuts cognitive load, then the pair dig into where agency token spend really goes, why deterministic Python and SQL beat AI judgment on cost, and how to keep a stack of 90 skills clean as models change. They finish on the human side: Ritu's two past burnouts, Danny's reset habits, and why controlling your attention matters more than keeping up with every new release. Key Topics AI on the move - running Claude and Codex sessions from your phone while away from the desk Claude remote control vs Codex remote - one-time setup, per-project setup, and the "laptop must be open" catch Gemini Spark - an always-on assistant for Gmail, Calendar, Tasks and BigQuery Plan-reading tip - ask for a natural language plan on top and the technical plan underneath Where tokens really burn - judgment work, scraping, images, video, browser work and MCPs versus leaner CLI and scripts Skill hygiene - using /insights and /doctor, merging duplicates and building a skill map Burnout and resets - breaks, walks, meditation and protecting your attention Timestamps 00:00 - Danny welcomes Ritu back for the monthly show 00:14 - Ritu on Accelerate and the AI adoption shift 01:01 - The foundation problem: chat is faster than the human 03:15 - Claude remote control: how it works 04:43 - The terminal quirk for activating remote control 06:23 - Answering Claude from the car (and why not to) 06:43 - Danny spots the new remote control toggle in Claude Desktop 07:56 - The catches: laptop must be open, set up per project 08:22 - Codex remote: desktop and mobile mirror each other 09:21 - Sharing one GitHub between Claude and Codex 10:02 - The protocol: plan at the desk, follow up on the move 11:05 - Danny's plan tip: reject early plans, ask for a plain-English top half 12:40 - Gemini Spark for the Google ecosystem 13:58 - How steep is the Claude to Codex learning curve? 15:06 - Sonnet 5.5 efficiency versus Opus 5.5 cost 15:49 - Running 86 to 90 skills and watching token usage 16:41 - Left brain versus right brain: where tokens skyrocket 18:15 - MCP versus CLI token cost 19:10 - Running /insights and /doctor over your skills 21:38 - Maintenance: old scaffolding can slow newer models 22:23 - What Ritu actually does on the road 23:18 - Notepads and breadcrumbs: Apps Script on Gmail 24:14 - Client sentiment analysis from email 25:10 - Staying fresh and Ritu's two burnouts 26:52 - Danny's resets: walks, meditation and breaks 28:31 - Wrap-up: the luxury of experimentation 30:15 - Danny: control your time and attention 31:12 - Where to find Ritu Key Takeaways Plan at the desk, steer on the move - do the heavy work in one sitting, then answer questions and corrections from your phone. Know the catches before you rely on remote control - the laptop has to stay open, and Claude needs setup project by project while Codex is enable-once. Ask for a plain-English plan - a natural language top half with the technical plan underneath makes plan review far easier on your brain. Push repeatable work into scripts - Python and SQL cost nothing once built, while judgment, scraping, images, video and browser work eat tokens. Maintain your skills - merge duplicates, add a skill map, and retire guard rails that newer models no longer need. Protect your attention - pick a handful of things to follow, set boundaries and take real breaks before burnout does it for you. Notable Quotes "Chat is faster than me, and I'm seeing that I am becoming the bottleneck." - Ritu Java "We thought AI could make us freer than before. No. I feel like a slave. But it's fun." - Ritu Java "Scaffolding or guard rails you put in eight months ago can actually slow the model down." - Danny McMillan "Control your time and attention, because AI is going to drop something new every single day." - Danny McMillan Resources Mentioned Claude remote control - lets you answer a running Claude Code session from the Claude app on your phone Codex remote (ChatGPT Codex) - mirrors desktop and mobile, enabled once for every project, Mac only Gemini Spark - always-on assistant in enterprise Google Workspace for Gmail, Calendar, Tasks and BigQuery /insights and /doctor - built-in commands for reviewing and tidying your skills Google Apps Script - used to mine email for notes, ideas and client sentiment Notion and Freeform - Danny's breadcrumb tools outside Claude Connect Ritu Java - find her on LinkedIn under her full name Seller Sessions is the leading podcast for advanced Amazon sellers, hosted by Danny McMillan.
Danny McMillan and Shubhash unpack the Fable 5.1 vs Astra debate, the six-stage AI harness, and why your folder structure is the real cost lever. Shubhash joins from his new home in Dubai to dig into the two biggest AI releases of the fortnight, Fable 5.1 and Astra, dropped within 72 hours of each other. Instead of relitigating which model wins, he makes the case that "which model is better" is the wrong question entirely, and spends the episode showing why. You'll hear the real cost story behind cached tokens, why a shiny 3D render says nothing about which model is actually smarter at your business's real work, and Shubhash's six-stage "harness" framework for judging any AI tool. Danny closes with a teaser: an enterprise AI consultant's folder-as-operating-system approach that could cut token burn without touching the model at all. Key Topics Fable 5.1 vs Astra - what a codebase-drift benchmark actually revealed, beyond the marketing screenshots The cached-token price trap - why identical list prices don't mean identical bills The six-stage harness - job, prompt, tools, model, failure handling, pass mark Model-switching without the cost trap - avoiding preloaded tools when routing to third-party APIs Claude Desktop as a single workspace - Danny's parallel-conversation, no-VS-Code setup Folders as the AI operating system - a teased framework for scoping context with markdown files Timestamps [00:01] Shubhash joins from his new home - relocated to Dubai [00:57] Agenda: Fable 5.1 and Astra, launched 72 hours apart [01:24] Danny's pushback - "are they building anything?" [01:50] Shubhash: "which model is better" is the wrong question [02:06] Ellis's LinkedIn benchmark - Astra similar quality to Fable 5.1, lower cost [03:13] Where Astra broke - drifting from existing codebase conventions on the hardest tasks [04:29] Why comparison screenshots are confirmation bias - published by the model's own maker [05:35] Shubhash's five-point checklist before adopting any new AI tool [06:59] "A model is just an engine" - the car and harness analogy [08:28] The real price difference - cached token reads, 25c vs $1 per million [09:35] Season ticket vs pay-on-the-gate pricing [09:54] How few sellers actually examine their AI bill [11:41] Avoiding the third-party API cost trap - tool preloading [12:20] Real example - a $4.50 job cut to 35p once preloading was stripped out [12:40] Where Astra genuinely wins - 3D renders, exploded views, web design [13:46] Splitting by job type - Astra on design, Claude on knowledge work and recovery [14:30] The six-stage harness framework introduced [17:12] "The model is the sex and sizzle" - Danny's framing [18:21] Shubhash's VS Code setup - Claude and Codex extensions handing off work [19:52] Danny's Claude Desktop-only workflow, no VS Code [20:22] Finder and Spotlight optimisation, Kimi K3 kept to the terminal only [23:39] Widgets over walls of text - "like a kid's colouring book" [24:24] Natural-language plan on top, technical plan underneath, on request [24:45] Freeform and stylus for complex problem-solving [25:50] Raycast as a free Spotlight replacement [27:08] Why "you don't need instruction files anymore" ignores who's paying for the tokens [27:56] Teaser - an enterprise AI consultant's file-structure system [29:15] The folder-as-AI-operating-system concept [31:27] Three-layer breakdown - the map, context rules, work tools [33:45] Wrap-up - Shubhash's three-question pre-switch checklist Key Takeaways "Which model is better" is the wrong question - the harness around the model decides the outcome far more than the model itself. List prices hide the real cost - cached-token rates can be 4x apart even when headline pricing looks identical. Split tasks by strength, not loyalty - Astra ahead on visual and web design work, Claude ahead on knowledge work, long documents and error recovery. Tool preloading is the hidden API cost - stripping it out cut one job from $4.50 to 35p. Your folder structure is your harness - scoping Claude to only the context a task needs cuts token waste before any model swap is needed. Notable Quotes "A model is just an engine. If you haven't built the car, the chassis, the tyres, everything else around it, a faster engine isn't getting you anywhere." - Shubhash "You don't pay your goalkeeper up front just because he's the best athlete in the squad." - Shubhash "The model is the sex and sizzle, not the bit underneath it." - Danny McMillan "Before you chase the next model, write down only what you know... get that right and we are good." - Shubhash Resources Mentioned Fable 5.1 - the latest release under discussion, benchmarked against Astra on real codebase tasks Astra (GPT-6) - OpenAI's release, strong on visual/web design work, weaker on holding existing coding conventions Raycast - free Spotlight replacement Shubhash uses for local search VS Code (Claude + Codex extensions) - Shubhash's multi-agent handoff setup Claude Desktop - Danny's single-workspace setup: parallel conversations, in-app browser and file viewer Freeform (iPad + stylus) - Danny's tool for mapping out complex problems before handing them to Claude Connect Shubhash - Not a Square, now based in Dubai (relocated from London) Seller Sessions is the leading podcast for advanced Amazon sellers, hosted by Danny McMillan. Ritu returns next week for Go With The Flow; Shubhash is back next month.



