Feature Update: New User Interface and Simplified Jobs Process

 13   Tweet

This post hasn't been updated in over 2 years.


Using Microlancer is a collaborative process. From the time a buyer submits a brief, to the completion of the job, there is generally some back-and-forth to share work in progress and feedback. We work hard to facilitate these conversations, and to make it as easy as possible for jobs to get completed efficiently.

With that in mind we recently interviewed Microlancer users and dived into the data to help get a better understanding of where and how we can improve the process.

As a result of our analysis, we’ve simplified the job process and redesigned the user interface to make it easier for providers to submit work and for buyers to approve work. Importantly, providers no longer need to mark a job as completed, and the status of the job and next steps are clear at all times.


We’re confident that these changes will provide greater clarity regarding what comes next with jobs, reducing delays and speeding up the time to job completion.

This new user interface is now live! Previous and in-progress jobs will keep the original user interface.

As always, we’d love any feedback you have regarding the changes. Let us know what you think in the comments.

 13   Tweet

Jordan McNamara

Jordan is the Communications Manager for Envato Studio and for the past 6 years has worked passionately to build and support the Envato community. He loves cats, sci-fi and video games.

More →


  1. That’s a very helpful feature you added. Being one of the top providers on Microlancer I’m sure it will come in handy when getting the final files to the client.

    Well done and keep them coming 🙂


  2. Good job MicroLancer. Let’s make this platform the most popular platform for high quality services with a fair prize for the service providers. I have suggestion for MicroLancer.

    Please let customers to review the Project as soon as we deliver it. Because long days mean less reviews and it means low social proof for ML Services. That’s not a good sign.

    Thank you,

  3. Hi – The problem with your flow (unless I am missing the link to it – then it is a problem with your architecture) is that it doesn’t allow for a pre-sales conversation but forces you to purchase immediately. This pushes one out of your environment and onto the developer’s site and inevitably leads to the deal being consummated outside of your involvement.

    This should be fixed. Again, unless I have missed the link to the question box.

    Thank you.

    1. Thank you so much for this feedback! The good news is this another area we’ve identified as needing work and have kicked off the planning for addressing this concern. 🙂 Keep the suggestions coming 😉

  4. Might be semantic, but the use of the term ‘revision’ is misleading for the first version or draft.

    The ‘revisions’ should be counted from the second submission, or perhaps be called something else, like versions.

  5. The new system is easier to use.
    Just my suggestions:
    1) A button to add extra revisions
    2) Two different buttons for submitting and conversing
    i.e SUBMIT – reduces the number of revisions
    SEND – to discuss small changes

    Other than that the system is great and very helpful.
    Keep em coming.

Leave a Reply

Your email address will not be published. Required fields are marked *