Data collection
Deepen AI's trained operators run recording sessions to your spec and capture the scenarios your robots need, with every session logged and checked.
Rate in your plan before you pay A plan within 2 working days No sales call
What a logged session looks like
Each session is checked against your spec before it reaches you, and anything outside it is recorded again or raised with you.
- Spec
- 50 teleoperated picks of mixed items from a bin, with both arms.
- Session 14
- 50 picks recorded, including 3 dropped items.
- Checked as
- AcceptedAll 50 picks meet the spec, and the 3 drops are labeled as failed attempts.
- Reason
- Your spec asks for failed attempts to be kept and labeled, not deleted.
- Spec
- Warehouse aisle runs in low light, under 50 lux.
- Session 22
12 runs recorded.- Checked as
- Partly re-recorded7 runs measured 120 lux and were recorded again with the dock lights off.
- Reason
- Every session log includes a light reading, so runs outside the spec are caught before delivery.
- Spec
- Door-opening demonstrations on 10 doors, pushing and pulling.
- Session 40
- 10 doors, push and pull, each with a note on the handle type.
- Checked as
- AcceptedEvery door and direction on your checklist is covered.
- Reason
- The notes match your scenario checklist, so each run is easy to find later.
- Spec
- Kitchen tasks with 20 different mugs.
- Session 31
- 20 mugs, 4 of them the same model in different colours.
- Checked as
- Sent to youDo colour variants of the same mug count as different mugs?
- Reason
- Your answer is added to the spec for every later session.
How we start on your work
No sales call. A plan in your inbox, then a short paid pilot on real sessions.
What we need from you
- Your collection spec: the tasks, the scenarios and how many of each
- Your robots, rigs or teleoperation setup, and how sessions are recorded
- A checklist of what makes a session usable
- 5 minutesTell us the task
What you need recorded, how much, and where the robots or rigs are.
- Within 2 working daysGet a plan and a price
Operators, hours, the rate, start date and the total price.
- 2 weeksRun the pilot
We train operators on your setup and spec, run real sessions and send two weekly reports. Then you decide.
Who collects, and how sessions are checked
Trained operators, working in English. Each one learns your setup, your spec and your safety rules before recording, and every session is checked against your checklist.
Every reviewer's accuracy is measured
Items you've already answered are hidden in the real work, so we know how accurate each person is.
Nobody guesses on unclear cases
The team lead decides, or asks you. Your answer joins the guidelines.
You see the results every week
A weekly report shows work done, QA results and what's improving.
Standard collection covers teleoperated demonstrations and recorded scenarios with your equipment. On-site and vehicle collection programs are scoped by the enterprise team.
How much does data collection cost?
Data collection is quoted in your plan, because the rate depends on your setup, where sessions happen and the skills they need. You pay for the hours operators work, with a team lead, QA checks and a weekly report included.
Set before you pay. Your plan shows the rate, team size, hours and total price.
Starts with a two-week pilot on real sessions, paid upfront, with two weekly reports.
Your data stays protected. We work under NDA with the access you set. Deepen AI holds SOC 2 Type II, ISO 27001, ISO 9001 and TISAX.
Questions
Where does collection happen?
Where your plan says: remotely, by teleoperating your robots, or on site with your equipment. On-site and vehicle programs are scoped by the enterprise team.
Do you keep failed attempts?
Your spec decides. Many teams keep them, labeled as failures, because they help a model learn what not to do.
How do we know every scenario is covered?
Sessions are logged against your scenario checklist, and the weekly report shows how many runs each scenario has and which still need more.
What format do recordings come in?
The one your setup records, with a session log for each recording: the scenario, the conditions, the operator's notes and the checks it passed.
How do operators handle safety?
Operators learn your safety rules and procedures before the first session, and follow them on every run.
Can collection follow what curation finds?
Yes. When curation finds a gap, it becomes part of the next collection spec, so the team records what your data is missing.