"Why does your CRM do payroll?" is the question we get most often in demos, usually with a raised eyebrow. It is a fair question — no legacy CRM does — and the answer says a lot about who Autometa CRM is actually for. This post explains the reasoning, then walks through what the People, HR & Operations suite ships: attendance, shifts, leave, payroll and the permission system that makes it safe to keep beside your sales data.
The hidden cost of a second system of record
For a mid-sized team, "we use a separate HR tool" really means: another subscription, another login, another admin, and a growing pile of duplicated records — the same people existing twice, drifting apart in both places. Commission needs sales data joined to payroll data; capacity planning needs pipeline joined to leave calendars; and every month someone reconciles the two systems by hand.
For companies under a few hundred people, we think the split is historical accident, not architecture. A CRM is already the system of record for how work happens. Extending it to the people doing the work removes the gap instead of bridging it — one directory, one permission model, one place where a rep’s deals, shifts and payslips coexist without a sync job.
Attendance that knows where the team is
Attendance in Autometa CRM is built for teams that do not all sit in one office. Geolocation check-ins verify where a check-in happened — the field rep at the client site, the support agent at home — while shift rotations, break tracking and work-from-home policy enforcement handle the schedule side. Managers see coverage in real time; the timesheet builds itself as a by-product of people just clocking in.
Leave without the spreadsheet ping-pong
Leave management replaces the email-thread-plus-spreadsheet ritual most small companies never admit to. Define custom leave types with their own accrual rules, let balances track themselves, and route requests through multi-tier manager approvals — the team lead signs off, then HR, automatically, in order. The employee sees their balance before they ask; the manager sees team coverage before they answer. Nobody updates a spreadsheet.
Payroll as an output, not a monthly project
Because attendance, shifts and leave already live in the system, payroll stops being a data-gathering project and becomes a computation. The configurable payroll engine applies allowances, tax deductions and bonuses on top of attendance-driven salary calculation, with per-employee overrides for the exceptions every real company has. Run it, review it, publish it.
Employees get a self-serve portal: view shift schedules, submit leave requests, download official PDF payslips — without messaging HR for any of it. The dozen small interruptions that make up an HR admin’s Tuesday simply stop arriving.
The permission system that makes this safe
Salary data next to sales data is only acceptable with serious access control, which is why the HR suite leans on the same granular RBAC as the rest of the CRM: field-level permissions, custom roles, team hierarchies and complete audit logs. A sales manager sees their team’s pipeline but not its payslips; an HR admin sees compensation but not deal notes; and every access is logged. The permission model is one system too — which means it is enforced everywhere, with no gaps where two products meet.
Who this is actually for
If you are a two-thousand-person enterprise with a dedicated HRIS team, keep your HRIS. The unified suite is for the companies in the middle: agencies running field teams, clinics and academies scheduling shifts, sales-led SMBs where the founder is also the HR department. For them, "why buy separate HR software?" is not a rhetorical question — it is a line item, an integration project and a monthly reconciliation they can simply delete.
One system of record for leads, people and operations was the founding idea of Autometa CRM, not a feature bolted on later. The HR suite is that idea taken seriously.