DeepSeek vs Claude: what $1,000 of real build work showed

I am not a DeepSeek fan by default. I teach Claude workshops at universities in Lebanon, I hold Anthropic credentials, and I build AI agents for businesses. Claude is the model I know best. So this is not a fan letter. It is what we saw when we used both models on real build work.

We built two real products: a WhatsApp bot and a business intelligence platform. The work was backend engineering and UI and UX design, and it used about $1,000 of tokens across Claude and DeepSeek. On that work DeepSeek got through more for the money, about 90% of its results matched what Claude produced, and the same work cost about 40% less. These are our own figures from our own build work, by our own estimate. It was not a controlled lab test and it is not a published statistic.

Two projects are a small sample, so I did not stop there. I went looking for independent evidence, including the evidence against DeepSeek. It agrees with the direction of our result and disagrees on the size. Claude is still better at the hardest work. DeepSeek is far cheaper, and for a lot of daily business work the quality gap does not change the outcome.

Every figure below is one of three kinds: sourced (with publisher and date), our own, or modelled (with its assumptions shown). Prices and models were checked on November 11, 2026 and change often. See how we publish.

What DeepSeek is today

DeepSeek is a Chinese AI lab that publishes its models with open weights, which means anyone can download and run them. The current model for most work is DeepSeek V4.1 Flash, called deepseek-flash in the API.

• April 24, 2026: DeepSeek released V4 Pro and V4 Flash, both with a 1 million token context window and open weights (DeepSeek API docs).
• September 10, 2026: DeepSeek released V4.1 Flash, with 552 billion parameters and native image input. DeepSeek says it beats V4 Pro on performance, cost and speed. That is the company's own claim (DeepSeek API docs).
• September 14, 2026: DeepSeek began routing deepseek-v4-pro requests to V4.1 Flash at Flash prices, until a V4.1 Pro launches (same announcement).
• October 17, 2026: the model behind deepseek-flash became V4.1 Flash 1017 (DeepSeek API docs home).

The price

Per token, DeepSeek Flash costs roughly 92% to 97% less than Claude Opus 5.5. Prices are in US dollars per 1 million tokens, as listed in November 2026.

DeepSeek prices are from SiliconFlow (September 28, 2026) and NxCode (updated November 9, 2026). Opus 5.5 prices are from Artificial Analysis. These are third party pages, so confirm on the official pricing pages before you budget. Peak hours are 01:00 to 04:00 and 06:00 to 10:00 UTC, Monday to Friday. In winter that is 03:00 to 06:00 and 08:00 to 12:00 in Beirut. Everything else is half price.

Modelled example. Take a job that reads 10 million tokens and writes 2 million, with no caching and no retries. On Opus 5.5 that costs $80. On DeepSeek Flash at peak prices it costs $5.40. The same $1,000 buys about 12 such jobs on Opus and about 185 on DeepSeek. This is arithmetic on list prices, not a measurement.

Why our work showed 40%, not 95%. Our own build work came out at about 40% cheaper, far below the gap on the price list. I did not measure the reasons, but the likely ones are visible in independent data. DeepSeek writes a lot of reasoning text before it answers, and that text is billed. Bito measured about 3,600 output tokens on one long task, against 700 to 900 for the earlier model (Bito, October 24, 2026). Add retries and the human time spent checking answers, and the real gap shrinks.

Why it is this cheap: the engineering

The low price is not only a discount. It comes from design choices that make each token cheaper to compute. These are the terms developers use, in plain words.

• Mixture of Experts (MoE) with sparse activation. The model has 552 billion parameters, but only 8 billion are active for each token it reads and 16 billion for each token it writes. Each written token uses about 3% of the model (DeepSeek technical report, arXiv, September 17, 2026).
• Causal Encoder-Decoder (CED). One half of the network reads the prompt and the other half writes the answer. DeepSeek says this roughly halves the compute for reading a prompt, which engineers call prefill (same report).
• KV cache compression. The KV cache is the model's working memory of your conversation. V4.1 Flash stores 890 bytes per token, about a quarter of V4 Flash, so a full 1 million token prompt needs under 1 GB of it. It does this with Compressed Sparse Attention 2 (CSA2), which reuses the cache across layers, and FP4 caching, which stores it at lower precision (arXiv report and the vLLM recipe, updated November 5, 2026).
• Long context that stays cheap. Going from a 4,000 token context to 1 million raises the compute per written token by only about a quarter, according to the report.
• Prompt caching priced near zero. An agent resends the same instructions and history on every step. DeepSeek bills those repeated tokens, called cache hits, at $0.006 per million at peak, which is 2% of the normal input price. For agents, this matters more than the headline price.
• Drop in compatible. The API accepts both the OpenAI and the Anthropic request formats, so it runs inside tools such as Claude Code and OpenCode without rewriting your agent (DeepSeek API docs).
• Open weights you can host. The reference recipe needs about 614 GB of GPU memory, for example one 8 GPU H200 node, with weights quantized to MXFP4 and FP8. That is data centre hardware, not an office PC, but it means you are not locked to one vendor (vLLM recipe).

