Challenge
The Tuesday morning mess
What problem existed?
Staffing teams live in parallel worlds: Naukri Resdex for search, PDF folders for CVs, WhatsApp for candidate pings, spreadsheets for tracking, and a different tool again for invoices. There is no shared state. Managers cannot see what recruiters actually did. Sales cannot invoice against a clean candidate or client trail. Every handoff loses context.
- ▸CVs trapped in email and desktop folders
- ▸No safe way to push Resdex shortlists into an internal CRM
- ▸Activity and revenue invisible to leadership in real time
- ▸Role boundaries unclear — everyone has every button, or none
What we built
One ops layer, real roles, real pipeline
What PragmaLabs created
NestOS is built as the daily workspace for recruitment operators — not a marketing brochure. Recruiters source and save. Managers review. Sales invoices. Admins govern. The system is designed around how HummingBrains / RTS-style teams actually close the day.
Talent hub with OCR
Drop bulk PDFs; text-layer CVs parse on day one, scanned docs path through Azure Document Intelligence when configured.
Naukri Resdex bridge
Chrome helper captures what recruiters already see on Resdex/demo pages and ships structured candidates into NestOS — no public Naukri API required.
Lifecycle beyond hire
WhatsApp and email from the candidate drawer, document verification hooks, invoices under Revenue, and end-of-day activity so ops is measurable.
How it works
How we phased delivery
Simple workflow — how delivery was sequenced
- 1
Ops spine
Auth, JWT cookies, RBAC (admin / manager / recruiter / sales), SQLite store, and the shell app recruiters land in every day.
- 2
Talent intake
Bulk PDF upload, model parse endpoints, candidate drawers, and sample data for trial workshops.
- 3
Sourcing extension
Unpacked Chrome extension, extension guide, demo Resdex flow, auto-load into Find on Naukri → Save / Save all.
- 4
Revenue & rhythm
Invoices for gated roles, activity logging, end-of-day, trial ops materials for stakeholder demos.
In detail
Key parts of the product
Role-based access
Recruiters source; sales invoices; managers and admins see the full board without shared passwords.
Bulk PDF → candidates
Talent Hub accepts stacks of CVs and turns them into working records with OCR assist.
Naukri helper
Chrome path that respects how recruiters already work on Resdex instead of inventing a fake API.
Outreach from the record
WhatsApp and email launch from the candidate context so conversations stay attached to the person.
Revenue loop
Create invoices from the ops layer so delivery and billing share one truth.
End-of-day discipline
Activity log and EOD ritual give managers a pulse without spreadsheet chasing.
Technology
Technical stack
NestOS ships as a focused stack: Node server, SQLite for portable trial deploys, JWT session cookie, optional Azure DI and Resend. The Chrome extension is a first-class citizen of the product, not an afterthought. Model parse is exposed as explicit API surfaces so hosting and OCR vendors can be swapped without rewriting the recruiter UX.
- Node / Express
- SQLite
- Chrome extension
- Azure Document Intelligence
- Resend
- JWT RBAC
Result
What improved
- Recruiters can move Resdex shortlists into NestOS without retyping profiles.
- Managers get a role-correct view of talent, activity, and revenue.
- Trial accounts demonstrate the full staffing day, not a slide deck.
- Ops can run on local SQLite for demos and expand hosting without a rewrite.
For a staffing leadership team, NestOS replaces ‘which tool has the CV?’ with a single workspace. The win is not a feature list — it is recruiters finishing source-and-save without switching six tabs, and managers seeing work product without a status call.
“If Resdex is where search happens, NestOS is where work survives the handoff.”
Want something like NestOS for your business?
Book a free discovery call or a deeper working session — we start from your business problem, not a template.