NLP Data deliveries
We publish no fixed listings, because nothing is held in stock. What follows is the structure every NLP Data delivery takes. The fields your specification needs, and what actually arrives in the package.
Why there is nothing to add to a cart
A catalog listing answers the question "what do you have?" Our model answers a different question: "what do you need?" Every NLP Data project is quoted from a specification, which means the price, the timeline and the data itself are all derived from your requirement rather than from something already built.
The tradeoff is real and worth stating plainly: the timeline starts when the specification is agreed, not when you click a button. What you get in exchange is a dataset that matches the requirement, and (for anything unusual), one that is not also available to your competitors.
What arrives in a delivery
| Component | What it is |
|---|---|
| The data files | Format, structure and segmentation set to your pipeline. Named to a convention you specify. |
| Labels or transcription | Orthographic, phonetic or categorical, produced under a guideline you review before production starts. |
| Contributor metadata | The attributes that let you slice the set: age band, gender, region, dialect background, or whatever your task turns on. |
| Collection conditions | Environment, device and, where it can be measured, signal quality: recorded per file. |
| Annotation guideline | The document the annotators worked from, so you can reproduce the conventions on your own data. |
| Consent records | Signed contributor consent covering your intended use, plus cross-border transfer terms where they apply. |
| Collection methodology | How contributors were recruited, screened and scheduled. The part that tells you how biased the pool is. |
| Quality report | Pilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them. |
Specification fields for NLP Data
- Volume:total hours, and minimum distinct speaker count. The second number constrains the project far more than the first.
- Language and variety:including dialect where the language has meaningful internal variation, and script where the language has more than one writing system.
- Recording conditions:studio, home, mobile, or a named environment with a target signal-to-noise ratio.
- Annotation depth:Whether the annotation guideline document and inter-annotator agreement (IAA) figures are provided.
- Delivery format:audio container and sampling rate, segmentation length, metadata schema.
- Compliance scope:where the speakers are, where the data will be used, and whether the model will be distributed.
Next step
Send the specification and you will get a real number and a real timeline. If the requirement is not something we can source well, we will say so rather than take the order.
Request NLP Data
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.
- You send the spec Language, hours, recording conditions, and the deadline.
- We reply within two business days A real number and a real timeline, not a range.
- You approve a pilot batch A small run first, so problems surface before the full order.
- Full run, then delivery with documents Audio, transcripts, and the consent record for every speaker.