Introduction
These days, "I built X with AI alone" posts are everywhere. For personal projects, it feels like this has become the new normal. Yet in professional software development (by which I mean contract-based system development for clients), I've never heard anyone say "we built it with AI alone."
So why, despite all the progress AI has made, do professional projects still not go "AI only"?
I want to nail down my own answer to this question now — so that when AI capabilities increase even further, I have a benchmark to revisit and ask: "Does that change anything?"
My conclusion: it comes down to responsibility.
Breaking Down "Responsibility"
A contract for system development cannot include a clause like: "Built entirely by AI, so humans accept no liability for bugs." (Deeply discounted, of course!)
So what does "responsibility" actually mean in a contract context? It breaks down into roughly three things:
- Warranty period (free bug fixes) — The work of fixing bugs can involve AI. But the liability itself — handling damage claims or contract termination — can only be borne by humans.
- The commitment to do everything possible when something goes wrong — Apologizing, coordinating, explaining preventive measures. Only humans can do this. AI cannot.
- The resolve to minimize bugs as close to zero as possible — Even humans can't promise perfection. But a human can say "we will do our absolute best." AI famously cannot guarantee zero bugs, and everyone knows it.
In short: only humans can be held responsible — and that's the fundamental reason "AI only" is a step no one takes in professional development.
Systems Where AI Alone Is Dangerous
With that understanding of responsibility, these domains still require human involvement:
| Domain | Why |
|---|---|
| Healthcare (diagnosis, medication, etc.) | Directly affects life and death. The cost of errors is too high. |
| Payments and finance | Financial damage can extend to third parties. |
| Legal documents between companies (invoices, purchase orders, etc.) | Legally binding. Errors affect relationships outside the organization. |
The common thread: errors have direct, irreversible impacts on people or society. Using AI-generated output in these fields without human review is, in my view, still too risky at this point.
Systems Where AI Alone Is Fine
On the other hand, these kinds of systems have no significant barrier to being built AI-only:
- Games
- Bill-splitting calculators
- Inventory trackers
The common thread: errors are limited in impact and easy to fix.
Summary
In professional contract work, the developer using AI is a human who holds the contract. Whether to use AI as a development tool is fundamentally up to the contractor's discretion — and the real question is whether humans can be accountable for the output.
AI is just a tool. No matter how capable the tool gets, the questions of what you build with it and who takes responsibility don't change. To put it bluntly: in a contract dispute, the worst case is court. AI cannot stand trial.
"Built entirely with AI" is something you can proudly say only when the impact of mistakes stays entirely within the maker's own sphere — that's my conclusion for now.
That said, even life-critical systems like autonomous vehicles are increasingly powered by AI. But they're not "AI alone" — they work because of strict legal frameworks, multiple layers of safety design, and a clear chain of human accountability. Which suggests: wherever that kind of structure can be built, AI adoption will follow.
Related Articles
Check out the other articles in this series!
- Why I Built a Framework for SI Projects
- What I Learned Developing a Custom Framework with Generative AI
Thank you for reading!
I'd appreciate it if you could give it a ❤️!
Top comments (1)
Solid.