Vendor reportedLive since Nov 2024Added Oct 2026

Convirza

Convirza serves 60 call-scoring models from one Llama 3 base and cuts cost 10x versus OpenAI

Convirza, a call analytics platform, moved from Longformer models to adapters fine-tuned on Meta's open-weight Llama-3-8b. Predibase, which hosts the setup, reports a 10x cost reduction and an 8% higher F1 score than OpenAI, and sub-second mean inference time.

Key figures

Copied exactly from the sources. Copy any figure with its citation.

10

x reduction

Operating cost compared with OpenAI1

8%

higher

Average F1 score compared with OpenAI, across the first 20+ indicators1

80%

higher

Throughput compared with OpenAI1

4

x higher

Throughput compared with the previous Longformer models1

What it took

CostNot disclosed
TeamNot disclosed
TimelineAdapters for 20+ indicators trained and deployed in the first month1

The problem

Convirza helps enterprises analyse customer calls and score how well agents perform. It processes millions of calls a month and extracts information into scorecards. Its older system used Longformer models (a type of text-analysis model) trained on over 60 indicators. Training took 9 to 24+ hours per iteration. Each model also needed its own compute, which cost $500 to $1,500 per indicator per month and limited the ability to add custom indicators for customers.

What they built

Convirza trained a separate small add-on (a LoRA adapter) for each of its 60 indicators and serves them all from one Meta Llama-3-8b base model. Llama-3-8b is an open-weight model, meaning its files are published and can be adapted by a company. Fine-tuning means further training on a company's own labelled examples. The adapters run on Predibase's managed platform, built on LoRAX, an open-source tool that serves many adapters off a single base model.

How they did it

Convirza chose a managed platform rather than building multi-adapter serving itself, because the load is highly variable and the engineering work would have been large. In the first month it trained and deployed adapters for 20+ indicators. The platform scales GPUs automatically, so Convirza can scale up to double-digit A100 chips at peak and back down when calls slow.

Results

According to Predibase, Convirza saw a 10x cost reduction versus OpenAI, an 8% higher average F1 score than OpenAI (F1 balances missed cases against false alarms) and 80% higher throughput than OpenAI. Compared with its earlier Longformer models, throughput is 4x higher. Mean inference time is sub-second, and Convirza's VP of AI says average response time stays under two seconds across 60 adapters.

What to copy

If your AI feature needs many tailored variants, test an adapter-per-task design on one shared base model before paying for per-feature compute.

All reported figures

MeasureFigureCitation
Operating cost compared with OpenAI10x reduction1
Average F1 score compared with OpenAI, across the first 20+ indicators8% higher1
Throughput compared with OpenAI80% higher1
Throughput compared with the previous Longformer models4x higher1
Mean inference timeSub-second1
Previous cost to serve one Longformer indicator$500 to $1,500 per month1
Previous training time per iteration9 to 24+ hours1

Lessons for your project

  1. Count the cost of one model per feature. Convirza's older setup needed dedicated compute for each of 60 indicators, which drove inference costs to hundreds of thousands of dollars a year.

  2. Share one base model across many tuned variants. Small add-on adapters on one Llama model let Convirza add indicators without a dedicated server for each.

  3. Buy the serving layer if you lack the team to run it. Convirza chose a managed platform over building its own multi-adapter infrastructure.

  4. Plan for load spikes. Convirza's peak call-processing hours need scaling to double-digit A100 GPUs.

Caveats

  • The source is a vendor case study by Predibase with quotes from Convirza's VP of AI. No independent source confirms the figures.
  • The post reports sub-second mean inference time, while a Convirza quote in the same post says average response time is under two seconds.
  • The post does not say which OpenAI model it compares against, or the test dataset.
  • The post does not give the go-live date. The deployed date shown is the post date.
  • The post does not state where Convirza operates. The region shown is an assumption, not from the source.

Sources

  1. Improving Agent Feedback with Multi-LoRA at Convirza

    Predibase · 2024-11-25 · Vendor case study · predibase.com

Summarized in our own words from the sources above. Spotted an error? See corrections.