How a Surabaya Company Halved Time-to-Hire with Odoo Recruitment

A growing company in Surabaya — a logistics and distribution business expanding fast enough to be hiring most months — kept losing good candidates. Not to better offers exactly, but to time: by the point they got around to interviewing a strong applicant, that person had often already accepted a job elsewhere. Their hiring was slow, and in a competitive market, slow loses.

Hiring out of an inbox

Applications arrived by email and, increasingly, WhatsApp. The HR coordinator collected them, but with hiring happening across several roles at once and her juggling other duties, CVs piled up. A promising applicant might wait a week before anyone reviewed their CV, another few days before a screening call was arranged, and more delay before the hiring manager gave feedback — which itself arrived as scattered replies in an email thread.

The hiring managers, meanwhile, had no shared view. Each saw the candidates forwarded to them, gave opinions over chat, and nobody had a single picture of where each candidate stood. Candidates fell through the cracks, got contacted twice, or simply went cold while the process meandered. In a fast market, the delay was the killer.

What changed

They implemented Odoo Recruitment.

A careers page feeding the pipeline. Job openings went onto their website, and applications now flowed in directly as candidate records. The inbox pile disappeared — every applicant landed in the right role’s pipeline automatically.

One shared pipeline per role. Hiring managers and HR shared a single view of every candidate and their stage. The “where are we with that applicant?” confusion ended, because the answer was on the board.

Feedback on the record. Interview feedback and screening notes were recorded on each candidate, so decisions were made from a shared, complete picture rather than scattered chat opinions. This alone sped up decisions noticeably.

Visible next actions. The pipeline showed who was waiting on a next step, so candidates stopped going cold through neglect. HR could see at a glance which strong applicants needed prompt action.

The result

Time-to-hire roughly halved. The company was not hiring different candidates or lowering its bar; it was simply moving candidates through the process fast enough to actually land the good ones before competitors did. Strong applicants who would previously have accepted another offer during the delay were now getting interviewed and offered while still available.

There was a quieter benefit too: the hiring managers found the process less painful. Instead of forwarded CVs and chasing feedback over chat, they had a clear pipeline and a shared view. Hiring stopped being a frustrating side-chore and became a manageable, visible process.

Why it worked

The company did not have a candidate-quality problem; it had a speed problem, and the speed problem came from inbox-based chaos and lack of a shared view. Candidates were lost to delay, and the delay came from CVs piling up, no clear next actions, and feedback scattered across chats. Putting every applicant into a visible, shared pipeline removed all three sources of delay at once.

It is worth noting the careers-page integration mattered: capturing applications directly into the pipeline, rather than collecting them by email and entering them later, removed the very first source of delay — the gap between a candidate applying and anyone noticing.

If you are losing good candidates to slow, inbox-based hiring in a competitive market, the fix is usually speed and visibility, not more applicants. We are happy to look at how your hiring runs and show you where the time goes, in a free one-hour conversation.