01 / HR & payroll

EazyHR

A multi-tenant HR and payroll platform where every employee runs on one WhatsApp contact and the employer runs on a web dashboard.

Year
2024–25
Status
Archived in 2026. The platform is no longer maintained.
The EazyHR employer dashboard: today's priorities, attendance, headcount, compliance and leave at a glance.

The problem, stated properly

An HR app that employees have to install is an HR app most employees never open. Clocking in should take one message. So attendance, leave requests, payslips and HR queries all run through a chat thread people already have open, and the dashboard exists for the person who actually needs a dashboard: the employer.

Compliance here is specific to South Africa: SARS tax tables, UIF, overtime at 1.5× and 2×, and the Basic Conditions of Employment Act. A generic payroll engine would have been faster to build and useless to the customer.

The rule that shaped it

Any common action, in three taps or fewer.

Employee management, leave and attendance on the employer side were redesigned around that limit. Multi-tenancy is enforced in Postgres with row-level security rather than in application code, so a missing WHERE clause is a failed query rather than a data leak.

The EazyHR WhatsApp menu: clock in, leave, profile, attendance, roster, payslip, ask Summer.
The employee side: a numbered menu in WhatsApp. Clock in is one message.
The labour inspector audit trail: documents required for a Department of Labour review, with completion.
The labour audit: every document a Department of Labour inspection asks for, tracked to completion.
The EazyHR marketing page with the WhatsApp thread beside the headline.
The public site. Card required, thirty days free, cancel anytime.

What it is built from

  • React + Vite
  • Express on Vercel functions
  • Supabase Postgres with row-level security
  • Twilio WhatsApp Business API
  • Paystack
  • Google Gemini

Known limits

Stated plainly, because a client should know what they have.

  • Archived. Not accepting new tenants.

Need something like this to run on?

A thirty-minute call, then a written scope within five business days. No obligation either way.

Start a project
Call
30 minutes
Scope
5 business days
Build
Weeks, in the open