AI-FirstAI-First
Back to blog
outils-ia
September 19, 2026
10 min read

Claude Code review: what 6 months with SME clients actually taught me

Does Claude Code deserve the glowing reviews? After 6 months using it with my SME clients, here are the real gains, the hidden costs and what still breaks.

Vincent

Vincent

AI expert, AI-First

Claude Code review 2026: real costs, SME use cases, limits and alternatives tested. An honest verdict from an AI trainer after 6 months in the field.

Does Claude Code deserve its reputation as the tool that gets you hooked? After six months of using it myself and training SME leaders on it, my answer is yes for technical profiles, and no without support for everyone else. The gap between those two audiences is the real story that online reviews rarely tell.

  • 📈 Developers have adopted it hard, engineers burning 700 million tokens a day, usage that tips into openly admitted dependence.
  • ⚠️ The real bill is underestimated, a $200/month subscription can hide up to $1,800 of actual cost across two heavy days.
  • 💡 Delivered in 9 days for an SME, a quote configurator built with Claude Code, at one twelfth the budget of a traditional agency.
  • 🎯 The terminal is still the real barrier, without a technical foundation the tool frustrates more than it helps, whatever the "for everyone" marketing says.

I have been training French SMEs on Claude Code since spring 2026. I have watched developers use it like a senior colleague, and I have watched non-technical executives give up after twenty minutes staring at a terminal. This article pulls together what the most-watched videos and forum threads say on the subject, what my own numbers show, and what I actually delivered for a client.

Why developers (and I) became dependent on Claude Code

Alberta Tech, a YouTube channel followed by engineers, devoted an entire video to this collective obsession: developers posting on Twitter about their Claude Code usage the way other people talk about an addiction. One user even asked on Hacker News how to "set limits", and the top-voted answer was: have kids.

This is not just niche humour. An engineer with 14 years at a big tech company (MAG7) describes on r/ClaudeCode comparing about a hundred hours with Claude Code against twenty or so with Codex, on a real 80,000-line project in Python and TypeScript with close to 2,800 tests. His conclusion: both tools produce correct code, but Claude Code does better on architecture and cross-file consistency.

What is Claude Code, exactly?

Claude Code is a coding agent built by Anthropic that works directly in the terminal, in an IDE like VS Code, or in a desktop app. Unlike Claude on the web, it has direct access to a project's files: it can read an entire codebase, edit several files at once, run tests and fix what breaks, with no manual copy-pasting.

That difference, direct filesystem access rather than a plain chat window, is what explains the gap with other AI assistants. The time saved does not come from smarter answers, it comes from autonomous execution. On impli.fr, a consultant who has been using the tool for six months with his SME clients makes the same point: unlike the other AI tools he tested, Claude Code works on local files without copy-paste and can handle several tasks in parallel.

What I delivered for an SME client with Claude Code, end to end

Full disclosure: I train SMEs on Claude Code at AI First, so my enthusiasm is not disinterested. It also comes from more than 200 hours of field feedback with non-technical executives, not from an off-the-shelf sales pitch.

In March 2026 I delivered an internal quote configurator built with Claude Code for an e-commerce client. Nine days of work, for a budget of roughly 1,200 euros of engineering time, where a traditional agency would have billed around 15,000 euros for the same functional scope. The client had no technical skills in-house: I carried the project, but the execution speed genuinely came from the agent, not from me typing faster.

It is not an isolated case. Jedha, an AI training school, reports the case that went viral in early January 2026 of a Google engineer whose tweet explained that Claude Code had reproduced in one hour a project that had taken her team a year. The details change, but the order of magnitude keeps coming back in these accounts: what used to take weeks takes days.

What does Claude Code really cost an SME?

This is the point most mainstream reviews dodge. Jordan Urbs, a YouTube creator and solo entrepreneur, cancelled his $200-a-month subscription despite the tool being "absolutely essential" to his work. The reason: over his last 30 days of subscription, he went past 700 million tokens per day twice. At API rates, those two days alone would have cost more than $50,000, and even with caching and discounted pricing, around $1,800.

For an SME starting out, that extreme scenario is not the norm. But it illustrates a real risk: a flat subscription hides consumption that can explode. One developer who analysed three months of his own Claude Code sessions with an open source tool (TokenScope, posted on r/ClaudeAI) put his usage at $4,935 in API-equivalent terms across 60 sessions, with 455 failed tool calls accounting for roughly $201 of "rebilling" tied to those failures. His most profitable finding: a 95% cache hit rate saved him close to $15,600 on a single project.

The limits the glowing reviews leave out

Everything above assumes a user who already knows how to code. That is where the gap between developer reviews and the reality of an SME becomes sharpest.

On its blog, École Cube sums up the constraint well: Claude Code requires command-line fluency, precise requests and systematic human review. That is not a technical footnote, it is the filter that decides whether a non-technical executive can use it alone or not. I have watched SME clients give up within twenty minutes in front of an empty command window, while the same client found Claude Cowork (the web interface) immediately readable.

A Reddit thread on r/ClaudeCode points to another, subtler flaw: the tendency of AI agents to overdo it. One developer built a plugin ("Ponytail") to force Claude Code to write the minimum code necessary, after finding that a simple email validation task produced a 27-line class with a wrapper and a shaky regex. His benchmark across five tasks: 16% fewer tokens, roughly 4 times faster, and a dashboard that went from 190 lines to 13 once the over-engineering was stripped out.

