Evaluation dataset
Together with your domain experts we assemble examples with a known correct outcome. This dataset is the benchmark for every model variant, and it remains your property.
We adapt language models to your tasks, through fine-tuning, small dedicated models, or prompting and structured outputs. Measurement decides which route fits.
45 minutes, no strings attached. You leave with a written shortlist.
Many fine-tuning requests can be solved without fine-tuning. Good prompting, retrieval over your documents, and strictly defined output formats often bring an existing model up to the required level. That is faster, cheaper, and easier to maintain.
Fine-tuning earns its place in clear cases: when a smaller model needs to handle a narrow task as well as a large one, when a fixed format or domain vocabulary has to be reliable, or when high volumes make cost per transaction the deciding factor.
Every decision rests on an evaluation set built from your real cases. We use it to compare the options and see whether an adapted model genuinely beats the simpler route.
Together with your domain experts we assemble examples with a known correct outcome. This dataset is the benchmark for every model variant, and it remains your property.
Prompting, in-context examples, retrieval, and structured outputs against a fixed schema. This turns a general-purpose model into a tool for your task, with no training involved.
Where the numbers justify it, we fine-tune an open-source model on your data, usually with efficient methods such as LoRA. The result runs on your own or EU infrastructure.
Classification and extraction often need only a small model that is fast and cheap to run. Typical tasks are routing enquiries, recognising document types, or reading fixed fields.
You receive a side-by-side comparison of the variants by quality, latency, and cost per transaction. It ends in a reasoned recommendation, which may well be not to fine-tune.
In 45 minutes we clarify what the model needs to do and whether adapting it is even a candidate. No obligation and no cost.
We build the evaluation set and measure how well existing models perform without training. Any adaptation has to beat this baseline.
Prompting, fine-tuning, or a small dedicated model: the chosen approach is delivered as a package with a fixed price and acceptance criteria measured on the dataset.
When your data changes or better base models appear, we test again. We only retrain when the measurements show an improvement.
The industry overview lists concrete use cases. Detailed pages are available in German.
When a narrow task comes up very often, when a fixed format or domain vocabulary must be reliable, or when a smaller model should replace a large one for cost or data protection reasons. For questions about your own documents, retrieval is usually the better route.
They solve different problems. RAG gives the model access to current knowledge from your documents, with sources. Fine-tuning changes the model behaviour, style, or output format. For knowledge questions RAG is almost always the first choice, with fine-tuning added if needed.
Depending on the task, a few hundred to a few thousand good examples are often enough to fine-tune an existing model. Quality matters more than volume. How much your case needs becomes clear from measurements on the evaluation set.
Yes, in the sense of an adapted open-source model or a small specialised model for classification or extraction. Training a large language model from scratch is not something we recommend to mid-sized companies.
Yes. The trained weights, the training data, and the evaluation set belong to you. The base model licence still applies; we check and document it during selection.
It depends on whether prompting is enough or training is needed, and on the effort required for example data. With methods such as LoRA, compute for training is usually the smaller part. After the baseline measurement we quote a fixed price per package.
45 minutes, no strings attached. You leave with a written shortlist.