Recruitment ATS Pro (Pipeline + Portal)

We build it as a proper Frappe app (its own module, installed on your bench with bench get-app / bench install-app) that extends the native Recruitment doctypes rather than replacing them. Custom DocTypes such as ATS Pipeline, ATS Stage, Candidate Application, Interview Slot and Interview Scorecard sit alongside Job Applicant, so nothing you already report on breaks. Stage transitions and SLA timers are enforced through hooks.py doc events (on_update, validate, after_insert) and server scripts, so a candidate can never skip a required stage or a rejection can never fire without a reason code. The kanban board and inline scorecards are driven by client scripts and whitelisted methods (@frappe.whitelist()) called over the Frappe REST API, so the UI stays fast and the business logic stays server-side and auditable.

The candidate-facing side is a branded careers portal built on Frappe's website/portal layer: public Job Opening web pages under your own route (for example /careers), an application form that creates a Candidate Application and attaches the CV as a File, and a token-based status page so applicants can track their progress without an ERPNext login. Resume parsing runs as a background job on submit — extracting name, email, phone, skills and experience into the candidate record and de-duplicating against your existing database. Interview scheduling reads interviewer availability, writes Event records to their calendars, sends templated emails, and collects structured scorecards that roll up to a weighted hiring recommendation. When a candidate is selected, the app generates an offer letter from a Jinja print format, routes it for internal approval via the workflow engine, and sends it for e-signature; countersigned offers post back as an approved Job Offer. A scheduler_events job nudges stale candidates and flags SLA breaches on the recruiter dashboard.

Because this is build-to-order, we scope your exact pipeline stages, roles and portal branding first, then build against your requirements on ERPNext/Frappe v15 or v16. You get the installable source for your version, a UAT pass on a staging bench with a rollback plan, and a git repository handover — not a black box. Typical delivery is 2–4 weeks from confirmed scope, and every ECOSIRE build includes a post-go-live support window so you are not left alone the first time you run a real hiring cycle through it.