Fine-tuning · Agents · Speech · Applied ML

You don’t need a modelthat knows everything.You need one thatknows your business.

We’re a small engineering team. We fine-tune open models on your data, build the agents and voice systems that use them, and keep them running after launch.

Model fine-tuning

What we build

Four things we build,and run afterwards.

Most of our work is one of these four. Each drawing is the actual system, not a metaphor for it.

Why own the model

The case for owningyour model.

If a task runs thousands of times a day, renting a general model is the expensive way to do it. Three things change when the model is yours.

  1. 01

    It costs less per task

    A small model tuned for one job needs shorter prompts and cheaper hardware. We count training, inference and operations at your real volume before we recommend it.

  2. 02

    It’s better at your work

    Your experts have already made thousands of these decisions. Training on them teaches the model your categories, your tone and your edge cases, and we test it on new work before it ships.

  3. 03

    Nobody else can copy it

    The examples, evaluations and corrections you collect are yours. Every month of use makes the model better and the gap wider.

In practice: routing support tickets
  1. Ticket arrives
  2. Your model classifies and drafts
  3. An agent reviews and sends
  4. The outcome trains the next version
Dhwani · live call
  1. CallerHi, I need to move my appointment to Thursday.
  2. DhwaniThursday at 10:30 is open. Shall I book that for you?
  3. CallerYes, please.
  4. DhwaniDone. You will get a confirmation by SMS in a moment.

An example exchange. The latency figures are from our own logged test calls.

1,761 msp90 time to first token
Proof

A voice agent that answers in 770 ms.

Dhwani is our own phone agent, running in production. After trying several model combinations on real logged calls, we brought the time to first token down from 1,761 ms to 770 ms at the 90th percentile.

Before
1,761 ms
After
770 ms
Faster
56%
How we work

How an engagementactually runs.

We don’t sell platforms. We pick one workflow, prove it works, and expand from there. Each stage ends with something you can look at.

  1. 01

    Assess

    Pick the right problem.

    We map the workflow, measure how it performs today, and agree what better means before we build anything.

    What you receiveA clear scope and evaluation plan
  2. 02

    Build

    Prove it on your data.

    We prepare the data, train or connect the models, and test against real tasks from your business, not a demo set.

    What you receiveA working system and the evidence
  3. 03

    Deploy

    Put it in your environment.

    It goes into your systems with permissions, monitoring and a way to roll back.

    What you receiveAn operational release and runbook
  4. 04

    Improve

    Keep making it better.

    We review what went wrong, watch quality and cost, and ship changes only after they pass the tests.

    What you receiveA measured improvement cycle
Our products

We also shipour own products.

All products
Get in touch

Tell us aboutthe work.

A workflow that takes too long, a model that keeps missing, a product that needs its next version. Write to us and we reply within a working day.

Discuss your use case hello@nftatoms.com