What We Offer

Two dataset types. Three underserved languages. Nothing ships until it earns its way through.

Rootspeak builds native-authored training and evaluation data in Hausa, Yoruba, and Igbo — three of West Africa's most-spoken languages, and three of the most under-resourced in AI training data today. This page is the full, current catalog: exactly what we produce, and exactly how each unit earns its way into a dataset we're willing to sell.

2 data types in production
3 languages: Hausa, Yoruba, Igbo
7 gates, none skippable
The Catalog

What we produce, in every language we cover — no exceptions.

Two formats, built to the same standard, in all three languages. Both are live, tested pipelines — not a roadmap.

Instruction / Response Pairs

Native-authored prompts and completions

A native speaker writes a natural, fluent response to an assigned prompt — everyday situations, opinions, instructions, comparisons, and dozens of other categories, deliberately spread thin so no single topic starts to feel manufactured. Every response is original writing, never translated from English and never machine-generated.

Translation Pairs

English ↔ target-language sentence translation

A native speaker translates an English source sentence naturally into their language — not word-for-word, but the way a fluent bilingual speaker would actually say it. Back-translated and compared against the original source as part of the same quality process every unit goes through.

Language
Instruction / Response
Translation Pairs
Hausa
4,000task prompts built and liveInfrastructure ready
4,000source sentences built and liveInfrastructure ready
Yoruba
4,000task prompts built and liveInfrastructure ready
4,000source sentences built and liveInfrastructure ready
Igbo
4,000task prompts built and liveInfrastructure ready
4,000source sentences built and liveInfrastructure ready
How We Guarantee Quality

Seven gates. Skip one, and nothing reaches a dataset.

This is the actual pipeline every unit of work passes through — the same one our own operations dashboard is built around internally. Nothing here is aspirational; it's what genuinely has to happen before a unit becomes sellable.

Applied

A real person applies with their name, language, and a written sample of their experience — reviewed for basic legitimacy before anything else happens.
Why it mattersNo scraped identities. Every contributor is a real, contactable person from the start.

Vetted

A paid writing sample, screened by automated back-translation for machine-translation or LLM-generation patterns, then read and judged by a native-speaking Lead Linguist — before the contributor ever touches paid production work.
Why it mattersQuality is checked before volume, not after.

Consented

A signed Contributor Agreement on file, confirming compensation and consenting to inclusion in datasets licensed to third parties. No signature, no work assigned — the gate is enforced in code, not just on paper.
Why it mattersEvery record traces back to documented, provable consent.

Screened

Every submission is back-translated and compared for stylometric drift — a signal that flags likely machine-translated or copy-pasted text before a human ever reviews it.
Why it mattersContamination is caught early, not discovered by a buyer later.

Reviewed

An AI judge scores every submission against a written quality rubric — advisory only. The Approve/Reject call is always made by a native-speaking Lead Linguist. AI never decides what ships.
Why it mattersA human, native in the language, is accountable for every "yes."

Exported

Approved units enter the language's master dataset carrying full provenance: an opaque contributor ID, task type, consent reference, license reference, and reviewer ID — never the contributor's name or contact details.
Why it mattersContributor privacy is preserved without sacrificing auditability.

Packaged

Every 250 linguist-reviewed units are sliced into a numbered package, run through an integrity check (consent on file, no duplicates, no contributor PII in the text), and documented before it's ever offered for sale.
Why it mattersWhat we send you has already been checked twice — once by a person, once by a machine looking for what the person might have missed.
Ships With Every Package

Documentation your compliance review won't have to chase down.

  • ✓Signed consent, per unit. Every record in the package traces to a documented Contributor Agreement, not a blanket assumption.
  • ✓A data license agreement covering your permitted use, reviewed by counsel before it's ever sent.
  • ✓Full provenance metadata — contributor ID, task type, category, review history, and license reference on every record.
  • ✓QC documentation covering the automated screening and the human Lead Linguist sign-off behind every included unit.
  • ✓No scraped, machine-translated, or LLM-generated text presented as native-authored — checked at the screening gate, not assumed.
Boutique By Design

Three languages, done properly — not fifty done thinly.

Hausa, Yoruba, and Igbo were chosen for the same reason: tens of millions of native speakers each, real demand from AI labs building Nigerian and West African language coverage, and a fraction of the training data that population deserves relative to its size. We'd rather cover three languages this thoroughly than spread the same effort across a dozen we couldn't stand behind.

Contributors are paid per accepted unit, above local market rates, under signed agreements — never a race to the lowest bid.

Building in Hausa, Yoruba, or Igbo? Let's see if there's a fit.

Tell us what you're working on and we'll walk you through a sample matched to your use case — instruction data, translation pairs, or both.

Request a sample