Why fine-tune at all
Frontier models are remarkable generalists, but generalists are expensive, sometimes slow, and occasionally inconsistent at exactly the narrow thing you need. A fine-tuned 7–14B parameter open model can match or beat a much larger model on a specific task — classifying support tickets into your categories, extracting fields from your document types, writing in your house style — at a fraction of the cost per call, and it can run on hardware you control.
Fine-tuning is not the answer to everything, though. It is a poor way to teach a model facts that change, and it adds an asset you have to maintain. That’s why our first step is always a baseline: we measure how far careful prompting and retrieval get you. If they get you most of the way, we’ll tell you, and save you the training bill.
Data is the project
Training runs are the quick part. The real work is the dataset. We help you assemble examples from historical records, expert annotations and — carefully — synthetic generation, then clean, deduplicate and balance them. We write labelling guidelines so examples are consistent, because a model learns your inconsistencies as faithfully as your rules. A held-out test set, never seen in training, is the honest judge at the end.
Training and evaluation
We use parameter-efficient methods — LoRA and QLoRA — via tools such as Hugging Face PEFT, TRL, Unsloth and Axolotl. They let us try several base models and settings quickly on modest GPUs. Every run is tracked with its data version, configuration and scores.
Evaluation goes beyond a single accuracy number. We compare against the base model and a frontier API on your test set, check that general capabilities and safety behaviour haven’t regressed, and review samples by hand. You get a clear table: quality, latency and estimated cost per thousand requests for each option.
Deployment you control
Finished models are quantised where it helps and served with vLLM, TGI, llama.cpp or Ollama — on your cloud, on-premises or on a dedicated GPU server. You receive the weights, configs and a retraining recipe, so the model can improve as your data grows.