Benchmark testing
Your model's outputs measured against the accuracy targets you define, on a test set that looks like your real users.
For go or no-go decisions before launch
Data and model evaluation is benchmark testing against accuracy targets you set, plus bias and fairness checks across groups and languages, and monitoring after your model ships. We check the outputs and the data behind them. Your team trains the model, and we tell you how well it's doing.
group vs your target
overall looks fine. one group doesn't.
Data and model evaluation checks how well a trained model performs, and whether the data behind it can be trusted. The model's outputs are compared with checked answers, against targets you set, and the results are broken down by the groups your users belong to.
It's separate from training. Your team builds and trains the model, and evaluation measures it from the outside, before launch and on a schedule afterward.
Good evaluation depends on the test set as much as the model. It should look like your real users and stay separate from the training data. If it doesn't, the scores flatter you.
An evaluation is only as good as the labels behind it, so it helps to read how annotation quality is judged before you set a target.
Your model's outputs get measured against the accuracy targets you define and compared across demographic and linguistic groups. After launch we keep checking on a schedule. And we can look at the training or test data itself, before it gets anywhere near a model.
Your model's outputs measured against the accuracy targets you define, on a test set that looks like your real users.
For go or no-go decisions before launch
Results compared across demographic groups to find the people your model serves worst, before they find out for themselves.
For fair treatment across the people who use it
Language is one of the groups we compare, including speech that mixes two languages, which is where models often slip.
For multilingual assistants and speech recognition
Models drift as users pick up new slang and new products launch. A fresh sample of outputs gets checked against human judgment on a schedule we agree.
For catching a drop before your customers do
The data itself, checked before it gets near a model: whether the test set looks like your users, and whether it's truly separate from training.
For scores you can believe
Where there's no single right answer, like a chatbot reply, people who know the language and the domain rate each output against rules agreed with you.
For chatbots, assistants and generated text
Common reasons teams check a model, and the part of this page behind each one. They're examples of the work, not a client list.
A clear answer on whether the model meets the targets you set, on data that looks like your users.
Results split by age, gender, region or other groups, so a gap hiding in the average comes out.
The same bot checked for each language and accent your callers have, mixed speech included.
Regular checks on fresh outputs, so a slow slide in quality gets noticed before customers complain.
A check that test items never appeared in training, and that the test set looks like real use.
Two versions of your model run on the same test set, so the better one wins on evidence.
An overall accuracy figure is an average. A speech model can score well overall and still fail badly for one accent, one age group or one language, because the groups it handles well outweigh the ones it doesn't.
So we compare results across groups and languages, and we care about the test set as much as the model. Language is one of the groups we compare, and we work in languages from all over the world, with deep coverage of Indian ones (see Indian language data).
Evaluation is only as useful as the questions it answers. These four get settled with you at the start.
The accuracy targets the model has to meet, in numbers where possible, and what counts as a correct answer.
The demographic and linguistic groups your users belong to, so the results get broken down the way your risks are.
Test data that looks like your real users and stays apart from the training data. Otherwise the scores flatter you.
Models drift after launch. We agree the schedule with you and report back on it each time.
Your named contact stays with it from the first target to the last re-check. Here's the usual order.
You tell us what good looks like, in numbers where possible.
The NDA is signed before any of your data moves.
We agree the test data, the correct answers and the groups that matter.
We evaluate a small sample free, so you can see the kind of findings you get.
Outputs and data get tested against your targets, across groups and languages.
You get findings your team can act on, and a plan for checking again.
The words that come up when you plan an evaluation, and what each one means.
One team can collect the test data, label it and check your model against it. You can also compare all eight services.
New test data gathered from the people your model will serve.
Checked labels to use as the correct answers.
Reviewed transcripts to score speech models against.
Real conversations to test a voice bot or assistant with.
Generated data for gaps, always tested on real data too.
Short answers about this service. The services FAQ covers the other services and how they fit together.
Checking how well a trained model performs, and whether the data behind it can be trusted. The model's outputs are compared with checked answers, against targets you set, and the results are broken down by the groups your users belong to.
No. We provide data and evaluation. You train your own model, and we check its outputs.
It's an average. A model can score well overall and still fail badly for one accent, one age group or one language, because the groups it handles well outweigh the ones it doesn't. So we compare results across groups.
Yes. Bias and fairness checks across demographic and linguistic groups are part of the service.
Your model's outputs, and agreement on what a correct answer looks like. No accuracy targets yet? That's a good first conversation to have with us.
It depends on how fast your users, products and language change. We agree a schedule with you, check a fresh sample of outputs against human judgment each time, and report back.
Yes. Send a short brief and we'll evaluate a small sample free before you commit.
Yes. The NDA is signed before any data moves, we use it only for the scope we agreed, and only the people working on your project can get to it. It's returned or deleted when you ask.
Pick the checks you need, say what your model does and which groups matter, and send it. We'll evaluate a small sample free before you commit.
This opens your email app with the brief filled in. Nothing is sent until you press send. You can also use the contact page.