What developers report

These are individual accounts from public forums, not controlled tests.

• On Hacker News, in a thread titled "Why isn't the industry freaking out about DeepSeek 4.1 Flash?" (about October 7, 2026, 990 comments), user georgel reports running DeepSeek behind the Claude Code harness for 5 to 8 hours a day. User pimeys says nearly all of their input is cached, which keeps spend at roughly $5 to $10 a day.
• On Reddit's r/LocalLLaMA, user Comfortable-Rock-498 tested the earlier V4 Flash on large code changes and reported more than 100 tool calls with zero errors, including multi file edits, but slow generation. We read this through a third party summary of the original post.
• The same Hacker News thread carries the warnings. Your real price depends on your cache hit rate and how long the cache lives. Third party hosts do not all serve the model at full precision, and hosting it yourself is the only way to be sure. Not every host offers zero data retention.

How good it is

On the hardest tests Claude Opus 5.5 is clearly ahead. On everyday work DeepSeek comes close, at a small fraction of the cost. Four independent sources, each with limits.

1. A coding test with costs. Bito (October 24, 2026) ran real agent coding tasks from its own services and had a judge score each answer against an answer key.

On long sessions DeepSeek reached about 89% of Opus's score at about 3% of the cost. It lost most on implementing fixes (68% against 85%), auditing (70% against 82%) and analysing failures (75% against 90%), and it was slower. Bito's own advice is to use Opus for implementing and auditing code changes. Limits: Bito sells coding agent products, the judge was Opus 5.5, and the Claude numbers came from earlier runs on the same tasks. That shape matches our own result: about 90% of the outcome at a much lower price.

2. The general intelligence index. On Artificial Analysis, Opus 5.5 at maximum effort scores 59. DeepSeek V4.1 Flash at maximum effort scores about 40 on an earlier version of the index, as reported by SiliconFlow. The index has been revised, so treat this as a rough gap.

3. The US government's evaluation. NIST's Center for AI Standards and Innovation tested DeepSeek V4 Pro and found it trails leading US models by about 8 months. It also found DeepSeek's own numbers flattering. CAISI still called it the most capable Chinese model it had evaluated (NIST, May 1, 2026).

4. Mixed rankings. On Vals AI (April 2026), V4 Pro ranked second among open weights models on the Vals Index, yet only 36th of 88 on SWE-bench and 89th of 151 on LegalBench among all models.

DeepSeek's own headline wins over Claude compare against Claude Opus 5, not Opus 5.5, as Kie.ai notes. Treat vendor tables as marketing until someone else repeats them.

Why I see real value in it

This section is my own view, not a sourced finding.

Most business work is repetitive, structured and easy to check: reading messages, sorting them, extracting details, drafting replies, summarising documents, preparing a first analysis. For that kind of work, the extra quality of the most expensive model rarely changes the result. The price does change what a business can afford to automate.

That is the real value. When a model costs 90% less per token, and about 40% less in our own build work, a task that was too expensive to run all day becomes cheap enough to run on every message. For small and mid size companies in Lebanon and the Gulf, that is the difference between an agent they can afford and one they cannot.

A sensible setup is not one model for everything: DeepSeek by default, Claude when the task is hard, high stakes, or touches tools that can act on the world.

Why I suggest DeepSeek for a new startup or a working business

This is my recommendation, based on the evidence above and on what I see in my own work.

