“Fine-tuning” sounds technical, but the idea is simple: take a model that already knows a lot, and give it extra lessons so it gets good at your specific job.
What it actually does
A pretrained model like an open-weight LLM has broad general ability. Fine-tuning continues its training on a smaller set of examples you provide — pairs of input and the output you want — nudging the model toward your task, tone, or format. The result is a specialized version of the model.
What it is good (and bad) at
Fine-tuning shines when you need consistent behavior: always answering in a particular JSON structure, matching a brand voice, or handling a narrow classification task reliably. It is not the right tool for adding fresh factual knowledge — for that, retrieval (RAG) is cheaper and more accurate, because facts change and retraining is slow.
The cost question
Full fine-tuning of a large model is expensive. The breakthrough that made it practical for most teams is parameter-efficient fine-tuning, especially LoRA, which freezes the original model and trains only a tiny number of new parameters. That cuts compute and storage costs by orders of magnitude while keeping most of the benefit.
Who should care
Teams that have tried prompting and RAG and still need more consistency or a specialized skill. The sensible progression is: prompt first, add retrieval next, and fine-tune only when those hit a wall.