01Also called Large Language Model, foundation model, base model
The engine under almost every AI feature you’ll be asked to sign off.
A large language model learns the patterns of language from an enormous body of text, then writes by predicting what should come next, one small piece at a time. Do that well enough and it can draft, summarise, translate and reason in plain English. Claude, GPT and Gemini are all examples, each built by a different company.
In Everyday Terms
Think of the most widely read colleague you’ve ever worked with, someone who has absorbed an enormous library and can talk fluently about almost anything in it. They’ve never lived any of it. Everything they know came from text, not experience.
The Trap I See Most
Vendor concentration is a board risk before it is a technical one. The moment your roadmap assumes one provider’s model, pricing power sits on their side of the table, so demand a switching test in the architecture from day one.
Ask This in Your Next Meeting
“Which model is this feature actually running on, and what happens to our product if that vendor changes pricing or availability overnight?”
02Also called token count, context length unit
The meter that’s always running.
Models don’t read words the way we do. They break text into small pieces called tokens, and in English a token averages roughly three-quarters of a word. Tokens set the price of every request and the limit on how much a model can take in at once.
In Everyday Terms
If a word processor charged by the character, you’d start writing differently. Tokens quietly shape how much a feature costs to run and how long a conversation can stay coherent before something gets dropped.
The Trap I See Most
Finance discovers tokens about three months after launch. Long system prompts and chat history mean you pay for the same words thousands of times a day, so the flabbiest prompt in the building quietly becomes a line item.
Ask This in Your Next Meeting
“What does this feature cost per interaction once real usage kicks in: not the demo number but the production one?”
03Also called context length, max tokens
Everything the model can see right now, and nothing more.
The model’s working memory for a single conversation. Your instructions, the chat so far, any documents and the reply itself all have to fit inside it. When it fills, something has to give, and the earliest material is usually the first to go.
In Everyday Terms
Picture a desk, not a filing cabinet. Everything the model is working with has to fit on the desk at once; anything that doesn’t fit gets swept onto the floor and forgotten.
The Trap I See Most
Bigger windows license lazy product design. Teams stuff everything in because they can. Quality sags in the middle of the pile and cost doubles, when curation would have beaten capacity.
Ask This in Your Next Meeting
“Does this use case need the model to hold a whole document, or a whole conversation, in mind, and does the model we’ve picked actually do that?”
04Also called prompting, instructions
Better briefs, better answers. It really is that simple, and that hard.
A prompt is the brief you give the model. Prompt engineering is the craft of writing that brief so the answer comes back accurate, in the right voice and within scope, every time rather than once. A sharper brief often beats a pricier model.
In Everyday Terms
The same brief handed to two different agencies produces two different campaigns. A vague brief gets vague work back, no matter how good the agency is. Prompting works the same way.
The Trap I See Most
Prompts are product decisions dressed as text files. An unversioned prompt tweak changes behaviour for every customer overnight, which means you shipped a release with no release process.
Ask This in Your Next Meeting
“Who owns this prompt, and where is it version-controlled, so we know exactly what changed when quality shifts?”
05Also called context design, context management
Curating what the model sees, not just what you say.
The discipline that has grown up beyond prompt writing: deciding everything the model sees at the moment it answers. That includes instructions, examples, retrieved documents, memory, tool results and conversation history, all chosen and ordered to fit the context window.
In Everyday Terms
A great executive assistant doesn’t just write a good cover note. They decide which three papers go in the folder, which stay out and the order of the rest. The meeting goes well because of the folder.
The Trap I See Most
More context isn’t better context. Stuffing the window with everything you have makes answers slower, dearer and often worse, because the important signal gets buried.
Ask This in Your Next Meeting
“What exactly does the model see when it answers this customer, and who decided?”
06Also called prediction, serving
The bit you pay for every time a customer clicks.
Training is school and inference is the job. Every time a live product sends a model a question and gets an answer back, that’s inference. Training is a large, occasional bill. Inference is a smaller bill that arrives with every single customer interaction, for as long as the feature lives.
In Everyday Terms
Training is years of medical school. Inference is every consultation afterwards. The learning happened once, but the diagnosis is worked out fresh, every single time someone walks in.
The Trap I See Most
The demo is the cheapest this feature will ever be. Growth multiplies inference cost in a straight line unless someone owns caching, batching and routing, and that someone defaults to no one.
Ask This in Your Next Meeting
“As adoption grows, is our inference cost growing in a straight line, or have we found ways to cache, batch or route to cheaper models?”
07Also called thinking models, extended thinking
Slower, pricier and far better at hard problems.
Models built to think before they answer, spending extra time working a problem through internally. They shine on maths, code, planning and knotty analysis. They’re slower and dearer per answer, so they earn their keep only where the question deserves it.
In Everyday Terms
It’s the difference between catching a colleague in the corridor and booking an hour of their time. For most questions the corridor answer is fine. For the knotty ones you want the hour.
The Trap I See Most
Teams switch reasoning on everywhere because the demo looked brilliant, then wonder why the wait and the bill both tripled. Decide which journeys genuinely need deep thinking.
Ask This in Your Next Meeting
“Which of our use cases genuinely need a reasoning model, and what does that choice add to cost and wait time?”