Hacker Newsnew | past | comments | ask | show | jobs | submit | Jay_D's commentslogin

The transaction fee comes into picture only once during the entire project. Here’s the breakdown.

1. Users start a project and send it for review 2.Client, signs up, approves and pre-funds its (escrow-like). These funds sit in an escrow like account with us. 3.The user creates tasks and assign budget from the funds. 4.When the work is done, the user moves the task for review (approval workflow) 5.If the client approves, the funds assigned to the task move to your account. If he doesn’t, he can request/specify modifications. (Payment workflow)

Hope I made sense.


There is a fee that gets piled up during ‘payout’ though - when we send money to users bank. As you mentioned, this can be made to do batch wise daily or weekly or manually :)


This, as a side effect, is useful to the clients as well:

1. Don't have to pay a non-refundable advance. 2. Have complete visibility of the budget right from the dashboard. 3. Move smaller tranches of money to the service guy by approving tasks rather than moving big chunks of it. 4. Always have complete control on each dollar that is move to the service provider. 5. Also, enjoy working with a happy vendor who is getting paid regularly, which sort of improves the odds of winning.


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

Search: