Recruitment and manpower agencies live and die by two numbers: time-to-fill and placement margin. Yet most agencies run those numbers across a spreadsheet of candidates, a separate CRM for clients, an email inbox for job orders, and an accountant who invoices placements weeks after the fact. Odoo's native Recruitment app was built for a company hiring its own staff — one hr.job maps to one internal vacancy, candidates become hr.applicant records funneled toward a single employee contract, and there is no concept of a paying client, a placement fee, a margin, or a candidate you place at multiple clients over a career. The moment you try to model "Client A ordered 12 welders, we sourced 40 candidates, placed 9, and now bill a 15% placement fee," native Odoo runs out of road.

This module reshapes Odoo into an agency operating system. We introduce first-class models for the agency's real objects: a candidate database (ecosire.candidate) with structured skills, certifications, availability windows, expected salary and document tracking; client job orders / requisitions (ecosire.job.order) linked to the client res.partner with required headcount, rate card and deadline; and a placement record (ecosire.placement) that binds one candidate to one job order with the contract terms, start date, and the fee or margin that placement earns. A Kanban matching pipeline sits between candidates and job orders — sourced, screened, shortlisted, client-interview, offer, placed — implemented as a state selection with a stage model so recruiters drag cards exactly like they do in native CRM. Computed fields (@api.depends) roll up fill rate per job order, days-to-fill, and gross margin per placement so managers see the health of the desk without exporting anything.

Technically it is a clean, upgrade-safe Odoo addon. Business rules live in the ORM (models.Model with validated fields, @api.constrains guards, and compute/store fields), not in fragile automations. Access is governed by ir.model.access.csv plus record rules so a recruiter sees only their own desk while a manager sees the branch, and overseas-manpower workflows (visa stage, medical, deployment) are modeled as extra pipeline stages rather than bolted-on notes. Placement billing is wired straight into Odoo Accounting: confirming a placement can generate the client invoice for the placement fee or the ongoing margin against the contract, so finance never re-keys anything. QWeb reports produce the candidate CV pack, the client shortlist sheet and the placement/commission statement on your letterhead. Everything is reachable over Odoo's XML-RPC / JSON-RPC API, so a job board or a WhatsApp intake bot can create candidates and job orders programmatically. Automated actions handle the tedious edges — flagging expiring candidate documents, nudging stalled job orders, and alerting when a placement's guarantee period is about to lapse.

Because every agency's desk, fee model and compliance rules differ, this is a build-to-order engagement, not a one-click install. We start from this proven blueprint, scope your exact stages, rate cards, fee structures and document requirements on a short call, then build, test and hand over a module tuned to how your agency actually works. Typical delivery is one working week from confirmed scope, targeting your Odoo version (17.0, 18.0 or 19.0) on Community or Enterprise. You receive the full source, a staging UAT, training, and a post-go-live support window — you own the code and the Git repository at the end.