Offer 08 · Artificial intelligence

An AI model adapted to your language, your vocabulary or your images, measured.

Sooatek trains open models on your data (fine-tuning, speech, vision), measures the gap on an unseen test set and delivers them where they need to run: your server, your cloud or your users’ phones. Our Malagasy speech recognition model, released openly, has a 12.7% word error rate (with a language model; 14.3% without), against 21.5% for our previous model, a Whisper medium fine-tuned on the same data.

Fixed price, on quote, GPU compute re-invoiced at actual cost

Server · cloud · device · before-and-after measurement

Illustration: a workshop as a scale model; a raw block of terracotta, next to a stack of files, is shaped in a vise, then shown finished, fitted to its stand.
FIG. 01 — A model fitted to your data · 3D illustration

§ 01 / When it helps

Fine-tuning is not always the right answer.

Before training anything, we check that it is the right tool for your problem.

Useful when

  • The task is precise and repetitive: recognize, classify, transcribe, extract.
  • General-purpose models get your language, your vocabulary or your images wrong.
  • The data must stay with you, or the model must run offline.

Not useful when

  • The problem comes from the data or the catalog: we fix the data first.
  • A good prompt or an assistant that searches your documents (RAG) is enough: it is simpler to maintain.
  • The task is standard transcription, already cheap through an API.

In that case, we tell you before any training.

§ 02 / The offer

A model, and what you need to understand it.

Everything is delivered to you: you can retrain it, have it audited or hand it over to another team.

What you receive

  1. The prepared dataset and its split, documented.
  2. The model weights and the training and inference code, in your repository.
  3. A measurement report: before and after, on an unseen set, error examples, known limitations.
  4. The model exported (server, CPU or phone) and connected to your application, with versions and rollback.

Not included

  • Outsourced bulk annotation.
  • Standard transcription, already cheap through APIs.
  • GPU compute: re-invoiced at actual cost, or run on your hardware.

§ 03 / Method

Five steps, the same measurement at the start and at the end.

On a client project, the original model is measured before any training: that baseline tells whether the work paid off.

  1. Step 1: Data

    Your real data, split into training, validation and test sets. A set of examples is kept aside for judging.

  2. Step 2: Base model

    An open model chosen for the task and for where it will run: server or device.

  3. Step 3: Training

    On a GPU, with the curves tracked. We keep the best validation checkpoint, not the last one.

  4. Step 4: Evaluation

    The same measurement before and after, on an unseen set. Errors and limitations are written down.

  5. Step 5: Delivery

    Export in a standard format, versions kept, rollback possible.

§ 04 / Example 1 — Image recognition

Client case · anonymized

Recognizing one specific object among thousands of near-twins.

Context

A mobile collecting app identifies an object from a photo taken with a phone: reflections, angle, blur, sometimes a photo of a screen. Thousands of references look alike. A pre-trained image model, used as is, did not tell them apart well enough.

Approach

We fully retrained a compact open image model (MobileCLIP2) so that it produces one embedding per reference, with a loss function that pushes neighboring references apart (ArcFace). Training starts from the official catalog images, transformed to imitate a real photo, and evaluation is done on real photos. A second model, trained on synthetic images, finds the four corners of the object to straighten it. Both models run on the server and directly on the phone.

Training

  1. Official catalog images
  2. Transformed to imitate a real photo
  3. Embedding model MobileCLIP2 · ArcFace
  4. Versioned embedding index never overwritten

Recognition

  1. Photo taken with the phone
  2. Second model: the four corners the object is straightened
  3. Embedding of the photo
  4. Closest reference in the index

Both models run on the server and on the phone.

FIG. 02 — Two trained models, from the catalog to the photo · Diagram

What we learned

  1. The default settings made training collapse: we measured it, then fixed it.

  2. When confusions persisted, measurement showed that they came from near-identical variants in the catalog and from an index that needed refreshing. We did not retrain the model.

  3. Each embedding index is versioned, never overwritten: rolling back takes only a version change.

Data The data stays with the client.

§ 05 / Example 2 — Malagasy speech recognition

Public model · Hugging Face

A Malagasy speech recognition model, released openly.

We continued training an open speech recognition model (w2v-BERT 2.0, already adapted to Malagasy) so that it stays reliable on the short utterances of a voice assistant, with a single 16 GB GPU. The model, its language model, a punctuation model and a CPU version are published.

Word errors on 11,625 short utterances (2 to 8 s) never seen in training

  • Our model, with a language model 12.7%
  • Our model, without a language model (plain decoding) 14.3%
  • Starting model (badrex), plain decoding 19.9%
  • Our previous model: Whisper medium fine-tuned on the same data, plain decoding 21.5%
FIG. 03 — Word error rate (WER) · Chart · At equal decoding, our model gains 5.5 points over its starting model. Differences significant at 95% (paired bootstrap, published on the card). Lower is better.

Model card

Starting model
badrex/w2v-bert-2.0-malagasy-asr
Data
badrex/malagasy-speech-full
Hardware
1 GPU with 16 GB, about 3.5 hours of training
Metric
WER (word error rate), normalized text
Result
12.7% on 11,625 unseen short utterances · 10.1% on long clips
License
CC-BY-4.0

Key points

  • Speed: 52 ms median per utterance on a GPU, against 259 ms for the Whisper medium.
  • The gain comes from the short segments added to training: on long clips alone, the same recipe improved nothing.
  • Rigor: we publicly corrected a wrong measurement of our previous model (non-normalized text).

Known limitations

  • Short utterances cut from read speech, not captured by a real voice assistant.
  • Less reliable under 3 seconds and in noise.
  • Mostly official Malagasy; coastal dialects not evaluated.
  • Output without punctuation or capitals: a separate model restores them.

Taken from the card published with the model.

§ 06 / Guarantees

Your model and your data belong to you.

The commitments of all our projects, plus two specific to this offer.

  • Your training data is only used for your model

    Never reused for another client.

  • Training on our dedicated GPU or on your infrastructure

    Your choice, written down before we start.

  • Code on your Git from day one

    You see every commit: the code lives in your repository.

  • Rights assigned on payment

    The code is yours once the invoice is paid.

  • Human review before every production release

    AI prepares, a human validates.

§ 07 / Questions

Frequently asked questions.

How much does a specialized model cost?

The fixed price is set in writing before we start; GPU compute is re-invoiced at actual cost, or run on your hardware.

Do you need a lot of data?

It depends on the task. The diagnostic tells you before any training; on a client project, we first measure the original model.

Can the model run without a connection?

Yes, when its size allows: one of our models runs directly on the phone, and our Malagasy model has a CPU version.

Who owns the trained model?

You do: weights and code are delivered to your repository, rights assigned on payment.

A task where general-purpose models get it wrong?

Describe it in a few lines: we tell you whether fine-tuning is the right answer, or whether a document assistant is enough.