Five techniques, one spectrum
Before you fine-tune anything, place the problem on the spectrum. Each technique trades effort for control, and most projects pick the wrong rung — usually one too high.
| Technique | Cost | Effort | When it shines |
|---|---|---|---|
| Prompt engineering | Free | Minutes | ~90% of practical use cases. Always start here. |
| Few-shot in context | Free | Minutes | Consistent output format, structured replies. |
| RAG | Low | Days | Model needs your data or documents that change. |
| Fine-tuning | Medium | Days–weeks | You need a behavior — style, format, refusal — to be reliable. |
| Pre-training from scratch | Very high | Months | You are building a foundation model. Almost no team should be here. |
RAG vs fine-tuning, one sentence each
RAG changes what the model knows at query time by injecting fresh context. Fine-tuning changes how the model behaves by adjusting its weights. They are not substitutes — most production systems use both.
The honest decision rule
Before reaching for fine-tuning, force yourself to answer: "What did the strongest prompt I could write get me, and where exactly did it fall short?" If you cannot describe the gap precisely, you are not ready to train. Fine-tuning will not rescue an undefined goal.