Skip to content

How a small transport startup replaced spreadsheets with a recruitment system

A France-based transport startup with seven employees started by tracking candidates in Google Sheets.

As the business grew, that approach no longer gave the team a clear, structured view of job offers and candidates. This page explains the practical lessons from that transition and gives a checklist for judging whether a similar move makes sense for your own team.

Starting point: a spreadsheet that had reached its limit

Truckrs connects freelancers with the transport industry. It was co-founded by Pierre-Arnaud with two partners and, at the time described, operated with a small team of seven people. Like many early-stage businesses, it first kept its candidate database in Google Sheets.

That worked while volumes were low. As hiring activity increased, the team needed a more structured, technology-led way to manage roles and candidates. The search that followed was for a combined applicant tracking system and customer relationship management solution, rather than another spreadsheet or a disconnected tool.

Why the team chose a combined ATS and CRM

The team discovered the platform through a recommendation from an existing client, Avizio, whose co-founder Henry suggested it. Peer recommendation mattered because the team could hear how the system worked in a comparable recruitment operation, not just from a product description.

What stood out during evaluation was the combination of ATS and CRM functions in one interface. For a small team, that combination is the key distinction to test: one place to track a vacancy, the people associated with it, and the relationship history around each candidate, instead of splitting that information across tools.

What changed in day-to-day work

Once jobs were imported into the system, including through third-party services, the team gained a dedicated view of each job offer. That structure is what allowed the candidate database to expand rapidly, because new roles and candidates could be organised by vacancy rather than added to a single sheet.

Use this as a practical example when assessing your own data: map one current vacancy end to end. Note where candidate details live, where job details live, where follow-up is recorded, and how long it takes to answer a simple question such as which candidates are attached to a particular role. If those answers require searching several files, a structured system is likely to save time even before any growth in revenue is considered.

Reported outcomes to confirm before publication

The reported outcomes were a tenfold increase in revenue year on year, time savings of around 20 to 50 percent, and an increase of almost 1000 percent in the candidate database. Treat these as illustrative figures rather than verified results: before relying on any of them, establish the measurement period, the starting baseline and the calculation method, and confirm each number against your own records. A worked approach is to record revenue, hours spent on database work and total candidate records at the start of a period, then repeat the same measurements after the change so any improvement can be traced to a defined cause rather than a headline claim. The useful lesson does not depend on any single headline number. A clearer structure for jobs and candidates made it easier to handle more activity with the same small team, and the time saved could be redirected to recruitment work rather than database maintenance.

Decision checklist for a similar move

Use this checklist before deciding to replace a spreadsheet or add a new recruitment platform:

  • Can vacancies and candidates be viewed together, with a clear view per job offer?
  • Are ATS and CRM functions combined, so candidate history and relationship notes stay with the record?
  • Can existing jobs and candidate data be imported, including through third-party services?
  • Is the interface simple enough for a small team to use consistently without specialist training?
  • Can you measure the baseline first, including time spent on database work, database size and revenue, so any later improvement is verifiable?
  • Has a comparable team recommended the system from direct experience, and can you speak to them?

If several answers are no, the case pattern suggests that a structured system may be worth evaluating. If your volumes are still low and one sheet answers every question quickly, staying with a spreadsheet may be the simpler choice.

Frequently asked questions

When does a spreadsheet stop being enough for recruitment?

A spreadsheet can work for a very small, early database, but it becomes harder to organise roles, candidates and follow-up as volume grows. The case pattern here is moving to a dedicated system when growth makes that manual approach limiting.

What should a small recruitment team check in an ATS and CRM?

Check whether applicant tracking and relationship management are combined, whether the interface is easy for a small team to adopt, and whether jobs and candidate records can be viewed together rather than in separate sheets.