Playment (YC W17) gives companies on-demand workers to analyze data using mobile
techcrunch.com
techcrunch.com
I am Ajinkya (AJ) co-founder Playment. We started Playment as mTurk is highly unreliable in terms of data output quality or reliability. We focus on the standardisation of work across workers. In a nutshell we provide enterprise grade SLAs.
We deploy algorithms to generate high quality crowdsourcing output rather just grading the workers. Building a mobile workforce makes us faster than any other existing mTurk like solution. It's an fully managed platform where the task requester needn't worry about the task design or worker selection or deciding worker incentives. Everything is managed by the platform itself. Just share the requirements and data and we do it all.
The use cases that Playment target are cataloging for e-commerce, training data for AI (text classification, transcription, bounding boxes and image annotation).
We have written a whole piece on Playment vs. mTurk - https://playment.io/playment-vs-mechanical-turk
Would appreciate more comments and remarks. Hope you find this useful.
Algorithms are only as good as the data that trains them. Besides having basic product features such as building bounding boxes on the images, identifying objects from images, context based text classification etc, we could also support multi step complex workflow. For example, for self driving cars, from a given image we could first find out if there are pedestrians present or not, then # of such pedestrians, then build boxes around it and finally tag them as males and females. To make it even more simple for our customers, we take over the complete ownership of building such complex workflows and ensuring quality.
Our platform can currently support services like image tagging, transcription, text tagging and bounding boxes. And workflows could be built using combination of these services.
At the end of the day, we have more than 100,000 skilled workers. We would love to hear more about various use cases that people would need definitely need humans for. :)
So there are quite a few differences, the primary being the quality & spam problem that mTurk has. We have a number of quality assurance models which help us promise enterprise grade SLAs to our customers.
Moreover, mTurk is limited to requesters from a few countries. We don't have any such restriction.
Also, Our product enables us to stitch together multiple tasks to model complex multi-step workflows so you don't need to take the hassle of setting up multiple tasks and compiling their results. Playment just does all of that for you.
We've put up a comprehensive piece on this: https://playment.io/playment-vs-mechanical-turk
1) SLA (Quality and turn-around times) assurance
2) Fully managed solution. Just send us the data and guidelines, we take care of the rest.
3) Support complex workflows
We wrote an elaborate piece on our differentiation against mechanical turk! Check it out on - https://playment.io/playment-vs-mechanical-turk