Not a list of features. A process that runs end to end.
HR work is not a set of screens; it is a year that repeats. Somebody is hired, onboarded,
paid every month, reviewed, and eventually leaves. Here is how each of those stages runs
when all of it lives in one place.
Plan & hireOnboardThe working monthPayGrowKnowPart ways
1
Before anyone joins
Decide the headcount, then go and fill it
Hiring starts as a budget decision and ends with somebody accepting. One thread runs through the middle, so nobody has to ask where a candidate got to — or whether the role was agreed in the first place.
Headcount that was actually agreed
Roles are opened against a plan, so “are we hiring more than we said” has an answer rather than an argument.
One pipeline, not five inboxes
Candidates, conversations and interview notes stay attached to the role they applied for.
An offer with a trail behind it
Who approved what, and when — without reconstructing it from a mail thread six weeks later.
What stops happening: No more spreadsheet of open roles that three people maintain and nobody trusts.
2
Acceptance to day one
Turn a yes into a colleague
The gap between “I accept” and the first morning is where most HR runs on memory and email. Closing it takes two things: knowing what to collect, and having somewhere ready for them to arrive.
Know what to collect, before you need it
The joining data, documents and identifiers, gathered once and in one place.
A portal waiting on day one
They sign in to their own balance, their own documents and the company feed — not to a welcome PDF.
Structure that mirrors yours
Department, designation, grade, location, shift and who they report to, set once and used everywhere.
What stops happening: No first week spent chasing a document by email while somebody waits to be paid.
3
Every day, every month
The month mostly runs itself
Attendance, leave, time and spending all arrive as small decisions. The job of the system is to put each one in front of the right person, with enough context that deciding takes seconds rather than a conversation.
Exceptions raised by the person who noticed
Missed sign-ins, corrections and days worked out of hours come from the employee — not from someone chasing.
One queue for everything waiting on you
Leave, time, expenses, corrections and requests, in one inbox, whatever they are about.
Balances people actually believe
Every movement traceable back to the policy that caused it, which is what stops the arguments.
What stops happening: No reconciliation week at month end, and no separate spreadsheet shadowing the system.
4
The part that must be right
Pay people, and be able to prove it
A run is computed, checked, then frozen. Out of the same numbers come a payslip a person can read, a register an accountant can use, and a file a bank will accept.
Rebuild a draft as often as you like
Fix something and compute again. Once finalised it is a record, and records do not quietly change.
Statutory rules that are yours
Rates, ceilings and thresholds are entered by you and dated, so last quarter keeps computing last quarter’s answer.
One run, three outputs
Payslips, the register and the payment instruction — all derived from the run, so they cannot disagree.
What stops happening: No parallel workbook that disagrees with the payslip somebody was handed.
5
Through the year
Reviews that start from evidence
Goals, feedback and recognition accumulate quietly through the year, so the conversation in March is about a record instead of whatever both people happen to remember.
Goals that stay current
Updated as work changes, rather than written the night before the review.
Feedback attached to the person
Not to a cycle — so it is still there next year, when it is worth more.
Recognition in the open
With a reason worth reading, and a finite monthly allowance so it keeps meaning something.
What stops happening: No review written from a blank page an hour before the meeting.
6
What the numbers say
What is happening, and what changed
Two different questions, answered in two different places. One is about today: who is off, what is waiting, where the queue is. The other is about the year: how the shape and cost of the company moved.
Today, at a glance
The operational picture a Monday morning needs, with every number linking to the queue behind it.
The year, in shape
Joiners, leavers, attrition and the make-up of the team across any window you choose.
Derived, never stored
Every figure is computed from the underlying records, so correcting the record corrects the report.
What stops happening: No board pack assembled by hand from four exports the night before.
7
The last mile
Leaving, done properly
Somebody works a notice period, hands over, gets cleared by three different teams, is paid what they are owed — and only then does their access stop. Each of those is a record, because each is something people ask about afterwards.
A clearance list with teeth
The items that must happen before money moves are marked as such, and the system enforces it rather than reminding you.
A settlement that shows its working
What can be derived is derived; what a person decided is typed in with a note saying why.
Access ends, history does not
The login stops working the same day. The record stays intact for audit, because it has to.
What stops happening: No “did anyone ever collect the laptop” three weeks after the leaving drinks.
Underneath all of it
The parts nobody asks for until the day they need them.
Every stage above sits on the same foundations. These are not features you switch on; they are how the thing is built.
A boundary per company
Every record is scoped to your organisation at the data layer — by construction, not by a filter somebody could forget.
Roles that mean something
Employee, manager, HR and owner each see exactly what their role allows, and your admins decide where those lines fall.
An audit trail underneath
State-changing admin actions are recorded with who did it, when, and what changed — including what it changed from.
Modules on when you want them
Start with what you need today. Everything else waits, switched off, until somebody asks for it.
Your own email identity
Connect your own mail server so invitations and notifications reach your people from your domain, in your words.
One inbox for approvals
Whatever is waiting on somebody — leave, time, expenses, proofs, corrections — arrives in the same place.
Straight answers
Three things this product will not do
Each one is a decision with a reason behind it. You should know them before you buy, not after.
By design
We do not ship tax rates
Every rate, ceiling, band and limit is entered by you, from your own compliance advice, and dated. Software that shipped rates would go quietly wrong the year they changed, in a way nobody would notice until it mattered.
By design
We do not issue Form 16
That comes from the tax authority’s own system, against tax actually deposited there. We give your team the statement of what was withheld and say plainly on the screen that it is the worksheet, not the certificate.
By design
We do not switch things on for you
New capability arrives disabled. Nothing appears in your people’s navigation because we shipped something — an administrator turns it on when the team is ready for it.
See the whole year on your own data.
Create your portal, run the setup wizard and invite your team. Start with the stage that hurts most and add the rest when you are ready.
