Don't Use a Cannon on a Mosquito: The Five Levels of AI in a Business, and Which One You Actually Need
The easiest trap for a company adopting AI is using a cannon to swat a fly—jumping straight to training or fine-tuning a model when the actual business need could be met with something far simpler and cheaper. Andrew Ng once said that 75% of teams doing fine-tuning are working on problems that don't require fine-tuning at all, and might not even need complex prompts. Yet plenty of companies have walked right into that pit and burned real money.
Here's something that seems strange on the surface: more than half of all compute worldwide is now going to AI coding. Not everyone is a programmer, but coding is eating half the compute, and every major tech company is racing down that track. Think about what actually happens when we sit at a computer all day. The machine turns code into text and images we can read on screen; we edit those documents with a mouse and keyboard; and our edits get converted back into code that operates on the files. The step that actually produces the deliverable is the code step. Tools like Claude Code and Codex skip the part where we operate the computer—they take our intent, write it directly as code, and the work is done. Writing a proposal is writing code. Building a spreadsheet is writing code. Making a web page is writing code. AI coding isn't serving programmers—it's using code to produce nearly every kind of deliverable a knowledge worker can make.
The easiest trap for a company adopting AI is using a cannon to swat a fly—jumping straight to training or fine-tuning a model when the actual business need could be met with something far simpler and cheaper. Andrew Ng once said that 75% of teams doing fine-tuning are working on problems that don’t require fine-tuning at all, and might not even need complex prompts. Yet plenty of companies have walked right into that pit and burned real money.
Before we get into the levels, consider something that seems strange on the surface: more than half of all compute worldwide is now going to AI coding. Not everyone is a programmer, but coding is eating half the compute, and every major tech company is racing down that track. Why?
It clicked for me one day. Think about what actually happens when we sit at a computer all day. The machine turns code into text and images we can read on screen. We edit those documents with a mouse and keyboard. Our edits get converted back into code that operates on the files. The step that actually produces the deliverable is the code step. Tools like Claude Code and Codex skip the part where we operate the computer—they take our intent, write it directly as code, and the work is done. Writing a proposal is writing code. Building a spreadsheet is writing code. Making a web page is writing code. AI coding isn’t serving programmers—it’s using code to produce nearly every kind of deliverable a knowledge worker can make.
So how did things get to this point? We can walk through the whole arc from the beginning.
When GPT first appeared, AI was just a large language model—something that could take text in and put text out. What made it remarkable was that it had pre-learned the world’s knowledge and methods. Every time you asked a question, it could quickly sift through all of that, find the most relevant answer, and articulate it back to you in coherent language. At that stage its role was essentially a talking encyclopedia—already impressive, and a huge boost to the speed of processing, filtering, and synthesizing information. A lot of work can still be done with nothing more than a large language model. The later levels don’t make this one obsolete.
The second level was the chatbot. People started learning about prompting. A chatbot takes the base language model and uses prompts to give it a specific scenario and identity, usually with a private knowledge base plugged in. Define it as a customer-service agent and it talks like one. Feed it your product manual and sales scripts and it can answer questions like a seasoned employee. Back in 2023 I ran an experimental project at Tencent—an AI-driven ad-review assistant that let small and mid-size advertisers do their own compliance pre-checks on ad content. To this day, the chatbot format is probably still the most common way AI actually gets used inside companies.
The third level is the workflow. By this stage, model capabilities had taken a meaningful jump—reasoning got stronger, multimodal abilities started emerging. A workflow breaks a complex business process into many parallel or sequential nodes and runs them like an assembly line, with conditional checks along the way. The output is extremely stable, but also relatively rigid. Almost nobody builds complex workflows anymore, yet simple workflows are still used constantly in day-to-day operations because they can churn out stable, high-volume deliverables with extreme efficiency.
The fourth level is Skills. As models kept getting more capable, there was no longer a need to hard-code every step. Instead, you write your workflow SOPs as documents the model can read directly. One document equals one skill; load whichever skill the task requires and call it on demand. But even today, a lot of people treat Skills like gospel—convinced that once their agent is loaded with a hundred expert-written Skills it’s unstoppable. Think about what a Skill actually is, though. It’s a prompt that gets loaded flexibly based on the scenario. That’s it. Useful? Sure. Magic? No.
The fifth level is the Agent. Honestly, there’s no strict consensus definition. Different people picture different things when they say the word. Earlier this year “小龙虾”—the Chinese nickname for the open-source Agent project OpenClaw—was everywhere, and for a while the name became almost synonymous with Agent itself. An Agent is a subject that runs autonomously over long periods, holds long-term memory, and can even develop personality traits. It doesn’t follow a fixed instruction manual. It decides on its own which tools to invoke and which path to take toward a goal. Through extended interaction it learns the user’s values, behavior patterns, and decision-making preferences, gradually becoming a working extension of that person. Agents are extremely flexible—but that flexibility comes at the cost of massive compute consumption, lower efficiency, and a higher error rate.
AI has arrived at this point one step at a time, but that doesn’t mean every company’s operations need the most advanced or most complex technology available. When the quality of the deliverable is the same, cost-effectiveness and efficiency deserve serious weight. If you’re running a business, the high-frequency, labor-intensive, high-value work on your plate should be matched to the right level of AI capability—and by now, you should have a working sense of which level that is.
Source: EP0087 (2026-08-27, 5:09) · audio recorded by the host · on-screen presenter is an AI avatar · both text and timecodes come from gemini-2.5-pro ASR of that recording, with three passages re-checked by ear and one passage lost at a chunk boundary recovered on a re-run
[00:00] Enterprises using AI The most common pitfall is using a cannon to shoot a mosquito They jump straight to training or fine-tuning a model when in fact, the business application doesn’t need anything that complex or expensive to get the job done So today, I’m going to follow the path of AI’s development and break down how AI actually ends up serving a real business After this, you’ll have a better grasp of these concepts in enterprise AI and you’ll be able to judge more accurately for your own business what level of AI capability you should use Before we start I want to invite you to think about a question Right now, more than half of the world’s compute
[00:26] is being used for AI coding This is a very strange thing in itself Not everyone is a programmer So why is it that coding has eaten up half of all compute? All the big tech companies are fighting for this lane What’s the reason for this? One day it suddenly dawned on me Think about it, when we sit in front of a computer working all day what is actually happening? The computer turns code into something we can understand text and images displayed on the screen Then we use the mouse and keyboard to edit those documents And that editing process
[00:51] is turned back into code by the computer which then operates on the documents The thing that actually does the work The thing that makes the file exist is the code step So Claude Code and Codex, these AI coding tools, what do they do? They skip the whole business of operating a computer They write our intent straight into code and the job is done Writing a proposal is writing code Making a spreadsheet is writing code Building a web page is writing code AI coding is not actually serving programmers It is using the act of writing code
[01:16] to complete very nearly every deliverable a knowledge worker can produce So how did things get to this point? Let’s review the whole process from the very beginning Back when GPT first came out AI was just a thing that took text in and put text out a large language model What was so remarkable about it? It had pre-learned the knowledge and the methods of the whole world For every question we ask it can rapidly filter through all of that find the best-matching answer and organise the language to explain it back to you
[01:41] See what I mean? At this stage, what was its role? It was a talking encyclopedia That alone was stunning It hugely raised the efficiency of processing filtering and explaining information Plenty of work can still be done with nothing but a large language model Then we get to the second stage Then came the chatbot or the chatbot And what did everyone start learning? Prompts A chatbot is usually built on a large language model with prompts added to inject
[02:06] a scenario and an identity And usually it has a private knowledge base bolted on When you define it as customer service it will talk to people the way customer service does Feed in the company’s product manual and the sales scripts and it can answer questions like a veteran employee Back in ‘23 at Tencent I ran an experimental project an AI-driven ad-review customer service that let small and medium advertisers do their own pre-check of ad compliance To this day this is probably still the most common way AI
[02:31] lands in an enterprise And here I’ll add a quick aside A lot of companies think because they have high-quality proprietary data that they have to go fine-tune a model wanting to use that data for business judgement But there’s really no need to fine-tune a model for that Andrew Ng once said that 75% of the teams doing fine-tuning are doing something that doesn’t need fine-tuning Some of it doesn’t even need such complex prompts to get the job done But plenty of companies have genuinely fallen into this pit and spent a lot of money for nothing
[02:56] Let’s move on to the third stage: the workflow At this stage, there was actually a pretty big jump in model capability Many models gained stronger and stronger reasoning and began developing multimodal ability In the era when workflows were dominant we could break a complex business process into many parallel or serial nodes executing down a line like an assembly line with various conditional checks in between In this mode, the AI is following a standard process as it executes The interaction is very stable
[03:21] but by the same token, it’s also relatively rigid Almost nobody builds these complex workflows anymore Instead, it’s the simple workflows that are still frequently used in business because they can produce delivery at volume stably and extremely efficiently Then, moving on to the fourth stage the Skill emerged As large model capability improved further we no longer had to hard-wire the process You can write a workflow SOP as a document the large model can read directly One set of documents is one skill you load whatever skill you need and invoke it on demand
[03:47] But to this day a lot of people treat Skills as scripture thinking once their agent has a hundred Skills from the big names makes them invincible But if we think carefully about what a Skill essentially is The essence of a Skill is just a prompt, loaded flexibly according to the scenario Then, as things developed, the Agent emerged Actually, there’s no strict definition of the concept When different people say ‘Agent’ what they have in their heads might be different Early this year, wasn’t the ‘crayfish’ all the rage? At that time, the word ‘crayfish’
[04:12] had basically become a byword for ‘Agent’ It’s an entity that runs autonomously over a long period with long-term memory and even personality traits It doesn’t act according to a specific instruction manual Instead, based on the goal it decides for itself which tools to call and what method and path to use to finish the task Through long-term interaction it can learn the user’s own values behaviour patterns, and decision preferences and gradually becomes the user’s digital double handling all kinds of things for us
[04:37] It’s extremely flexible but it also brings enormous compute consumption lower efficiency, and a tendency to make mistakes You see, as AI has walked this path step by step the business we run inside our companies doesn’t necessarily have to use the so-called the most advanced technology or the most complex technology Given the same quality of delivery for an enterprise cost-effectiveness and efficiency are also things you have to weigh heavily So at this point as a manager of a business for the high-frequency, high in human-labour cost,
[05:02] and high in business value work what level of AI capability should carry it you should now have a first idea That’s all for today See you next time, bye bye