I see it with my own clients: the problem is almost never the AI's capability, it is the lack of a clearly framed requirement. A more critical post, published on r/ClaudeCode by an engineer who has worked at several Silicon Valley companies, captures the opposite frustration: a lot of developers "prompt blind" without checking the output, producing code he himself calls "slop". The real bottleneck is still human, not technical.

Do you need to know how to code to use Claude Code?

Not necessarily, but you have to accept a genuine learning curve. On her Substack, Daria Viktorova, a trainer who describes herself as non-technical, tests Claude Code alongside Claude Cowork after several months of using Claude for writing. Her take: at her level, "we'll see how far this goes", which is proof the tool can be learned but cannot be guessed.

For an SME leader with no technical background, I always recommend starting with a concrete, narrow use case (a script, a simple automation) before taking on a full project. I laid out that progression in a step-by-step tutorial written for SMEs, with the basic commands and the classic day-one traps.

Claude Code versus Cursor, Codex and Kimi K3: who actually wins?

The comparison most cited in recent reviews comes from a user on r/programmation who had the same app (a React board game) built by Codex, Claude Code and Kimi K3, using the same prompt for each. His verdict: Codex is fast and cheap, but only does half the expected work and produces code that is hard to read. Claude Code and Kimi K3 are neck and neck on quality, each with its own drawback: price for Claude Code, development time for Kimi K3.

On insideapp.fr, a mobile developer compares Claude Code to Copilot and Cursor on a different criterion: the "prompt, plan, implement" workflow, which to him feels like real collaboration rather than glorified autocomplete. I dug into that comparison in more depth in a Claude Code versus Cursor breakdown for teams weighing up the two approaches.

Tool Indicative price Main interface Best for
Claude Code $20 to $200/month (Pro to Max) Terminal, IDE, web Complex refactoring, large projects
Cursor From $20/month Dedicated IDE Developers who want to stay in a classic editor
Codex (OpenAI) Included with ChatGPT Plus/Pro Terminal, IDE Quick tasks, tight budgets
Kimi K3 Usage-based pricing, generally lower Terminal Quality close to Claude Code, if you can wait

SOURCE: cited transcripts and Reddit threads · UPDATED 09/2026

According to Gartner, by 2028 around 75% of enterprise software engineers will use an AI coding assistant, up from less than 10% in early 2023 (gartner.com). That trajectory matches what I see in the field with my clients: the question is no longer "should we try a coding agent", but "which one, and for what".

"The best AI system becomes invisible: it slots into daily work and saves time without friction. Claude Code is not invisible yet, but it comes closer than any tool I have tested with my clients."

Vincent, September 2026

On ai-first.fr, the Claude Code tutorial article I published sits at an average position of 8 on Google with just 4 clicks last month, a modest but clear signal: demand for concrete, first-hand accounts exists, and most of the available content stays too theoretical for a busy executive.

So does Claude Code deserve the glowing reviews? Yes, with one condition few articles state plainly: somebody has to frame the requirement, validate the output and watch the bill. For a senior developer, the tool delivers on its promise and saves real time, measured in days rather than hours on a project like the one I shipped in nine days. For an SME leader without support, it remains too demanding to use alone, whatever the marketing suggests.

My practical advice: never start with a full project. Test Claude Code on one repetitive, expensive task, measure the time saved and the real token cost, then decide whether moving up a plan is justified. I have detailed the switching thresholds between Claude Pro and Claude Team in a guide on usage volume in SMEs if you want to run the numbers on your own case. For companies that would rather hand over the technical implementation entirely than steer the tool in-house, the GoLive Software blog covers how to structure a development team around this kind of project.

Frequently asked questions

Is Claude Code really worth the subscription cost?

For regular professional use, yes: the $20-a-month plan hits its limits quickly, but a higher plan still costs far less than a freelance developer doing the same volume of work. The thing to watch is token consumption, which can climb very fast on large projects, as the $1,800 across two heavy days shows.

Is Claude Code suitable for someone who cannot code?

Partly. The terminal interface remains a real obstacle for a non-technical executive, and human review of the generated code is needed at every step. A simple, well-scoped use case with support at the start works far better than a full project launched solo on day one.

What is the difference between Claude Code and Claude on the web?

Claude on the web answers through chat, with no direct access to a project's files. Claude Code runs in the terminal or an IDE with full access to the codebase: it can read and edit multiple files, run tests and fix errors without any manual copy-pasting.

Is Claude Code better than Cursor or Codex?

It depends on the criterion. On code quality, Claude Code and Kimi K3 come out ahead of Codex in several independent comparisons. Cursor is still preferable for developers who want to stay in a classic editor rather than a terminal. Codex remains the cheapest option when budget outweighs final quality.

How do you avoid overpaying with Claude Code?

Watch the cache hit rate of your sessions (95% cache usage saved one user around $15,600 on a single project), avoid having long documentation files re-read in every session, and start on the lowest plan before moving up if the limit becomes a genuine blocker.

Vidéos YouTube

Discussions Reddit

Articles & blogs

Articles & ressources

Take action with AI-First

Transform your business with AI. Audit, implementation and follow-up by certified experts.

Request an audit →

More articles