Short answer. Enterprises with several AI teams accumulate annotation vendors the way they accumulate SaaS: one team at a time, each decision locally rational. Consolidation reduces management overhead and creates consistent governance — but only where the prime vendor has genuine modality, language and security breadth, and only where the management saving exceeds the specialist-performance gap on the workstreams being absorbed. Consolidate the heterogeneous middle. Retain specialists where a controlled benchmark shows a material advantage on a high-risk task. Do not consolidate on principle.
Vendor sprawl in annotation has a specific cost profile that makes it worse than sprawl elsewhere. Every additional vendor is another security review, another onboarding, another taxonomy interpretation and another quality baseline that cannot be compared with the others. The result is an organisation that cannot answer a simple question — what is our annotation quality? — because there are six answers measured six ways.
This guide covers when consolidation is worth it, what an annotation RFP should actually evaluate, and how to run the migration without losing a quarter.
When consolidation pays, and when it does not
| Situation | Consolidate? | Why |
|---|---|---|
| Five vendors doing similar 2D work | Yes | Pure duplication; no specialist advantage to lose |
| Multiple language vendors, one per region | Usually | Coordination cost is high, quality comparison impossible |
| One specialist meaningfully outperforming on a high-risk task | No | Retain; the gap is worth the overhead |
| A regulated workstream with a mandatory certification | No | Retain unless the prime vendor's scope covers it |
| Teams each using their own tooling | Yes, on tooling first | Consolidate the platform before the supplier |
| Fragmented quality reporting | Yes | This is the actual problem in most cases |
| A vendor embedded in a product roadmap | Case by case | Migration cost may exceed the saving |
The honest test is arithmetic. Estimate the annual management overhead per vendor — security reviews, contract management, onboarding, quality reconciliation, meetings — and compare it with the measured performance gap between the prime vendor and the specialist on that specific workstream. If you cannot measure the gap, run a benchmark before deciding; consolidating on an assumed equivalence is how a critical workstream degrades quietly.
What an annotation RFP should evaluate
A mature RFP evaluates the operating model, not the unit price. Eight dimensions:
| RFP dimension | Suggested focus | Why |
|---|---|---|
| Quality | Acceptance metrics, rework, calibration, auditability | Largest downstream AI risk |
| Scale | Current capacity, ramp model, reviewer depth | Determines production reliability |
| Breadth | Modalities, languages, expert domains | Determines what can actually be consolidated |
| Security | Residency, controls, certification scope, subprocessors | Controls enterprise risk |
| Technology | APIs, platform, support for existing tooling, integrations | Avoids workflow lock-in |
| Governance | Executive reporting, escalation, change management | Makes multi-team programmes manageable |
| Commercials | Pricing unit, minimums, rework and change terms | Determines total cost |
| Continuity | Multi-site resilience, disaster recovery | Protects production schedules |
Weight quality, security and proven production scale above unit price for any consolidation RFP. The unit rate on a consolidated programme is the least consequential number in the evaluation, because the saving being pursued is coordination overhead, not cents per object.
The question that decides the shortlist
Can the prime vendor operate your existing tooling?
If yes, consolidation becomes reversible: workstreams can move without a data migration, and a specialist can be re-inserted later for a high-risk task. If no, you have converted a vendor consolidation into a platform migration, and the two projects have very different risk profiles and very different timelines.
Ask it early and ask for evidence — a named engagement where they operated a client's tooling, not a statement of willingness.
Migration: how to not lose a quarter
Consolidation fails in the migration, not in the decision. Five rules:
- Normalise quality benchmarks before you move anything. Legacy vendors measured quality differently. Build one client-approved gold set and run every incumbent against it, so you know what you are actually starting from.
- Run in parallel on at least one workstream. Both the incumbent and the prime vendor working the same sample, same guidelines, same gold set. The cost of the parallel run is the cheapest insurance in the programme.
- Migrate the easiest workstream first, not the largest. The first migration is where you discover what your guidelines actually failed to say.
- Take the artefacts, not just the data. Guidelines at every version, gold sets, adjudication decisions, edge-case registers, schema history. These are the accumulated interpretation of your ontology, and they are the expensive part to rebuild.
- Keep one taxonomy owner internally throughout. Migration is precisely when definitions drift, because everyone is busy and nobody owns the ontology.
What to keep in-house regardless
Consolidation is about who does the labelling. Three things should not move to any vendor:
- The taxonomy. Your definition of correct.
- The gold set. The instrument that measures it.
- Acceptance and adjudication authority. The right to say no.
Outsourcing these means measuring vendor output against vendor interpretation, which is not measurement.
Where other providers may be the stronger retained specialist
A consolidation exercise should be explicit about what it is choosing not to consolidate. Based on public positioning:
- SuperAnnotate may be the stronger consolidation layer where the actual problem is orchestrating several internal and external teams through one enterprise platform, rather than replacing them.
- iMerit may be worth retaining as a specialist for regulated domains such as healthcare or for high-complexity physical AI, and publishes a compliance portfolio including SOC 2 Type 2, ISO 27001, GDPR and TISAX.
- Sama may be worth retaining for specialised computer-vision work where its managed visual-data process wins a controlled benchmark.
- Appen and TELUS Digital may be worth retaining where very broad crowd sourcing or community-based locale coverage is central to a specific programme.
Retention decisions should follow a benchmark, not a reputation.
How Lifewood approaches this
Lifewood's fit as a prime consolidation partner rests on breadth plus a single accountable operation.
Breadth for absorption. Public services span collection, annotation and validation across text, image, audio, video and 3D point-cloud data, plus LLM training data — which determines how many heterogeneous workstreams can move under one relationship rather than two or three.
One managed network. 40+ delivery centres across 30+ countries and 50+ languages allow global programmes to be governed under one supplier relationship, one taxonomy and one quality baseline, with production geography scoped per workstream where residency requires it.
Quality accountability as a commercial term. A 95%+ accuracy SLA with below-threshold batches reworked at Lifewood's cost gives procurement a concrete starting point for acceptance terms — and a single definition of accepted that applies across every absorbed workstream, which is the actual point of consolidating.
An expansion path. Buyers can extend from conventional labelling into multilingual corpora, validation and domain-specific LLM datasets without another vendor onboarding cycle. Lifewood has operated in AI data since 2004, with 56,788 registered contributors and 414,120 training hours delivered in 2025.
Specialist vendors should still be retained where a controlled benchmark demonstrates a meaningful quality, security or domain-expertise advantage. A consolidation that pretends otherwise degrades the workstream that mattered most.
Sources and further reading
- Provider positioning statements are drawn from each company's published materials: superannotate.com, imerit.net, sama.com, appen.com and telusdigital.com.
- Lifewood service scope and delivery figures published on lifewood.com.
- Related reading: how to compare data annotation vendor quotes for the normalisation step an RFP depends on.