The one-paragraph answer
If you're already running payroll + attendance + leave on Keka, Keka Hire is the obvious add-on. One bill, one vendor, one login. The hiring module isn't class-leading on AI scoring, but it's solid on basic ATS + structured workflow.
If your problem is hiring quality, not HRMS, Lucida. We don't do payroll, attendance, leave, performance, or expense — and we never will. We do one thing: AI scoring with cited evidence, candidate feedback for every applicant, and a calibration loop that gets sharper with every hire.
Feature comparison
| Lucida | Keka Hire | |
|---|---|---|
| Price (entry) | ₹2,499 / month, single admin | ~₹1,250 / seat / mo (bundled) |
| HRMS bundle (payroll · attendance · leave · perf) | No, never will | Yes, the actual reason to use Keka |
| AI scoring with cited evidence | Per dimension, every candidate | Light AI features, not the core |
| JD clarification pre-pass | Asks before drafting | Not present |
| Candidate feedback report | Automatic, every applicant | Manual / templated |
| Outcome → rubric calibration | 90-day survey · /admin/insights | Static |
| Audit trail (DPDPA / AEDT / EU AI Act) | Per-row, every score, Save-as-PDF | HRMS-grade compliance, not AI-decision-specific |
| India-native | DPDPA-by-default · GST invoice · Tier-2/3 channels | India-founded, strong on Indian compliance |
| Multi-user / pipeline stages | Single admin, no stages beyond shortlist | Full pipeline + recruiter collaboration |
| Best fit | Founder screening candidates, wants better hires | 20-200 person team wanting one HRMS for everything |
Where Keka wins (and we mean it)
- The HRMS bundle economics. If you need payroll + attendance + leave + performance, running them in separate tools costs more than the entire Keka bundle. Hard to compete with vertical integration.
- Pipeline + recruiter collaboration. If multiple people need to comment on candidates, move them through stages, assign owners — Keka has the workflow. Lucida is single-admin.
- Already in your stack. Switching cost is real. If Keka HRMS is running, Keka Hire is the path of least resistance.
Where Lucida wins
- Hiring is the product, not a module. Lucida exists for one thing: making the hire-no-hire decision better. Every line of code is in service of that. Keka Hire is one tab in a sprawling HRMS — gets attention proportional to how it ranks against payroll bugs.
- Cited-evidence scoring. Every score in Lucida quotes the résumé or interview answer that produced it. Keka's AI summaries don't carry the same defensibility — you trust the rank or you don't.
- The candidate-feedback report. Every applicant — even rejected — gets a private URL with their score breakdown. Keka does not write these; a personalised report for every applicant only works when AI is doing the writing, not a human recruiter.
- The calibration loop. Over time, Lucida tells you "your Mentorship dimension didn't predict hires; consider reweighting". Keka shows you funnel metrics; Lucida shows you whether your own judgment is working.
The pragmatic move
Use both. Run Keka for HRMS — payroll, attendance, leave, performance reviews. Use Lucida for the scoring + feedback layer Keka Hire isn't built for. Lucida's bulk-paste import handles résumés from Keka exports; the embed widget runs on your existing Keka careers page if you have one.
Most of our customers who came from Keka kept Keka for HR and added Lucida for scoring. Different jobs, different products. We didn't try to compete with the bundle.