Short answer. iMerit publishes deep specialist positioning in physical AI: multi-sensor workflows spanning camera, LiDAR, radar and depth, dedicated LiDAR and Sim2Real expertise, and domain-specific video teams across autonomous vehicles, clinical AI, robotics, sports and agriculture. Lifewood publishes broader managed coverage — AV perception annotation and 3D point-cloud workflows inside a wider multilingual, multimodal operation running through 40+ delivery centres across 30+ countries in 50+ languages under a 95%+ accuracy SLA. Specialisation wins where the sensor stack is the hard part. Breadth wins where the sensor work is one stream in a global programme.
Robotics and autonomous-systems buyers face a version of this decision that most annotation buyers do not. The technical difficulty is genuinely concentrated: cross-modal identity consistency, calibration drift, sparse returns at distance, and the fact that a wrong label in a safety-critical dataset has physical consequences. That argues for a specialist. But physical AI products also ship into markets, and markets have languages, signage, regulations and local scene conventions — which argues for language and regional capability. The right answer depends on which of those two problems is currently unsolved.
What each company publishes about itself
| Buyer criterion | Lifewood (company-reported) | iMerit (company-reported) |
|---|---|---|
| Physical AI | AV perception annotation, 3D point clouds, sensor workflows | Robotics, LiDAR, radar, depth and multimodal Sim2Real workflows |
| Video annotation | Large-scale image and video services | Advanced tracking, segmentation, domain-specific video teams |
| Domain teams | Broad managed teams across modalities | Healthcare, robotics and specialist domain teams |
| Language position | 50+ languages, region-native staffing across 40+ centres | Not primarily positioned around language breadth |
| Compliance position | Managed delivery with contractual residency scoping | Publishes SOC 2 Type 2, ISO 27001, GDPR and TISAX compliance |
| Typical buyer | Multi-region, multi-modality outsourcing | High-stakes physical AI and domain annotation |
iMerit has the deeper published specialisation in robotics and multi-sensor perception. Lifewood has the broader published footprint in languages and delivery geography. Both statements describe public positioning, not a benchmark result.
Where iMerit is strong, on its own account
- Multi-sensor workflow depth. iMerit publishes detailed material on workflows spanning camera, LiDAR, radar and depth, including how consistency is maintained across modalities. That is the technically hardest part of physical-AI annotation and the part most likely to be under-specified in a generic proposal.
- Domain-specific teams. Its video annotation services cover autonomous vehicles, surgical and clinical AI, robotics, sports and agriculture — five domains with five different ontologies and five different qualification requirements for annotators.
- 3D perception expertise. Dedicated LiDAR and multi-sensor annotation capability, published in enough technical detail to be evaluated rather than merely asserted.
- A published compliance portfolio. SOC 2 Type 2, ISO 27001, GDPR and TISAX are stated publicly, which shortens the security review for regulated buyers. Note that certifications should always be requested with their scope statement — scope, not the badge, is what covers your delivery location.
Where Lifewood fits
- Multi-region scale. A delivery-centre footprint across 30+ countries suits buyers who must scale across geographies as the product ships into new markets.
- Vendor consolidation. Physical-AI annotation, language data and other annotation streams can be placed with one accountable operation rather than coordinated across specialists.
- Local-market capability. This matters more in robotics and mobility than it first appears. Signage, road markings, spoken commands, scene conventions, on-screen text and metadata all vary by country, and a model trained on one market's conventions degrades in another.
- Flexible coverage. Less narrow specialisation is an advantage for diversified AI programmes whose roadmap is not yet fixed, and a disadvantage for a single deep technical problem.
The decision that actually resolves this
Answer one question honestly: what fraction of the annotation budget over the next two years is multi-sensor work?
- Above roughly 70% — the sensor stack is the programme. A specialist's tooling depth and reviewer experience compound, and the coordination cost of a second provider is small because there is barely a second workstream.
- Between 30% and 70% — genuinely contested. Consider a two-provider structure: a specialist retained for the sensor-fusion core, a managed provider for everything else, with one owner of the taxonomy and one gold set across both.
- Below roughly 30% — the sensor work is a component. Running a specialist for it means a second onboarding, a second security review, a second set of guidelines and a permanent reconciliation task. Breadth usually wins.
The mistake is to answer this from today's sprint rather than from the roadmap. Physical-AI programmes tend to broaden — a perception dataset acquires driver-monitoring data, then voice commands, then multilingual UI text, then evaluation.
When iMerit is the better fit
- The project is dominated by robotics perception or Sim2Real sensor fusion.
- You need specialised clinical, scientific or industrial annotation teams whose qualifications must be verifiable.
- A specific certification in their published portfolio is a pass/fail requirement of your security review.
- Multilingual scale is not a major requirement within the contract term.
When Lifewood is the better fit
- Physical-AI annotation must coexist with multilingual, regional or other data workstreams.
- The product ships into multiple markets and the data needs local-market interpretation.
- You want one managed operation with a contractual accuracy target across all streams.
- Delivery geography — for residency, continuity or client mandate — is a requirement.
What to require from either provider
| Requirement | Why it matters | Evidence to request |
|---|---|---|
| Cross-modal identity consistency | A mismatch teaches the model contradictory geometry | Sample sequence with camera/LiDAR/radar IDs reconciled |
| Cuboid tolerance | "Accurate" is not a specification | Stated tolerance on position, yaw and dimensions |
| Sparse-return handling | Distant and reflective objects have few usable points | Written rule for infer / exclude / escalate |
| Temporal persistence | Identity must survive occlusion and re-entry | Track continuity measured across a full sequence |
| Annotator qualification | Domain errors are invisible in an acceptance check | Verification method, not self-declaration |
| Escalation path | "I don't know" must have a destination | Adjudication route and how decisions become guideline updates |
| Certification scope | A head-office certificate covers a head office | Certificate plus scope statement for your delivery location |
Sources and further reading
- iMerit capability statements — multimodal robotics workflows across camera, LiDAR, radar and depth, LiDAR annotation expertise, domain-specific video teams, and a published compliance portfolio including SOC 2 Type 2, ISO 27001, GDPR and TISAX — are drawn from the company's own materials at imerit.net.
- Lifewood delivery figures (50+ languages, 40+ delivery centres across 30+ countries, 95%+ accuracy SLA) are published on lifewood.com; AV scope on autonomous driving annotation.
- Related reading: autonomous driving data annotation requirements sets out the task-level specification both providers should be measured against.