• Your runway lasts longer. A startup's AI bill grows with every user. On list prices, the same budget buys many times more tokens on DeepSeek than on a top closed model. That is more experiments, more features and more months before the bill becomes a problem.
• You can afford to test before you commit. When a test run costs cents, you can try ten ideas instead of one. For a young company, learning speed matters more than a few points of benchmark score.
• You are not locked in. The API follows the OpenAI and Anthropic formats, so moving a task to Claude later is a small change, not a rebuild. The weights are open, so you can also change host or run it yourself as you grow.
• It fits how agents really work. Agents repeat the same context on every step. With cache hits priced at 2% of normal input, the long running agents that small teams need become affordable.
• A working business can start without risk. Keep what you have. Move one repetitive, easy to check task to DeepSeek, measure it for a month, and expand only if the numbers hold.

My suggestion for any new startup or working business: start on DeepSeek for the daily volume, keep Claude for the hard and high stakes work, and let your own test decide the split. The exception is sensitive or regulated data. Read the limits below before you send any.

The honest limits

The case against DeepSeek is real. These are the points I take seriously.

• Where your data goes. The US Department of Homeland Security barred civilian federal agencies from buying DeepSeek products, citing data stored on servers in China (CyberScoop, October 19, 2026). Keep sensitive client data off DeepSeek's own servers. The weights are open, so a trusted host or your own server is an option.
• Agents being tricked. In CAISI's tests of older DeepSeek models, agents were on average 12 times more likely to follow malicious instructions than US reference models, and a common jailbreak worked on 94% of overtly malicious requests against 8% (NIST, September 30, 2025). We found no repeat of that test for V4.1 Flash, so assume the risk is still there. Give agents minimum permissions, and have a human approve anything that spends money or sends a message.
• Biased answers. The same report found DeepSeek models repeated inaccurate Chinese government narratives four times as often as US models. Do not rely on it for political, news or reputation questions.
• Hardest tasks. Hard implementation, audits and long multi step reasoning still belong with Claude, as the tests above show.
• Moving target. DeepSeek retired two model names on July 24, 2026 and rerouted another on September 14, 2026. Pin the model name and test again every month.

How to test it yourself in one afternoon

1. Pick 20 real tasks from your business where you already know a good answer.
2. Run each one on DeepSeek and on Claude with the same instructions.
3. Score the answers without knowing which model wrote which.
4. Add up the full cost, including retries and the time a person spends fixing mistakes.
5. Make DeepSeek the default where it scores close to Claude, and keep Claude for the rest.
6. Keep sensitive data away from DeepSeek's own servers, and limit what any agent can do.
7. Run the test again next month, because the models change fast.

If you want this set up for your business, our AI systems team builds and tests agents on the model that fits the task, not the one with the most hype.

Frequently asked questions

Sources

• DeepSeek API docs, V4 Preview Release (April 24, 2026), for the V4 release, the 1 million token context, open weights, and the OpenAI and Anthropic compatible API.
• DeepSeek API docs, V4.1 Flash announcement (September 10, 2026), for the V4.1 Flash release, the company's claim against V4 Pro, and the rerouting of V4 Pro requests.
• DeepSeek API docs home, for the current model behind deepseek-flash.
• DeepSeek technical report on arXiv (September 17, 2026), for the parameter counts, the encoder and decoder design, and the KV cache figures.
• vLLM recipe for DeepSeek V4.1 Flash (updated November 5, 2026), for the hosting hardware and quantization.
• SiliconFlow (September 28, 2026) and NxCode (updated November 9, 2026), for DeepSeek API prices and peak hours. Both are third parties.
• Artificial Analysis, for Claude Opus 5.5 prices and its Intelligence Index score.
• Bito (updated October 24, 2026), for the coding test scores and costs. Bito sells coding agent products.
• NIST CAISI evaluation of DeepSeek V4 Pro (May 1, 2026), for the 8 month gap.
• NIST CAISI evaluation of DeepSeek models (September 30, 2025), for the agent hijacking, jailbreak and narrative findings on older models.
• CyberScoop (October 19, 2026), for the Homeland Security order.
• Vals AI (April 2026), for the V4 Pro benchmark rankings.
• Kie.ai (updated November 1, 2026), for the note that DeepSeek's own tables compare against Claude Opus 5.
• Hacker News thread (about October 7, 2026) and the summary of the r/LocalLLaMA post, for the developer accounts.
• Our own data: about $1,000 of tokens spent on Claude and DeepSeek while building a WhatsApp bot and a business intelligence platform (backend engineering and UI and UX), by Byblos Horizon. The 90% and 40% figures are our own estimate and are not independently verified.