SumatoSoft

How small companies fine-tune without proprietary training data 🧠

A common assumption that's no longer correct: you need a large proprietary dataset to fine-tune a model usefully.

For most enterprise fine-tuning use cases in 2026, including domain-specific tone, structured output adherence, workflow-specific reasoning, and brand voice consistency, synthetic data has become a first-class option. The pattern works like this: you describe what you want the model to do in detail, you use a strong frontier model to generate hundreds or thousands of input-output pairs that match the description, you filter the synthetic pairs for quality, and you fine-tune a smaller model on the result. 🔄

The fine-tuned smaller model often performs the target task as well as the frontier model, at a fraction of the inference cost. This is the technique behind several recent open-weight model releases that punch above their parameter count.💰

Where synthetic data does and doesn't work: it works for behavioural fine-tuning (tone, format, structured output, domain-vocabulary adoption). It works less well for fine-tuning on specialised factual knowledge, where you want the model to know things it didn't know before. For factual grounding, RAG or graph RAG remains the better tool. The two approaches combine well: fine-tune for behaviour, retrieve for facts.🧩

For companies that have been told "we can't do AI because we don't have enough data," this changes the conversation. The data constraint that blocked fine-tuning in 2023 has loosened. What you need now is a clear specification of what the model should do, a frontier-model budget for synthetic generation, an eval suite to verify the result, and a serving infrastructure for the fine-tuned model. The fine-tuned model that comes out can often run on your own infrastructure for a few hundred dollars a month.✅

"Prompt engineering" is a 2023 word 📅

The phrase has quietly stopped showing up in serious AI engineering practice. What replaced it: context engineering. 🔄

Prompt engineering was about phrasing the instruction well: writing a single prompt that produces a good output for a single use. Context engineering is about assembling everything the model needs to do its job. The system prompt, retrieved documents, tool definitions, conversation history, user metadata, structured examples, and policy constraints, all selected and ordered for the specific request. 🧠

For a single-shot question, the difference is invisible. For an agent handling a complex workflow, it determines whether the system works at all. The agent that has access to all the right context produces good outputs reliably. The same agent with everything except the right ordering produces unpredictable outputs that look like model failures but are context-assembly failures. ⚙️

What this means for projects: the engineering work is upstream of the prompt. Building the retrieval pipeline that finds relevant content. Building the metadata layer that injects user-specific context. Building the templating system that orders information for the model's attention pattern. Building the cache layer that makes context-heavy requests affordable. Most of the work that determines whether an AI feature ships well lives in assembly, not phrasing. 🏗️

When a vendor pitches "we'll write your prompts," they're selling 2023. When they pitch context architecture, schema design for agent inputs, and retrieval evaluation, they're selling what 2026 ships. 📦

If your AI deployment doesn't run evals on every commit, it isn't in production ⚙️

A pattern across AI integration projects that ship versus ones that don't: the shipping ones treat evaluations as production infrastructure, not as a testing phase. 🚢

The distinction is straightforward. In a normal software stack, you write unit tests, integration tests, and end-to-end tests. They run on every commit. If they fail, the deploy is blocked. AI features need an equivalent layer, and the equivalent is the eval suite. A test answers "did the function return the expected output?" An eval answers "did the model produce a response of acceptable quality on a representative input?" 🤖

What an eval suite for a production AI feature looks like: a fixed set of inputs that span the workflow's distribution, ground-truth answers or scoring rubrics, automated grading (often by another LLM or a deterministic check), latency and cost gates, and regression detection across versions. Anthropic, OpenAI, and Google all publish their internal eval setups now. The pattern has converged. 📊

Why this matters for the buyer: when a vendor says they tested the AI feature, the question to ask is "do you run evals on every deploy?" Vendors that say yes are operating in 2026. The ones that conflate testing with evals are operating in 2023, and you'll find out in production. 🛒

Most failed AI integration projects didn't fail because the model was wrong. They failed because nobody had a running eval suite that would have caught the regression when the prompt changed, the model version updated, or the retrieval source drifted. Build the eval suite first. The model work is downstream of it. 🔧