# Should we fine-tune a model or just write better prompts?

> Test prompts, examples, retrieval and structured outputs first.

Canonical page: https://ionbin.com/wiki/questions/should-we-fine-tune-or-prompt/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

Question

## Should we fine-tune a model or just write better prompts?

Test prompts, examples, retrieval and structured outputs first. Consider fine-tuning for a measured, repeatable need after comparing quality and total operating cost. Confirm model and service availability: OpenAI is winding down self-serve tuning and Mistral marks its former feature deprecated.

Verified Oct 18, 2026 Review by Jan 16, 2027 5 sources

### What it is

This is a build decision for teams automating a repeatable task, such as classifying tickets or drafting product copy in a fixed format. [Fine-tuning](https://ionbin.com/wiki/concepts/fine-tuning/) trains a model further on your examples. Prompting changes only the instructions and examples you send.

### How it works

- Write a clear prompt with a few examples, and measure it with an [eval](https://ionbin.com/wiki/concepts/evals/). OpenAI describes optimization as a loop of evals, prompt engineering and fine-tuning.

- If the model lacks current or private facts, test retrieval ([RAG](https://ionbin.com/wiki/concepts/rag/)) rather than tuning.

- If format is still inconsistent at volume, try [structured outputs](https://ionbin.com/wiki/concepts/structured-outputs/).

- Only then test fine-tuning on a held-out set, and compare cost and quality against the prompted version.

**Vendor availability (checked 2026-10-18).** OpenAI’s [deprecations page](https://developers.openai.com/api/docs/deprecations) says self-serve fine-tuning is winding down: organizations with no prior fine-tuning lost access on May 7, 2026, and active customers can’t create new jobs from January 6, 2027. Mistral’s docs say its fine-tuning feature is deprecated, without a date. An open-weight model may offer another route where its license, tooling and your infrastructure permit training. That is a separate engineering and evaluation commitment.

The OpenAI Evals platform becomes read-only on October 31, 2026 and is scheduled to shut down November 30, 2026. Keep your evaluation data and criteria portable. Its October 14 deprecation notice also schedules listed GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini snapshots, including their fine-tuned versions, for shutdown on January 14, 2027.

### Benefits

- Avoids spending on training you don’t need.

- Lets you revise prompts or source material without another training job; changes still need regression checks.

- Gives a clear, evidence-based reason when you do tune.

### Limits and risks

- **Ties you to a model version.** Retirement requires a migration plan and re-evaluation; it may mean retraining or moving back to prompting.

- **Data must be clean and permitted.** Training examples need the right to be used this way.

- **The service can go away.** Vendors change which models can be tuned, and some are ending self-serve tuning.

### Checked specs

Snapshot from official sources on Oct 18, 2026.

| OpenAI's optimization loop | Evals, prompt engineering and fine-tuning used together [1](https://ionbin.com/wiki/questions/should-we-fine-tune-or-prompt/#src-1) |
| --- | --- |
| OpenAI self-serve fine-tuning (checked 2026-10-18) | Notice May 7, 2026; organizations that never fine-tuned lost access that day; job creation ended July 2, 2026 for organizations with no fine-tuned inference in 60 days; active customers can't create new jobs from January 6, 2027 [2](https://ionbin.com/wiki/questions/should-we-fine-tune-or-prompt/#src-2) |
| OpenAI fine-tuned models | Inference follows base-model lifecycle; listed GPT-4o/mini and GPT-4.1/mini snapshots and their tuned versions shut down January 14, 2027. [2](https://ionbin.com/wiki/questions/should-we-fine-tune-or-prompt/#src-2) |
| Mistral fine-tuning (checked 2026-10-18) | Docs say the feature is deprecated and no longer actively supported; no date given [3](https://ionbin.com/wiki/questions/should-we-fine-tune-or-prompt/#src-3) |

### Best-fit stacks

Stack 08

#### [Dev, web & IT](https://ionbin.com/use-cases/dev-it/)

Design, code, host and ship sites and internal tools, with an AI coding agent doing most of the typing.

Stack 10

#### [AI evaluation & quality control](https://ionbin.com/use-cases/ai-evaluation/)

Check an AI task against reviewed examples before changing the prompt, model or workflow.

### Agent compatibility

Not tool-specific. See [Agent-ready](https://ionbin.com/agent-ready/) for connector support by tool.

Levels come from each tool's recorded, sourced compatibility. [How the levels work](https://ionbin.com/wiki/questions/connect-a-tool-to-an-ai-agent/).

### Related entries

[Fine-tuning · Concept](https://ionbin.com/wiki/concepts/fine-tuning/)[Retrieval-augmented generation (RAG) · Concept](https://ionbin.com/wiki/concepts/rag/)[Evals (AI evaluations) · Concept](https://ionbin.com/wiki/concepts/evals/)[How do I write a prompt that gets usable work? · Question](https://ionbin.com/wiki/questions/how-to-write-a-prompt-that-works/)[Golden set: reviewed evaluation examples · Concept](https://ionbin.com/wiki/concepts/golden-set/)

### Sources

- [Model optimization](https://developers.openai.com/api/docs/guides/model-optimization) · OpenAIofficial accessed Oct 18, 2026

- [Deprecations](https://developers.openai.com/api/docs/deprecations) · OpenAIofficial accessed Oct 18, 2026

- [Fine-tuning](https://docs.mistral.ai/resources/deprecated/finetuning) · Mistral AIofficial accessed Oct 18, 2026

- [What is fine-tuning?](https://www.ibm.com/think/topics/fine-tuning) · IBMreference accessed Oct 18, 2026

- [Working with evals](https://developers.openai.com/api/docs/guides/evals) · OpenAIofficial accessed Oct 18, 2026

Practitioner views are restated in our words and labeled as views, not measured results. Product facts come from official sources dated above.

### Suggest an edit

IonBin's wiki isn't user-edited. Corrections go to our Directory Curator, who checks them against primary sources before anything changes. Spot something wrong or out of date on “Should we fine-tune a model or just write better prompts?”? Email us with a link to a primary source.

[Suggest an edit by email](mailto:contact@ionbin.com?subject=Suggest%20an%20edit%3A%20Should%20we%20fine-tune%20a%20model%20or%20just%20write%20better%20prompts%3F%20%5Bshould-we-fine-tune-or-prompt%5D&body=Page%3A%20https%3A%2F%2Fionbin.com%2Fwiki%2Fquestions%2Fshould-we-fine-tune-or-prompt%2F%0AEntry%3A%20questions%2Fshould-we-fine-tune-or-prompt%0A%0AWhat%20should%20change%3A%0A%0A%0APrimary%20source%20(link)%3A%0A) or write to [contact@ionbin.com](mailto:contact@ionbin.com)

Entry facts

**Type**: [Questions & how-tos](https://ionbin.com/wiki/questions/)

**Status**: Reviewed

**Verified**: Oct 18, 2026

**Review by**: Jan 16, 2027 (every 90 days)

**Sources**: [4 official · 1 other](https://ionbin.com/wiki/questions/should-we-fine-tune-or-prompt/#sources)

The wiki carries no sponsored placements or affiliate links. [Editorial policy](https://ionbin.com/editorial-policy/).
