
Mechanical Turk for enterprises.
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Playment (W17).
Playment began in Bengaluru in 2015 as a mobile marketplace for small human data tasks. The founders first applied it to e-commerce catalog work, then narrowed the company around managed training data for computer vision. By the time of its exit, Playment combined annotation software, project design, quality control, and a secure workforce for image, video, and LiDAR projects.
This was a successful capability sale. Playment learned that enterprise labeling required much more than a large crowd. Customers bought workflow design, security, specialist labor, and accountable quality. TELUS International already had global sales and more than one million annotators, so buying Playment accelerated its computer-vision product depth.[1] The acquisition completed on July 2, 2021; its price was not disclosed.[2]
Image 1 / 1
Siddharth Mall, Ajinkya Malasane, and Akshay Lal met through India's IIT network and later worked at Flipkart. Akshay worked on catalog products; Siddharth and Ajinkya helped build Flipkart's crowdsourced hyperlocal delivery operation. At Flipkart, they watched a captive business-process-outsourcing team of more than 500 people handle catalog operations while product volume changed unpredictably. Siddharth told YourStory: "We struggled to scale the team as millions of products got added to the catalogue."[3]
They started Playment in 2015 with Himanshu Sahu, an IIT Kharagpur classmate who had worked at Babajob. The first idea was a mobile app that broke catalog cleanup, content moderation, and other data operations into short tasks. Contributors, called players, chose work on their phones and earned rewards. Enterprises sent data through APIs; Playment split a project into microtasks, routed them to qualified workers, and aggregated the results.
The consumer crowd supplied elasticity, but enterprise buyers needed accuracy. Ajinkya told VentureBeat: "Legacy crowdsourcing platforms such as [Amazon's Mechanical Turk] don't assure quality."[4] Playment therefore sold a managed outcome instead of access to workers. Its software encoded task design, worker qualification, redundancy, and checking.
Customer demand then pulled the company toward computer vision. In 2017, Playment added bounding boxes, 3D cuboids, points, lines, and polygon segmentation. Autonomous-driving teams needed people to identify pedestrians, lanes, vehicles, and unusual road objects across large image and video sets. By November 2017, about 70% of Playment's roughly 30 customers were in autonomous driving.[4] The company had found a narrower, higher-value use for the operating system it first built for retail catalogs.
Playment sold a full labeling operation. A customer uploaded images, video, or sensor data and described the model behavior it wanted to teach. Playment's team translated that goal into label definitions and instructions, configured a project, trained workers, and returned checked annotations through files or APIs.
Read the complete post-mortem, the rebuild playbook, and the exact reasons Playment is still worth studying now.