RAG vs fine-tune audit
Week-1 workshop. We benchmark retrieval against the use case before committing a training budget. Often the answer is: skip fine-tuning entirely.
LoRA, DPO, or full fine-tune — chosen by data volume and use case, not vendor pitch. Feedback capture pipeline → labeled dataset → eval gate → adapter shipped. We pay back the training cost in weeks, not quarters.
Most teams reach for fine-tuning when better retrieval would solve the problem cheaper, faster, and reversibly. Our default is RAG. Fine-tuning is for the cases where the base model genuinely lacks the format, the domain vocabulary, or the latency profile you need.
Week-1 workshop. We benchmark retrieval against the use case before committing a training budget. Often the answer is: skip fine-tuning entirely.
Thumbs-up/down, edit-deltas, conversion signals — captured at the proxy and routed to a labeled dataset. The training set grows as you ship.
LoRA adapters as the default. Hot-swappable per customer or per tenant. The base model stays current; the adapter carries the customisation.
An adapter only replaces the production version after passing the golden eval suite. Same gate as every other prompt change.