Resources
Not everything is an LLM
People reach for a language model by reflex, but LLMs are one small family of AI. Here is what the specialist models do, when to use each, and how to tell which you actually need.
Reach for a chatbot by reflex and you will often pick the wrong tool. Language models are one small family of AI, six of the one hundred and forty-five approaches in our field guide. Most real problems, from forecasting demand to catching fraud to reading an invoice, are handled better, cheaper, and faster by a specialist model built for that one job. Here is how to tell which you actually need.
The reflex that quietly wastes money
When every AI story is about chatbots, every problem starts to look like a chatbot problem. So someone pastes a spreadsheet into a language model and asks it to forecast next quarter, or runs ten million support tickets through one at a time to sort them into twelve buckets. It works in the demo. Then the bill arrives, the numbers do not add up, and nobody can explain the answer.
A language model cannot do arithmetic reliably over a long series, has never seen what your customers did last year, and costs a fortune run a million times. The problem was never the model's intelligence. It was using a language tool for a job that is not about language.
Six language models. One family out of fourteen. The other 139 approaches do most of the work.
Specialists do the work. The language model takes the order.
The pattern that actually wins on cost, speed, and accuracy is quieter. A forecaster predicts demand. A vision model reads the invoice. A recommender learns what customers buy next. An anomaly detector flags the fraud. A solver builds the schedule that never breaks a rule. Each one is small, fast, and built for a single job.
The language model sits out front as the interface. It understands the request in plain English, hands each part to the right specialist, and writes the result back up in plain English.
It takes the order. It does not cook the meal.
How to pick, in two questions
You do not need to memorize one hundred and forty-five approaches. You need two answers: what are you starting with, and what do you need back. A spreadsheet and a predicted number point to one family. Images and a pass-or-fail verdict point to another.
We built a short interactive tool that walks those two questions, names the kind of model that fits in both plain terms and technical detail, and flags the trap that catches most people. It also maps the whole field, so you can see for yourself how little of it is a chatbot.
Why this matters if it is just you
This is not only an enterprise problem. The individual version costs less money and more time: months spent trying to make one chatbot do something it was never built for, concluding that AI does not work for your kind of work, and being wrong about that.
The skill worth having is not prompting. It is recognizing the shape of your problem well enough to know what kind of thing could solve it. That is learnable in an afternoon, on your own work.