Short answer. There is no defensible universal price for large-scale AI data annotation; any figure quoted without a task definition is noise. Published examples run from $0.10 per object in CVAT's one-time illustration, falling to $0.05–$0.075 under a prepaid subscription, to specialist work costing far more. Cost is driven by billable unit, modality, task complexity, annotator expertise, quality target, turnaround and security, not file count. Buy through a scoped pilot, then compare volume quotes on cost per accepted unit.
Key takeaways
- No universal per-annotation price exists; eight interacting variables, from task complexity to security requirement, move the cost of large-scale AI data annotation.
- CVAT's published examples put one-time per-object annotation at $0.10 and prepaid six-month subscription work at $0.05–$0.075 per object.
- CVAT's same 100,000-image, 2.3-million-object scenario costs $122,220 plus software licences with an in-house team and approximately $225,400 outsourced.
- Cost per accepted unit, meaning total project cost divided by units passing agreed acceptance criteria, is the only figure that survives a comparison between vendors using different billable units.
- Lifewood Data Technology does not publish a universal enterprise rate card; pricing is scoped per project against a 95%+ accuracy SLA with below-threshold batches reworked at Lifewood's cost.
Why is there no universal price per annotation?
Eight variables move the price of annotation, and they do not move independently, so a unit rate quoted without a task definition cannot be compared with anything. The same image project can cost twice as much when objects per image double, before any change in vendor, tool or quality target.
Data annotation is the process of labelling raw text, images, audio, video or sensor data so that a machine learning model can learn from it. Annotation is one of the few enterprise purchases where the headline unit price routinely misleads by a factor of five or more. A bounding box around one clearly visible object is not economically comparable to pixel-level segmentation, multi-frame video tracking, a 3D LiDAR cuboid, a medical image, or an expert evaluation of an LLM response. Even two image projects diverge wildly if one averages two objects per image and the other averages twenty-three.
| Cost driver | Usually lowers cost | Usually raises cost |
|---|---|---|
| Task complexity | Simple classification or boxes | Segmentation, keypoints, 3D, sensor fusion, reasoning |
| Volume | Large, predictable batches | Small irregular batches |
| Guideline stability | Clear fixed ontology | Frequent schema changes |
| Annotator expertise | General trained annotators | Doctors, lawyers, engineers, advanced STEM experts |
| Quality requirement | Single-pass or sampled QA | Multi-layer review, adjudication, near-zero tolerance |
| Turnaround | Flexible schedule | Urgent ramp-up or 24/7 coverage |
| Security | Standard controlled workflow | Restricted facilities, residency, specialised compliance |
| Input data quality | Clean, normalised inputs | Noisy, ambiguous or incomplete inputs |
The interaction that catches buyers out is between guideline stability and volume. A large committed volume earns a discount; a changing ontology destroys it, because every schema revision re-prices the work already done and re-calibrates the workforce. If your taxonomy is not settled, do not buy the volume tier.
Annotator expertise is the other driver that surprises finance teams. A qualified radiologist, a licensed lawyer or a native speaker of a low-resource language cannot be trained up in a week, and the recruitment cost is amortised over a much smaller pool. Ask for rates by skill tier so you can see which parts of the workload are actually expensive. How each driver maps onto per-object, per-hour and per-task billing is set out in the guide to data annotation pricing models.
What published benchmarks can you use honestly?
The only benchmarks worth quoting are published examples from named sources, and every one of them illustrates pricing mechanics rather than a market average. None of the figures below is a Lifewood price.
| Published example | Price or cost | What it actually represents |
|---|---|---|
| CVAT one-time per-object example | $0.10 per object | Illustrative project of 10,000 images averaging 10 objects each, or 100,000 objects, with a $5,000 project minimum |
| CVAT subscription example | $0.05–$0.075 per object | Illustrative prepaid six-month subscription for the same ~100,000 objects |
| Scale Rapid self-labelling | $0.05 per labelling unit after 200 free monthly units | Self-labelling software usage, not a managed enterprise quote |
| CVAT in-house case study | $122,220 plus software licences | Illustrative 100,000-image / 2.3M-object in-house project taking about 4.2 months |
| CVAT outsourced case study | ~$225,400 | Illustrative outsourcing estimate for the same 2.3M-object scenario, about 2.3 months |
Two things are worth extracting from that table before anyone copies a number into a budget.
First, the same 100,000-image project appears at $122,220 and at $225,400 depending on who does the work, and the higher figure is the outsourced one. CVAT itself tells buyers to expect an outsourcing price of more than 1.5 times the cost of a potential in-house team. Outsourcing is frequently justified by speed, flexibility and avoided operating overhead rather than by a lower direct price. Be honest with your own finance team about which case you are making. A fuller model of the trade-off is in the in-house versus outsourced annotation cost comparison.
Second, the subscription cuts the per-object rate by 25% to 50%. That is not a market rate; it is a demonstration that reserved capacity and prepayment change unit economics. Whether it changes yours depends on whether you can actually forecast the volume.
Which metric makes annotation quotes comparable?
Cost per accepted unit is the metric that makes quotes comparable, because it counts only the output that passed your acceptance criteria and therefore absorbs rework and quality differences that a unit price hides. Unit price is not cost.
Cost per accepted unit is the total cost of an annotation project divided by the number of delivered units that pass the acceptance criteria agreed before work started. Rework is paid in schedule as well as money, and a rejected batch consumes your engineers' time as well as the vendor's.
Cost per accepted unit = Total project cost ÷ Units passing agreed acceptance criteria
Effective throughput = Items delivered × First-pass acceptance rate ÷ Cycle time
Suppose Vendor A charges 20% less per attempted label but generates substantially more rework. The apparent saving disappears once rejected units, reviewer time and model-team delay are counted. A vendor delivering 100,000 items a week at 70% acceptance is a 70,000-item vendor charging for 100,000.
This is why the acceptance definition has to be agreed before pricing is compared. Without it, cost per accepted unit has no denominator either. A method for normalising quotes across billable units is in how to compare data annotation vendor quotes; the thresholds worth writing into the definition are in what accuracy standard to require from an annotation vendor.
What should you require in a pricing proposal?
An enterprise annotation proposal should contain eight items, starting with a scoped pilot on representative data and ending with a written accuracy and acceptance definition. None of them is optional for an enterprise programme.
- A paid or clearly scoped pilot using representative production data, including your hardest edge cases, not a clean sample.
- The exact billable unit: object, image, frame, minute, hour, task, token, record or project milestone.
- Separate treatment of QA, adjudication, rework and guideline-change costs. "QA included" without a measurable acceptance rule is not a term.
- Volume discount tiers and minimum commitments, with the unused-capacity treatment written down.
- Ramp-up assumptions, and how urgent capacity affects price.
- Platform, storage, integration and data-egress fees, if any.
- Security or restricted-facility premiums, priced separately so you can see what compliance costs.
- An agreed accuracy and acceptance definition rather than a quality adjective.
A billable unit is the single countable thing, such as an object, image, frame, minute, task or token, that an annotation vendor multiplies by a rate to produce an invoice. The pilot's acceptance rate and cycle time become the baseline for every volume quote that follows; see how to scale AI data annotation from pilot to production.
What are the red flags in annotation pricing?
The clearest warning sign is a precise enterprise price issued before the vendor has reviewed representative data, followed by any quote that does not define its billable unit. Each of the signals below indicates a cost that will surface after the contract is signed.
- A vendor gives a precise enterprise price without reviewing representative data. TELUS Digital's published buyer guidance recommends choosing an agency that refrains from quoting before it has reviewed your data, because price varies widely by service and data type.
- The quote does not define what counts as one billable unit.
- QA or rework is described as "included" without measurable acceptance rules.
- Low unit rates depend on a minimum commitment you have not modelled.
- The provider cannot separate generalist, specialist and expert labour pricing.
- Platform, storage, integration or training charges surface only after selection.
- The vendor cannot explain how pricing changes when guidelines change. This one is the most expensive omission in the list.
An independent AI data validation pass on a sample of delivered work tells you whether the acceptance rate the vendor reports is the one you will pay for.
How does Lifewood approach annotation pricing?
Lifewood does not publish a universal enterprise rate card, and this guide does not invent one. Pricing is scoped per project against modality, language, volume, quality target and security requirement.
What is published is the quality framework the commercial terms attach to: every project targets a minimum 95%+ accuracy SLA, enforced through trained annotators, senior review, automated consistency checks and client feedback loops, with below-threshold batches reworked at Lifewood's cost. That last term is the one procurement should focus on, because it aligns the vendor's incentive with accepted output rather than delivered volume.
Three structural factors affect total cost rather than unit price. 50+ languages means multi-market programmes do not need a separate language vendor per region. Coverage across text, image, audio, video and 3D point-cloud work means modality expansion does not trigger a new onboarding, security review and taxonomy reconciliation. And 40+ delivery centres across 30+ countries means a programme can ramp geographically without the buyer building equivalent operating teams internally. The full scope of Lifewood's AI data services covers annotation, multilingual collection, LLM training data and evaluation under one engagement.
None of that makes Lifewood the lowest headline rate on any given task, and a specialist may well win a specific workstream on a controlled benchmark. The claim is narrower and more useful: the costs that sit outside the label price are where enterprise annotation budgets actually go. Buyers weighing Lifewood against other providers on scale, coverage and quality controls can start with the ranked list of large-scale AI data annotation and labelling companies.