In brief:

• Personal environment that provides interaction with more than 150,000 freelancers
• Goal to keep freelancers constantly motivated
• Built with Laravel, VueJS and integrate into different websites as a package

Why this project?

In addition to the payroll system, we want to offer the freelancers who work for our partner an environment in which they can log in. Here they can view their data, view their work orders and invoices and, for example, adjust their payment methods.

It is also up to us, together with the partner, to see how we can reduce the turnover of freelancers and thus increase loyalty.

What has been built?

We are now busy making the first version of this system. It has become a package so that we can easily integrate it into the different websites that are used to recruit freelancers.

Which tech has been used?

We have therefore again opted for a backend system built in Laravel, with a frontend from VueJS. One of the microservices that we have already split off is an authentication service, which is used to login to the freelancer portal.

All data should be linked to the custom payrolling system. This is done through an API.

What are the future plans?

With the introduction of a new portal, there are also some other peripheral matters that we have to take into account, such as the 'recruitment flow' or the onboarding process. How do we bring in freelancers and how can we optimize that process? But how do we at the same time ensure that no fraud can be committed?

Every month we get more than 175,000 visitors to our recruitment websites and we try to convert them into actual working freelancers. Ultimately, 5,000 freelancers remain. That is a conversion percentage of 2.8%, what could we do to up this?

However, we also want to know which channels convert the best, so we work with references and other parameters that we have to log and store for the marketing department to analyze.

This tooling is now also incorporated in the monolith, but we think it would come into its own if we split it off into a separate service. What do you think?