§ 01 · The Hook
The bait, then the rug-pull.
The claim lands before the intro music fades: run Claude Code a hundred times cheaper, with a two-line swap and a five-minute setup. Nick Puru then immediately cuts to a polished multi-input dashboard he just built for two cents — the kind of output you'd expect from Opus — and the cost case is made before he even explains how.
What the video promised.
stated at 00:28 "In the next ten minutes I'm gonna be showing you the one prompt that does the entire install, the workflow that cut my Claude bill in half, and most importantly, the specific kind of work where this whole setup actually does fall apart — because nobody's being honest about that." delivered at 12:35
Where the time goes.
00:00 – 00:45
01 · Cold open — claim and proof
Dashboard demo result shown first. Cost: 2 cents. Same quality as Opus output. Promise of honest limitations built into the setup.
00:45 – 01:13
02 · Is it allowed?
DeepSeek officially documented the integration. Not a hack. They published the endpoint and instructions themselves.
01:13 – 02:12
03 · Why the swap works now
DeepSeek v4 dropped in April with MIT license. SWE-bench verified score in the 80% range — same neighborhood as Sonnet 4.6 and Opus 4.7. Open weights, self-hostable.
02:12 – 02:56
04 · Pricing breakdown
Opus 4.7: $5/$25 per M tokens. DeepSeek v4 Flash: 14c/28c per M tokens. Gap shows up fast on real workloads.
02:56 – 03:27
05 · Sponsor — Snapdragon
HP Omnibook X powered by Snapdragon Elite. All-day battery on heavy AI workloads, fans never spin up.
03:27 – 06:39
06 · Setup walkthrough
Navigate to deepseek.com, create API key, paste one prompt into Claude Code: set up DeepSeek as Claude Code provider using official DeepSeek docs method. Claude Code handles the PowerShell profile config automatically.
06:39 – 08:23
07 · Verify and fresh shell
Close terminal, open fresh project folder. Run Claude, type /model — DeepSeek chat already selected by default. /usage shows 13 cents total spend so far.
08:23 – 10:54
08 · Live demo — ROI calculator
One prompt: build a DeepSeek vs Claude Code ROI calculator as a single HTML file with three inputs, live calculations, and a bar chart. Output in 28 seconds. Total cost: 1 cent.
11:17 – 12:35
09 · Sponsor — Snapdragon chip story
7 hours into workday, 10 terminals open, multiple Claude Code sessions, video rendering — no fan spin-up. Dedicated AI engine in silicon keeps CPU free.
12:35 – 16:55
10 · Limitations — the honest breakdown
4 failure modes: (1) MCP servers silently dropped, (2) vision not supported, (3) prompt caching edge case flips savings, (4) multi-file debugging needs 2-3 re-prompts vs Sonnet one-shot.
16:55 – 18:13
11 · Hybrid workflow and CTA
Default to DeepSeek for everyday work. Hit /model for Opus/Sonnet on MCP, vision, or deep debugging. $200/month pilot becomes $20/month.
Visual structure at a glance.
Named ideas worth stealing.
16:55
model
DeepSeek as Claude Code default — hybrid model picker
- Default: DeepSeek chat for routine work
- Flip via /model to Opus for: MCP tasks, vision, multi-file debugging
- Never switch entirely
Set DeepSeek as your global Claude Code default. Use /model to jump to Opus or Sonnet only when the task hits one of the four failure modes. Jump back after.
Steal for Any tutorial on AI cost optimization or operator workflow
13:40
list
Four DeepSeek Failure Modes
- MCP servers (silently ignored)
- Vision / image processing (not supported)
- Prompt caching (Anthropic discount can exceed DeepSeek savings on agent loops)
- Multi-file debugging across large repos (needs re-prompts)
Specific conditions where routing through DeepSeek costs more or breaks functionality vs staying on Anthropic.
Steal for Honest limitations section in any AI tool review or comparison video
Lines you could clip.
00:28
"I ran this for about 2 cents. Is this the price for a stick of gum."
02:50
"The difference on any routine work, it's imperceptible — but the bill, however, is not."
16:33
"If you take one thing away from this video, do not switch entirely."
17:02
"The whole thing that was just too expensive to leave running around the clock just got cheap enough to actually leave running around the clock — and that's the real shift."
How they spent the runtime.
Hook length45s
Info densityhigh
Filler8%
Sponsor blocks
- 02:56 – 03:27 · Snapdragon / HP Omnibook X
- 11:17 – 12:35 · Snapdragon / HP Omnibook X
Things they pointed at.
02:56productHP Omnibook X (Snapdragon Elite)
How they asked for the click.
17:53
next-video
"Check out our free School community and our weekly AI newsletter. If you're a business owner looking to implement AI in 2026, book a call with our team."
Tacked on post-conclusion with three separate asks — community, newsletter, consultation call. Feels rushed after a strong payoff line.
Word for word.
HOOK opening / re-engagementCTA the pitch metaphor analogy story
00:00HOOKWhat if you can run Claude code a 100 times cheaper than whatever you're using right now? Now this is Claude code, but the model under the hood, it actually isn't even Claude. It's DeepSeek v four, the newly released open source model that's essentially just trading blows with Claude on any coding benchmarks.
00:15HOOKAnd this is all with just a two line swap, and it's a five minute setup. And it basically cuts the bill by a 100 x. So I just had to build me this entire dashboard from one prompt.
00:24HOOKBasically, just one shot at it, and it's a polished design. We have all the live calculations, and it took about three minutes from start to finish.
00:31HOOKThis is the kind of output that you would be expecting from one of the top tier models like Opus. Now if we were to take this and do this on Opus, this would have cost me, you know, 10 times the amount. I ran this for about 2¢.
00:41HOOKIs This the price for a stick of gum. Now in the next ten minutes, I'm gonna be showing you the one prompt that does the entire install, the workflow that cut my Claude built in half, and most importantly, the specific kind of work where this whole setup actually does fall apart because nobody's being honest about that. So two questions you're probably already asking about this.
01:00HOOKIt is allowed. DeepSeek, they officially documented this themselves. They even published the endpoint.
01:04HOOKThey published the exact environment variables, and they wrote the instructions for actually connecting their models into ClawdCode, into OpenClaw, and really anything else.
01:15They just want people to actually start doing this. Now the catch is the whole reason this video actually exists. So there is one specific category of work where, you know, this entire thing is breaking.
01:24And the people who got burned trying it earlier this year, they are why most operators still pay full price, and I will get you there. Just stick with me through the entire build. So just real quick on why the swap actually works right now because, you know, just about three months ago, it didn't.
01:37So all these open source coding models, they were very close, but you would just honestly fill the gap on anything past a boilerplate. But that recently changed in April when Deepsea v four dropped. You know, we have the open weights, MIT license,
01:49you know, that just means anyone can self host it. They can fine tune it or just run it locally instead of being, you know, behind a single vendor's closed API. And on the benchmarks that actually matters for coding, it finally caught up with all of this.
02:03So for example, on the SWE bench verified v four pro, it scored in the 80% range. You know, that's the same neighborhood as Sonnet 4.6 and Opus 4.7.
02:12Now on coding tests, v four is basically Sonnet, and on any hard reasoning, it's about 80% of OPUS. So for most of what Claude code actually does day to day, that gap doesn't really show up whatsoever. Now when it comes to the pricing, OPUS 4.7, it's $5 per million input tokens and $25 per million output.
02:29But DeepSea's v four flash, it's 14¢ per million input, 28¢ per million output. In the gap, it really will be showing up quite fast for you, pretty much the moment that you actually start running real workloads for this. I quite literally run three AI companies, and I've been pointing Claude code at this DeepSeek endpoint for the last couple of weeks across all three.
02:48And we're shipping the same code that I was shipping, you know, last quarter on Anthropix API. Now the difference is in actually comparing these two on any routine work, it's imperceptible, but the bill, however, is not.
02:58Now just a quick note, what I'm actually using is to run this entire thing. My laptop, it's powered by Snapdragon, which is effectively what's running this entire stack. And this video, it's actually sponsored by Snapdragon.
03:08So link will be down below in the description to check them out, but I've had this over a couple of weeks now, and I don't throttle on any long coding sessions. My battery lasts all day, and the cost I'm about to walk through, it plays even better when the hardware is not burning power either. Now anyways, for step one, we're just going to navigate over into deepsea.com.
03:27If you don't have an account already, just make sure it's to go ahead and sign up. It's completely free to make, so you only have to actually pay for what you use. And I dropped in about $5 just a couple of weeks ago, and I've barely touched this.
03:39But anyways, once you have signed up for your account, go ahead and navigate over into your API keys, create a new key. We will need this in a second. Now once we actually grab this, it's gonna get a little more interesting because we're just gonna use Cloud Code to actually install everything else, make it extremely simple for us to start using.
03:52Now once we do have our API key, we're just going to utilize Cloud Code to actually install everything for us. Now quick thing that I do want to flag before we actually keep going is that DeepSeek, they officially launched their own documentation showing exactly how to do this. So again, just how to actually connect their models to Cloud Code, and this is not a workaround.
04:09And this isn't some sort of like sketchy workaround or anything like that. This is not a hack. They wrote the instructions themselves.
04:16This is official. So you can see like this is their page. The official method is to copy six lines of code and paste them into a config file on your laptop.
04:23It's a little bit technical, but it does work. Link will be down in the description if you want us to it that way, but let me show you how to actually do it the easiest way. Oh, and one more thing worth knowing is that the same swap, it also works if you're using OpenCode or OpenClaw or Hermes, and DeepSeek officially supports all three of these.
04:37So we're staying on ClawdCode today, but the same idea carries over if your tool choice is going to be different. A pasting environment variables into shell config files is the kind of thing that makes operators, you know, just bounce off tutorials. I'm gonna show you a friend of your path that uses a tool.
04:51Alright. So we have Clog code running inside of our IDE. I'm using Versus code.
04:55You can use whatever you want to actually utilize this. You can use the terminal. You could also use the regular desktop application
05:02of Claude, but we're just going to paste this in. So what I'm saying specifically is set up DeepSeek as my Claude code provider using the official DeepSeek documentation method.
05:12So I'm effectively just copying what is in documentation of DeepSeek. And more importantly, we're going to leverage the power of Cloud Code to make it as simple as possible for us to actually install this system and make it a 100 times cheaper to actually be using Cloud Code moving forward. Now one important thing before we actually do send this off is that key that we actually copied from DeepSeek earlier.
05:32This is where we need to replace it. So right here, we can just replace this with our API key. Now we're just going to press enter, run this off, and really, we're just telling Clog code to do three different things in one prompt.
05:46First, to just go check my shell config file. So that's my file computer, which is going to actually be reading every time that I open a brand new terminal.
05:55And from there, it's going to just clean up any leftover deep seek settings from any older experiments. So we're just going to be starting fresh. So it's asking me how do you want to configure DeepSeek as your quad code provider on Windows.
06:08I'm just going to say a PowerShell profile. Now it's asking, did you mean this for WSL or Linux machine instead of this Windows host? I'm gonna say no configure this Windows machine,
06:18and we'll run that from there. It'll ask for a few more permissions that you wanna proceed with this PowerShell. I'll just go ahead and say yes, but you'll also notice in the prompt that I was asking it to present me the results so that I can just confirm that everything actually worked.
06:30Alright. So everything just finished installing. We got it all wired in.
06:33Now let's actually get started using this. But I do wanna say that when quad code edits your shell config, the terminal that you're currently running this in, it's not going to be picking up the new settings.
06:44So whatever you just installed, only a brand new shell will be picking that up. So instead of trying to refresh this specific window that we have right here, we just have to just close completely, open a fresh new project folder. It's gonna be a lot cleaner that way.
06:58So I went ahead and created a brand new folder. We've got a fresh window. We got a fresh shell.
07:03Now what I'm going to do is I'm just going to open up the terminal, and we're just going to run Claude code. So I'm just going to type out Claude. From here, if we actually expand on this a little bit, you can see it's automatically going to start up Claude for us.
07:15So we could run this in the dark mode, and we'll just press enter. Press enter again and use the recommended settings.
07:21Go ahead and trust this folder. Now we can see Claude code is fully loaded up, and we could expand this as much as we want. And if I just type out model again, we'll be able to pull up all the different models that we will have listed out.
07:33So you could see we have the defaults, of course, Haiku, and then we have down at the bottom, the most important DeepSeek chat. Currently, it's already selected by default because that's what we set in, uh, config. So most of the day, I'm just gonna be on DeepSeek, and I don't really think about it.
07:47And the bill automatically stays very low for us. If I just back out and just say, what model are we running on? You'll see what we get.
07:55We're running on DeepSeek chat. And if I just type out slash usage, we'll actually be able to see all the different models that we are running specifically and what's actually getting the charge.
08:05So DeepSeek, 24,000 inputs,
08:08about 400 outputs. And as you see, I've only spent about 13¢ on this. Anyways, the setup is completely done.
08:14Now let's get into some real stuff. So some quick context before I actually show you the build because this is the actual workflow that I have been running where most of the day, I'm going to be on DeepSeek, ClaudeCode.
08:24It looks completely identical. The work's going to get done. Our bill is going to stay very, very low.
08:29And when I hit something that is going to be heavier where I do need more complex demands from ClaudeCode, that is just where I can actually, you know, have a complex multi file refactor. I can have a vision task, something that just needs deeper reasoning.
08:44I just hit slash model, and I can so easily just flip between utilizing the default Opus 4.7.
08:52So that's gonna be the whole rhythm within this. The default, it's gonna be DeepSeek chat. And then when we do need something a little bit more hands on, then we'll be utilizing the default Opus 4.7.
09:02Now to show you that DeepSeek is genuinely capable of very real work, not just, you know, toy examples. I'm going to give it just one prompt right now and have it build me a real working dashboard. I'm gonna have it build out a calculator that figures out how much you save by routing routine work to DeepSeek.
09:18So this is the most on theme demo that I could actually think of for this I'm just gonna back out of this, and what we're going to paste in is this prompt right here. I'm just gonna run it off. Build me a single page interactive dashboard called DeepSeek versus Cloud Code ROI calculator as just one index HTML file.
09:33So it should take three user inputs. So the monthly Claude code spend in US dollars, the percentage of tasks that are routine slash boilerplates, and then the average deep sea cost ratio versus Claude and defaults to one out of a 100.
09:46Now number two is the live calculate and display. So just give me the monthly savings if it is routine work running to deep sea, the annual savings, the five year savings, and a simple bar chart comparing current versus the per monthly or the new monthly cost instead. Number three is just to use a clean modern design, and I'm just getting a little bit picky about how I want it to actually look.
10:06And then make sure that all values update live as inputs change. No submit button. So we scroll down just a little bit.
10:12We can see it already finished up generating this. I mean, that took how long exactly? That was twenty eight seconds.
10:18So let's open this up and we can before we do that, we could see what it does. So the monthly spend, the routine task slider, and the cost ratio. So I'm gonna open this up real quick inside of our folder.
10:30Cool. So here we are. The DeepSeek versus Claude code RI calculator.
10:33So our monthly Claude code spend, we're just on the $200 subscription. So the routine slash boilerplate tasks, we have about 60%, and we could also configure this as well.
10:42Then we have the DeepSeek cost ratio versus Claude. Now the monthly savings, so it's about a $119 versus $81. Annual savings, it's gonna be about $1,400,
10:52and the five year savings, $7,000. Let's scroll down a little bit further and we can actually see the bar chart. So this is going to compare,
10:59um, Claude plus DeepSeek. And then we scroll down, we can see the bar chart just comparing current, which is just all Claude versus a hybrid of Claude plus DeepSeek.
11:08Now to generate something like this even just a couple of months ago, I mean, we simply would not have been able to create this unless I was using some sort of supercomputer and honestly, like none of the open source models, they just were not there yet, but I genuinely think we are there right now. Now earlier in this video, mentioned I was using a Snapdragon chip and that is quite literally what makes my workdays possible using something like this.
11:31It is what these chips do with AI workloads. So right now as I'm filming this, about seven hours into the workday, Clog code, it has been running builds all in the background, terminals open all over the place, and all the fans, they haven't even spun up once. And the part that actually surprised me the most is it's not just Claude code that's actually staying quiet, it's everything at one.
11:49I have 10 different terminals open. I have multiple Claude code sessions running in parallel in a video rendering on top of that and a browser windows just everywhere. And the chip, it literally absorbs all of this like a bulletproof vest.
12:00And the reason for that is because Snapdragon, it has a dedicated AI engine just built directly into the silicon. The So heavy AI inference work, it doesn't fight the CPU for any power. The CPU, it's instead staying free for the rest of your work.
12:14And that matters for the cost story in this video specifically because the API bill is only half of it. And other half, it's just a hardware actually running underneath that. So if your laptop is just overheating and burning battery every time you run a build like this, you stop running them and then you batch your work, you wait until you're plugged in and you just avoid the long sessions and you're just not leveraging and capitalizing,
12:35um, you know, all the tools at our disposal such as AI. So overall, that's lost productivity, lost time and lost money for you in your pockets.
12:43But anyways, going back to this specific build, I mean, can change this monthly clot code spend, maybe it's gonna be about $300. I usually don't spend more than $300 a month and you can see the savings. About a $170
12:54versus a 122, the annual savings, and of course, the ten year savings as well. Now if we go back inside of DeepSeek, you could see I literally only used 1¢ to build that dashboard.
13:05Now this is why I actually defaults to this for most of my work because it's not just adequate. It's actually very, very good. Now anyways, I do wanna get honest and cover some of the limitations when it comes to actually going with this approach.
13:15So from my experience, I have been just routing my quad code work through DeepSeek for about three weeks now. I love it for what it actually does well, but I'm also gonna tell you exactly what it doesn't do because the operators, the builders, who are actually getting burned trying this early in the year, they got burned on these specific things, and I would rather you know right now.
13:33So four things to be flagging. First one I could actually show you on the screen right now, it's the MCP servers.
13:39So if you use quad code seriously, you've probably been wiring up MCP integrations. You have, like, file system access, linear, notion, whatever it may be. MCP,
13:48it's going to be the protocol that lets ClaudeCode actually reach out and talk to all of your tools. So it's a big part of why ClaudeCode is, you know, powerful for real work. Watch what happens when I actually check MCP
13:59while routed through DeepSeek. I'm gonna type out slash MCP, and it's going to say no MCP servers configured. Please run slash doctor if this is unexpected.
14:07So we're getting nothing, and the reason isn't that I forgot to configure any. It's just that DeepSeek's endpoint does not support the MCP protocol whatsoever. So DeepSeek, they actually officially documented this in their API compatibility table where MCP calls, they're flagged as just being ignored.
14:23So they're not broken. They're not throwing errors. It just quietly dropped it on the floor and they didn't really like regard it whatsoever.
14:30So even if you had 10 MCP servers wired up and working perfectly through Anthropic, the moment you start using DeepSeek, you know, it's not gonna fire any of those. That's why I would be switching back to Opus the second that I am in MCP territory, or you can just go to do something else like utilizing Sonnet or Haiku. You don't need to kill every single process with, you know, high premium model like Opus.
14:51Now number two, it's going to be vision. So if you've ever pasted a screenshot into Claude code just expecting the model to read what's on the screen, you know, like debug a UI bug from, a screenshot, pull data out of a chart or, like, looking at a design, like, capability, it lives on Anthropix side and DeepSeek's coding endpoint.
15:09It doesn't process images whatsoever. So anytime my work involves looking at something visual, I have to flip to a different model from Anthropic like Sonnet or Opus. Number three is the prompt caching.
15:19So this is like the quietest I would say, of all the four. So in Thropic, it gives you a discount when you actually reuse long system prompts across sessions because they cache the prefix on their end.
15:30Right? So for most of what you and I do day to day, that doesn't really matter where each session, it's gonna be completely fresh. But if you run agent loops with massive system prompts that are just going to be repeating all day every day, like maybe an SDR agent or a background worker hitting the API every single minute, the Anthropic cash discount can quietly become bigger than the DeepSeek savings on those exact workloads.
15:55So it's definitely worth modeling all of this out before you actually commit a heavy production workload. Now number four, and this is the one that I've actually felt the most in my actual work, is the multi file debugging across a large code base. So when you are three layers deep trying to just figure out why a request is going to so for example, if you're three layers deep trying to figure out why a request is failing in a multi service repo for you, DeepSeek, it usually needs two or three follow-up prompts where Sonnet would often just one shot it for you.
16:22HOOKSo the token savings, it does vanish on tasks like that because you are having to re prompt, you know, four times instead of just the one shot. So whenever I do hit deep multi file debugging, I flip to Opus, I do that part, I flip right back.
16:36HOOKIf you take one thing away from this video, do not switch entirely. Don't just go straight into DeepSeek as I showed you reasons why. You want to be using the model picker the way that I have been using it.
16:45HOOKSo your default, it points quad code at DeepSeek. That's your everyday setup and most of your work, it runs just right through it. Your bill, it's going to be dropping significantly
16:55and when something hard actually breaks like a multi file bug or a vision task, an MCP heavy workflow, you just hit slash model, pick out Opus or Sonnet, whatever it may be and you can flip to that, flip back later. So with that being said, is only going to be applicable if you are going to be utilizing the API. So some of you, you do utilize a cloud subscription.
17:15So in that case, it's not going to matter as much unless you're constantly hitting your limits. So with that being said, just stop paying full price for Cloud when most of your work, it does not need it. So that's the real unlock.
17:24So if you're an operator running automations or any internal tooling and Cloud Code, this literally turns a $200 monthly pilot into a $20 pilot. So the whole thing that was just just got cheap enough to actually leave running around the clock, and that's the real shift in what is actually worth building right now.
17:43CTABut anyways, just a quick thanks again to Snapdragon for sponsoring this video and for the laptop that is been powering the entire build that you just watched. So link will be down below in the description if you wanna check it out. Highly recommend them.
17:54CTABut any case, thank you guys for watching. If you are interested in getting more hands on approach, learning all stuff like this right when it drops, then make sure to check out our free school community and also our weekly AI newsletter. And if you're a business owner looking to implement AI into your business in 2026, then make sure to book in a call with our team.
18:09CTALink will be down below in the description. But, again, thank you guys for watching. I'll see you in the next video.
— full transcript
§ 05 · For Joe
Steal the hybrid model-picker workflow.
Operator playbook
Default Claude Code to DeepSeek for everything. Flip to Opus only when you hit one of four specific walls.
- Sign up at deepseek.com, load $5, grab an API key.
- Paste one prompt into Claude Code: 'set up DeepSeek as my Claude Code provider using the official DeepSeek docs method' — it configures itself.
- Open a fresh terminal and verify via /model that DeepSeek chat is now the default.
- Learn the four flip-to-Opus triggers: MCP integrations, vision/screenshot tasks, large-repo multi-file debugging, and any agent loop where Anthropic caching math flips.
- Track spend with /usage — most operators report staying under $20/month for workloads that previously hit $200.
- Never pitch this to your audience as a total switch. The hybrid framing is what makes it credible and safe.
§ 05 · For You
What this means if you use Claude Code.
For the builder in the audience
You don't have to choose between cheap and capable — you just have to know which tasks need which model.
- For most day-to-day coding (boilerplate, refactors, new features in existing files), DeepSeek v4 performs at Sonnet level for about 1% of the cost.
- The setup takes five minutes and Claude Code installs it for you.
- Keep Opus or Sonnet one /model command away for the four failure cases: MCP tools, screenshot-based debugging, massive codebase diffs, and heavy agent loops.
- Check your /usage panel weekly — the cost difference becomes visible almost immediately on real workloads.
