The average company runs 6.17 HR systems across one employee lifecycle. Emplora collapses that into a single employee record, wraps it in a copilot that finishes the work rather than suggesting it, and publishes the price — for the 50–500 companies that have outgrown BambooHR and can't justify Rippling.
It is short on HR systems people actually use. 82% of deployments report adoption challenges while 45% of HR leaders lose over half their week to admin — which means the category competes on time-to-value and interface quality, not on module count. Everyone already has the modules.
Plot the eight platforms that matter on depth against self-serve time-to-value and one quadrant is empty. Darwinbox has enterprise depth but needs a sales cycle. BambooHR has the ease but hits a ceiling. Nobody occupies both corners at once.
That gap has a name and a size: the 50–500 graduation gap, where companies resolve their needs by accumulating point solutions. Emplora attacks it with four wedges — one record, agents that close the loop, mobile parity, and a published all-in price.
6.17 providers per employee lifecycle, and 77% of organisations splitting people data across multiple HCM databases. The consequence isn't inefficiency — it's blindness. Data that lives apart cannot be correlated, so risk only surfaces after it has cost money.
What ships in the SMB tier is a conversational layer glued to a help-centre index. The shift buyers have named explicitly is that suggestions do not reduce workload — execution does. Nobody in this tier ships agents that complete a task end to end.
Managers are the largest user population and the worst served — which is precisely where the 82% adoption failure concentrates. An episodic user who relearns the interface every time is not a training problem; it is a structural design failure.
The most consistent grievance across every review source. Sticker prices understate true cost by 30–50% once add-ons land, and BambooHR carries a $250/month floor. In a category built on quote-gating, a published all-in price is a marketing asset, not just a policy.
05 — User Stories
Drawn from five personas — two of whom sign the contract and three of whom live in the product. Every story traces to a shipped module.
06 — Competitor Analysis
Parity on the table stakes is assumed. The rows that decide anything are the bottom five.
| Capability | BambooHR | Rippling | Darwinbox | Zoho | Emplora |
|---|---|---|---|---|---|
| Core HRIS & directory | ✓ | ✓ | ✓ | ✓ | ✓ |
| Integrated payroll | Add-on | ✓ | ✓ | Add-on | ✓ |
| People analytics | Basic | ✓ | ✓ | Basic | Predictive |
| Attrition risk scoring | — | — | ✓ | — | Explainable |
| Agentic task execution | — | Partial | Partial | — | Core |
| Natural-language command bar | — | — | — | — | ✓ |
| Mobile capability parity | — | — | ✓ | — | ✓ |
| Published all-in price | — | — | — | ✓ | ✓ |
| Seat floor | $250/mo | Yes | Yes | None | None |
Five decisions, each one a fork where the conventional answer was available and cheaper. Together they are the product.
org_id at the database, salary and engagement are stripped server-side before
serialisation, and one isomorphic permission matrix is imported by both the API that enforces and the
UI that hides./hr, /manager,
/me. Explicit, easy to reason about, and each one optimisable in isolation./dashboard route with three compositions. HR sees org
metrics, status and risk; a manager sees team to-dos, approvals and pulse; an employee sees their
balance, tasks and team.Extracted from Figma through the MCP server
rather than transcribed by eye, and built on Untitled UI primitives. The values below are the real tokens
in globals.css, consumed through Tailwind v4's theme layer.
Accessibility baseline: body text meets WCAG AA, focus is visible on every interactive element, status is never encoded by colour alone, charts expose an accessible table equivalent, and ⌘K is reachable from anywhere with Esc closing every overlay.
Emplora is a design and engineering concept running on demo data, so these are the success metrics the product was designed against — each with the baseline it is measured from — rather than adoption results from a customer base.
Baseline 6.17. The single record makes this structural rather than aspirational.
Baseline over 50%. Attacked by killing reconciliation and having agents close loops.
Baseline ~15%. The zero-recall ⌘K path and pre-drafted reviews target exactly this number.
Baseline zero. The signal exists in the data 60–90 days out; nothing in this tier surfaces it.
Portfolio work is usually presented as finished. This is more useful — and more honest — as a ledger.
Key Learnings
"The research kept pointing at the same thing from different angles: this category is not short on features, it is short on products people will open. That reframed the whole project. The interesting work wasn't designing fourteen modules — it was deciding that the score has to show its factors, that scope belongs in the database, that the assistant's output has to arrive as a draft, and that the price goes on the landing page. None of those are screens. All of them are the reason the screens work. I also learned to distrust numbers that look fine: the salary-band bug returned a perfectly reasonable 50% for everyone, and it took asking why nothing was ever flagged to notice the signal had been silently deleted."
Rupesh Chavan — Product Design & Build
