Why speaker count matters more than hours

Hours are the unit everyone quotes and the unit that predicts the least. Here is why the number of distinct speakers determines whether your model generalizes.

Ask ten vendors for a quote and nine will answer in hours. That is because hours are easy to count, easy to compare, and easy to inflate. It is also why so many buyers end up with datasets that look adequate on paper and underperform in training.

What a model actually learns from

When a speech model trains on a dataset, it is not learning "English" or "Arabic." It is learning the acoustic patterns present in the recordings you gave it — including the individual characteristics of the people who happened to be recorded.

If those recordings come from a small group of speakers, the model learns that group well and everything else poorly. This is speaker overfitting, and it is invisible in a cost-per-hour comparison.

A hundred hours from five speakers is, for generalization purposes, close to five hours of distinct information repeated twenty times.

What to ask for instead

Ask for the speaker manifest. Any serious producer keeps one, because they need it to manage the recording schedule.

  • How many distinct speakers, and what is the minimum per speaker?
  • What is the demographic spread — age range, gender balance, region or dialect background?
  • How were speakers recruited, and does that recruitment method bias the pool?
  • Is any speaker represented disproportionately in the total hours?

Why vendors resist this framing

Speaker count is expensive to increase in a way that hours are not. Recording the same five people for another twenty hours costs studio time. Recruiting, screening, and scheduling fifty new speakers costs coordination, and for uncommon languages it can cost weeks of lead time.

That is a real cost difference, and it is why a per-hour price is a poor comparison across vendors: the cheap quote and the expensive one may not be selling the same thing.

The exception

There is one case where hours genuinely dominate: single-speaker voice cloning and personalized TTS, where the goal is to model one specific voice as accurately as possible.

That is a narrow case. For almost every other application — recognition, diarization, wake words, emotion classification — the speaker count is the number that predicts whether the model works outside the lab.

More insights

  • Handling a data batch that failed acceptance

    A failed batch is a decision with three possible outcomes, and the expensive mistake is choosing the wrong one. How to measure the failure, and what to agree beforehand.

  • When to stop collecting data

    More data stops helping before it stops costing. The signals that the curve has flattened, and the stopping rule that makes the decision mechanical.

  • Avoiding scope creep in a data project

    In a corpus project every property is additive, so requests arrive continuously and each one looks small. The fix is a classification step before any pricing.

Submit a sourcing request

Tell us the language, the hours, and what the data needs to look like. You will get a real number and a real timeline — not a range. If we cannot source it well, we will tell you that instead.

  • Pilot batch before the full run, so problems surface early.
  • Consent documentation delivered with the data.
  • No medical or clinical data. No recorded telephone calls.

We reply within two business days. Your details are used only to answer this request. See our privacy policy.

Contact

Talk to a human

Send a specification and we will come back with a real number and timeline.

Submit a sourcing request

Or email hello@linguacorpus.com