Championing a fairer deal for client and freelancer

Why we're building Freelancer Protocol

The issues most commonly faced by both sides of the table haven't changed much in over two decades of freelancing.

The difficulty freelancers experience in getting consistently paid on time remains at the top of the list.

A design problem...

Employees are sure they'll receive their monthly salary. As it's one of their company's core responsibilities, the payment process is recurring and automated.

In opposition, for a freelancer to get paid, their client has to produce an effort outside of their daily habits. That makes the payment a one-off and manual process.

In practice, this changes everything.

A day in a freelancer's life

Sources: IPSE, CWJobs

...calls for a design solution

That's what we're set out to do with Freelancer Protocol, through a simple process:

  1. Projects are broken down into intermediary steps - we call them milestones. A milestone has a deliverable and a price, as well as a start and end date.
  2. We charge the client when each milestone starts and pay the freelancer when it ends, given the deliverable is uploaded by the deadline.

This means both sides:

  • give and receive throughout the project
  • manage their risk

    Bad project risk can't be eliminated altogether, but it can be reduced. Both sides are free to cancel all milestones that haven't started. This means that, from a client perspective, there's never more at risk than the current milestone amount.
  • enjoy relative outcome and timing certainty

    The freelancer is assured to be paid and to be paid on time, as funds are with us when the work starts. The client knows they'll have the deliverable on time - if not, they can choose to cancel or request a modification of terms.