AI-First
One month of a Claude Code subscription was all it took for a Chilean small business to replace an ERP it could not afford. That is the story told on r/chileIT by a user who never learned to code, and who delivered his mother an invoicing system that still runs today on a Raspberry Pi. The story raises a very specific question: how do you orchestrate a real coding project with Claude Code when you have neither a technical team nor the budget for an agency?
- 🚀 An in-house ERP in two weeks, a user with no developer training replaced Excel with real software using Claude Code.
- 🧠 Three levels of use, conversation, builder mode, agent: most business owners never get past the first.
- ⚙️ Three orchestration methods, subagents, Agent Teams and Dynamic Workflows each fit a different project size.
- ⚠️ The DIY orchestrator trap, automating the management of entire projects is tempting, and expensive when poorly scoped.
I have been training small-business owners on Claude Code for several months, and this case is a textbook example of what I keep seeing: the blocker is almost never technical, it is methodological. This article covers what was built and how, then explains the three levels of orchestration Claude Code offers today so that a project like yours does not stall at the demo stage.
A non-developer replaced Excel with real software using Claude Code
The family business ran its finances the way thousands of small companies do: Excel for everything, emails with attachments flying in every direction, and paper. A conventional ERP (Kame, Bsale, Laudus and Manager are named in the original post) was out of reach once licence costs and implementation fees were added up.
The author tested Gemini, Codex and Claude Code on the same starting idea: track invoices, manage accounts payable, and keep books that comply with Chile's 14 TER tax regime. After a few weeks of structured prompts and feature-by-feature testing, he shipped a working system, hosted locally on a Raspberry Pi, with no cloud dependency. The software keeps running even when the fibre connection goes down.
How did a non-developer build this in-house software?
The method he describes comes down to three repeated steps: describe a precise need to Claude Code, validate each feature once it is coded, then import the historical data from the existing Excel files. He then asked Codex and Gemini to audit the resulting code for security flaws, a cross-checking habit he himself flags as imperfect for an amateur system, but good enough for a tool that only ever lives on the company's local network.
This result is not a one-off. It is exactly what Claude Code's agent mode promises, and exactly what most users never actually tap into.
Why most business owners stay stuck at the conversation level
A video from the AI Master channel breaks Claude usage into three levels, and most professional users stay stuck on the first without knowing the other two exist. Level one is the classic conversation: ask a question, get an answer, ask another. Useful, but it amounts to using a sophisticated search engine.
Level two is builder mode: you ask Claude to produce a deliverable (a script, an email, a document analysis) but every step is still driven by hand. Level three, the one that actually matters for a full coding project, is agent mode: you give a final objective, not a list of instructions, and Claude breaks the task down, runs each phase, checks its own work and delivers a result.
Why does the conversation level hold a real project back?
A project like the Chilean ERP would never have shipped at the conversation level, because every feature (invoices, accounts payable, historical data import) involves a chain of decisions no non-technical owner can arbitrate by hand on every turn. Agent mode is what absorbs that complexity: the user validates the result, not each intermediate micro-decision.
Once you adopt agent mode, a second question comes up straight away: what do you do when a single agent is no longer enough, because the project has outgrown one session?
Subagents, Agent Teams and Dynamic Workflows: which orchestration for which job?
That is precisely the subject of a video from the DIY Smart Code channel on Anthropic's dynamic workflows. The starting problem is structural, not a settings issue: every subagent reports back into a single context window, the main agent's, which has to absorb it all. The more workers you add, the closer that window gets to saturation.
The analysis describes a three-rung ladder. First rung, classic subagents: the main agent spawns and coordinates workers one at a time, which remains the simplest entry point for a modest project. Second rung, Agent Teams: several agents talk to each other directly through a shared task list, without routing everything through a central coordinator. A video from the Julien Sanson | Automatisation & AI channel notes that this feature shipped with Opus 4.6, whose context window went from 200,000 to 1 million tokens, which makes it possible to run several agents in parallel on the same job.
This architecture has a documented limit: coordination between teammates is expensive in tokens, which caps an effective team at three to five members according to the DIY Smart Code video, and the whole team vanishes if the session crashes. Third rung, Dynamic Workflows, released as a research preview on 28 May 2026 according to Ken Huang's analysis on Substack: Claude generates an orchestration script on the fly, capable of running dozens to hundreds of subagents in parallel, with adversarial agents that check the others' output before final validation.
Subagents, Agent Teams or Dynamic Workflows: which one should you pick?
The choice depends on the actual size of the job, not on the urge to look sophisticated. For a project like the Chilean ERP, classic subagents are more than enough: one feature at a time, validated before moving to the next. Agent Teams start to make sense when several modules need to progress in parallel with a genuine need for coordination (front end and database at the same time, for example). Dynamic Workflows target enterprise-scale work where the load exceeds what a handful of agents can absorb, and are currently limited to the Max, Team and Enterprise plans according to the same source.
On the technical side, the Shipyard blog notes that enabling Agent Teams requires Claude Code 2.1.32 at minimum, with the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS environment variable switched on. A technical detail, but one that saves a non-developer from hunting for a feature that stays off by default.
Project mode: the memory that saves you from explaining everything twice
Efficient orchestration is worthless if every session starts from scratch. That is the job of Claude's project mode, described in a video from the ThomRichard channel as the equivalent of a dedicated desk in a coworking space, as opposed to a hot desk where you have to unpack everything each morning.
Project mode bundles three things that persist from one session to the next: custom instructions (tone, audience, available tools), knowledge files (context documents, style examples), and a project memory that updates as you go. On a job like the Chilean ERP, project mode would have saved him from restating the 14 TER rules or the structure of the already-imported Excel files in every prompt.
How does project mode save you from re-explaining everything each session?
Project mode walls memory off per project: what was decided on one job does not bleed into the others, and Claude remembers decisions already made instead of asking again. This is the piece that turns a string of isolated conversations into genuine project follow-through. For an owner running several AI projects in parallel, this detail, more than the choice between subagents and Agent Teams, is often what separates a project that moves forward from one you keep restarting.
| Orchestration method | What it does | Main limitation | Suited to |
|---|---|---|---|
| Plain conversation | Question, answer, manual iteration | No real delegation | One-off research |
| Builder mode | Produces a deliverable on request | Every step still driven by hand | Small isolated tasks |
| Subagents | One main agent delegates and coordinates | Context window saturates past a few agents | Solo project such as a small-business ERP |
| Agent Teams | Agents in parallel, direct messaging | High coordination cost past 3 to 5 members | Multiple modules at once |
| Dynamic Workflows | Orchestration script generated on the fly | Limited to Max/Team/Enterprise plans | Large-scale enterprise work |
SOURCE: cited transcripts (AI Master, DIY Smart Code, Julien Sanson) and kenhuangus.substack.com · UPDATED 09/2026
What a Claude Code project really costs (and where it breaks)
Once you have subagents and project mode down, the next temptation is almost always the same: automate the coordination itself. A user on the r/ClaudeAI subreddit turned one Claude Code session into a "CEO" that routes tasks to separate worker sessions, keeps a register by state (open, in progress, in review, done), and only accepts a "done" status after checking it against the project's Git history and changelog. That safeguard is not trivial: the author explains he had been burned too many times by an agent announcing "done" when nothing had been verified.
Another thread, on r/aiagents, shows the opposite drift: a user builds a "master harness" that orchestrates Claude, Codex, Gemini and a local model across several physical machines, with arbitration layers between models. He asks the question himself in his title: is he over-engineering his own project? That is exactly the risk I see among small-business owners discovering orchestration: building a system that impresses in a demo, but is too complex for one person to maintain.
"The best orchestration system is not the one with the most agents, it is the one that stays invisible in the daily life of the team using it."
Vincent, September 2026
I train small-business teams on Claude Code, so my enthusiasm for these tools is not disinterested, but it also comes from dozens of hours spent watching where things actually break: almost always at the moment the owner adds a layer of orchestration before having a single use case that genuinely works. According to Gartner, by 2028, 33% of enterprise applications will include agentic AI, up from less than 1% in 2024: the wave is coming, but it does not excuse skipping the small start. On ai-first.fr, my article on the French-language Claude Code tutorial has 34 clicks and 2,734 impressions over the last thirty days according to my Search Console (May 2026): a modest volume, but one that confirms demand is for the concrete, not for orchestration theory.
To go further on the features that make agent mode genuinely usable day to day, I have written up 12 Claude Code features most users never touch. And if your project is mostly about automating repetitive tasks rather than building full software, the Claude Cowork guide covers complementary ground. On the ecosystem side, community projects such as the barkain/claude-code-workflow-orchestration plugin (85 GitHub stars, 13 forks) or oh-my-claudecode (39,000 GitHub stars according to its own page) are trying to automate this orchestration choice, proof that the question goes well beyond a single isolated use case. For the development side through an agency, when the project outgrows what a small company can absorb alone, the GoLive Software blog covers the practical aspects of integrating technical teams.
The verdict: start with one subagent, not an orchestrator
The question posed at the top was simple: how do you orchestrate a real coding project with Claude Code without a technical team or an agency budget? The answer comes down to a clear hierarchy. For a first project, a classic subagent in project mode is enough, exactly as the Chilean ERP demonstrated in a few weeks. Agent Teams only earn their keep when several modules genuinely need to advance in parallel. Dynamic Workflows remain a large-enterprise tool, not a starting point.
The real risk is not under-using Claude Code, it is jumping straight to orchestration before you have a use case that works. Start with one precise, measurable task you can test within a few days. Add another agent only when the first becomes a genuine bottleneck, not before.
Frequently asked questions
Do you need to know how to code to use Claude Code on a real project?
No. The Chilean ERP case shows it: a user with no developer training shipped working software by iterating through prompts and validating each feature one by one. The skill that matters is the ability to describe a business need precisely, not the syntax of a programming language.
What is the difference between subagents and Agent Teams in Claude Code?
Subagents all report back to a single main agent, which becomes a bottleneck past a few workers. Agent Teams talk to each other directly through a shared task list, without routing everything through that central coordinator, but coordination cost caps an effective team at three to five members.
Are Dynamic Workflows available to every small business?
Not on every plan yet. According to Ken Huang's analysis, the feature, released as a research preview in late May 2026, is available on the Max, Team and Enterprise plans, via the Claude Code CLI, the VS Code extension, the desktop app and the Claude API. A small business starting out rarely needs that level of orchestration on its first project.
How long does a project like the Chilean ERP take?
The original post mentions a few weeks of full-time work, at a cost equal to one month of a Claude Code subscription. The real timeline depends mostly on the number of features to validate one by one and the volume of historical data to import.
Does project mode replace Agent Teams?
No, the two answer different needs. Project mode preserves the memory and context of a job from one session to the next. Agent Teams exist to move several workers forward in parallel within a single session. A well-run project often combines both: project mode for continuity, subagents or Agent Teams for execution.
Vidéos YouTube
- How to Build an AI Agent with Claude Code (Claude AI Agent Tutorial) — AI Master
- Workflows inside Claude: Is This the End of Manual AI Agent Orchestration? — DIY Smart Code
- 3 minutes pour comprendre : les projets dans Claude AI — ThomRichard
- La NOUVELLE fonctionnalité AGENT TEAMS de Claude Code est INCROYABLE (Opus 4.6) — Julien Sanson | Automatisation & AI
Discussions Reddit
- Implementé un sistema de finanzas y cotizaciones para una pyme desde cero a puro claude code, sin ser programador — r/chileIT
- I turned one Claude Code session into a "CEO" that manages all my side projects — r/ClaudeAI
- Building a "master AI harness" to orchestrate Codex/Claude/Gemini/Kimi + local Qwen across multiple PCs — am I overengineering this? — r/aiagents