Fine-tuning takes an already-trained foundation model and continues training it on a smaller, focused dataset — customer support transcripts, legal documents in a specific format, a particular tone of voice — so the model’s behavior shifts toward that narrower task without starting from scratch. It’s a middle ground between using a general-purpose model as-is (prompting) and building an entirely new model from zero.

The nuance a beginner often misses is that fine-tuning is not always the right tool. It requires real data preparation, some machine learning expertise, and ongoing compute cost, and it doesn’t teach a model new factual knowledge as reliably as people assume — for grounding a model in current, specific facts, retrieval (RAG) usually works better and is far cheaper to update. Fine-tuning tends to be worth it for narrow, high-volume tasks where consistent style or format matters more than fresh factual lookup — for example, classifying support tickets in a company’s exact categories, or writing in a very specific brand voice repeatedly.

For a startup deciding between prompting, RAG, and fine-tuning, the practical order is usually: try clear prompting first (cheapest), add retrieval if the task needs current or private facts, and reach for fine-tuning only once a specific, repetitive task has proven itself worth the extra investment.

🇵🇭 Philippine Example

Philippine AI-recruitment and salary-benchmarking sources list fine-tuning as one of the named, in-demand skills (alongside LLM and RAG work) that local AI engineers are expected to know, reflecting real market demand for this skill in the Philippines even without a single named company's fine-tuning project to point to.

Related Terms