Training vs Inference (and Why It Matters for Cost)
What you'll learn
- Distinguish training (building the model) from inference (using it)
- Understand fine-tuning as a middle path
- Know which phase you actually pay for and how to control it
Two phases, two economies
Every model lives two lives. Training is the one-time construction: feeding enormous datasets through expensive hardware for weeks to set the model’s billions of parameters. It costs a fortune and happens rarely — the frontier labs do it, most people never do.
Inference is everything after: running the finished model to answer a prompt, generate an image, or transcribe audio. Each call is comparatively cheap, but you pay it every single time. For anyone building on AI, inference is the meter that actually runs.
Fine-tuning: the middle path
Between “use it as-is” and “train from scratch” sits fine-tuning — taking a pre-trained model and training it a bit more on your own narrower data to nudge its style or specialise it (say, on your support tickets). It’s far cheaper than training a base model, but it’s still a training process with data, cost, and maintenance. Crucially, it’s often unnecessary: good prompting plus retrieval (RAG) solves many problems people reach for fine-tuning to fix.
The habit that saves money
Because inference scales with usage, a successful feature’s bill grows month over month. That’s why the whole Best Practices track exists — routing easy work to cheaper models, caching, and trimming tokens all attack inference cost directly.
One more thing to internalise: standard inference does not retrain the model. Your conversation doesn’t teach it anything permanent, and (unless a provider says otherwise) shouldn’t leak into the next person’s answers — though you should still check each provider’s data-use policy and disable training-on-your-data for anything sensitive.
That completes the Foundations module. From here you can jump into Prompt Engineering to get dramatically better answers, or head to Using AI Tools to choose and verify a chatbot.
For each task, tell me whether it happens during TRAINING or INFERENCE: 1) Answering my question right now 2) Learning grammar from billions of web pages 3) Fine-tuning on a company's support tickets 4) Generating an image from my prompt Give a one-line reason for each.
1) Inference — it's using the already-trained model to respond. 2) Training — the model is learning general patterns from data. 3) Training (fine-tuning) — adjusting a base model on new, specific data. 4) Inference — running the trained model to produce an output.
Sample output — AI responses may vary.
Common mistakes
- Thinking the model 'learns' from your chats in real time. Standard inference doesn't update the model — your conversation doesn't retrain it.
- Assuming you must train or fine-tune a model to use AI. The vast majority of applications only ever do inference against an existing model.
- Ignoring that inference cost scales with usage — a popular feature's bill grows every month even though training was a one-off.
How to check the AI's answer
- Before a 'we need to train our own model' project, confirm a prompt + retrieval approach on an existing model can't do it — it usually can, far cheaper.
- Check a provider's data-use policy: does your inference data get used for training? Turn it off for anything sensitive.
Key terms
Test yourself
3 questions · answers reveal after you check.
1. Which phase are you using when ChatGPT answers your question?
Answering a prompt uses the already-trained model — that's inference.
2. Fine-tuning is best described as…
Fine-tuning takes a pre-trained model and further trains it on narrower data — a middle path between prompting and training from scratch.
3. For a typical AI feature in production, which cost grows with the number of users?
Training is a one-time (or occasional) cost; inference is paid per request, so it scales with usage.