Show HN: A fair, simple and free alternative to freelancing platforms
freelancerprotocol.com
freelancerprotocol.com
Freelancer Protocol is for people who haven’t met on a platform and need a framework to engage in a standard deal. Deal finalisation (deliverable against money) is conditioned to the client accepting a demo (link or video) of the working code. The framework has basic features, like paperwork generation (invoice & contract) and communication (chat and file share).
I just integrate with Stripe for payment & invoice. After checking out a couple of APIs, decided to go with https://esignatures.io/ for online contracts/signatures. They charge per contract and have the features I need (Templates mgmt + Zapier integration).
Please let me know if you know a better way for me to integrate chat (right now I use the firebase db and messages load with a little lag, it’s not a meant for this use case). Feel free to reach out to hello@freelancerprotocol.com or in the comments.
Perhaps consider making it more clear what it is you do - something like "Contract and escrow service for freelancers" or something along that line, rather than the current "A fair, simple and free alternative...".
Also, the flow diagram under "How it works" is helpful, but please don't repeat the animation. I was still busy reading the part under what happens when the client rejects when the diagram was cleared and the animation started again. Even better would be if you don't animate it at all as I think it goes too fast for non-native English readers such as myself.
Best of luck with the platform!
+------------------------------------+
| Milestone starts |
| |
| when both parties accept its terms |
+------------------------------------+
|
| Money is transferred
| into escrow account
V
+-----------------------------------------+
| Freelancer uploads |
| |
| a demo (link or video) and deliverable. |
| Client only receives the demo |
+-----------------------------------------+
| |
/ \ / \
/ \ / \
/ \ / \
/ \ / \
< Accepts > < Rejects >
\ / \ /
\ / \ /
\ / \ /
\ / \ /
| |
V |
+---------------------------------+ |
| Transaction gets made | |
| | |
| Freelancer receives the money, | |
| Client receives the deliverable | |
+---------------------------------+ |
V
+-----------------------------------------+
| Lose-lose |
| |
| Freelancer only receives a third of the |
| sum, rest is paid back to client. |
| Client doesn't receive the deliverable. |
+-----------------------------------------+I wonder if one can optimize that balance to abuse this structure.
We could exclude any freelancer that abuses this structure to just get the 'easy third' and any clients that repeatedly reject whatever freelancers do even when it corresponds to their requirements.
I'm always looking for a more fair and less hackable model though.
A client that rejects the demo has to justify in what regards it doesn't respect these terms, if not, it's a breach (of freelancer protocol rules and of the contract).
Maybe I should make this more explicit on the landing page?