Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Could you please explain how you will address:

* quality: How do I know the quality of the work will be good? What happens in the case of disputes?

* reputation: How will you keep track of reputation of the workers? Odesk, Vworker, Ebay are marketplaces that do a decent job at filtering out spammers and bad guys. Where they lack is determining the difference between good and great. Everyone gets FIVE STARS or close to it for every job, unless it's completely bungled. This also creates a perverse pressure on the contractor. If an employer complains about the contractor publicly, the contractor quickly lose all work. Workers are thus pressured to satisfy out-of-scope employer demands so they get a five star rating and maintain their sterling reputation.



* quality: Matching the task with the right providers is crucial. At the moment we do a lot of manual vetting, making sure each task gets to the right people and everyone is happy. Over time we will collect more data to improve matching. Disputes are handled by ourselves right now and we want to have humans in charge for these things in the future.

* reputation: We also have a rating system in place which is used to give the provider feedback on their work and also helps us with matching future tasks. Buyer will get rated too. At work.io the buyers don't have to choose the provider but only defines what results they want to have delivered. There is the option to buy services directly by someone but these deals are normally done because of the reputation someone has outside of work.io


In addition to what luca said: We take a lot of pressure out of the marketplace by not having a biding mechanism in the first place, so better matches in terms of budget / skills etc are likely (happy to go into more depth on this) and we also collect tons of implicit data, so once we should get some traction, it should be easier to model the current manual work we do behind the scenes into corresponding algorithms (also happy to expand on this).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: