Back office · payroll, leave & billing

The last day of the month — just another Friday.

Payroll runs from compensation records you set once. Payslips render as branded PDFs — your logo, nobody else's. Leave keeps its own balances and calendar. Stripe bills your clients on schedule. You check in. You don't carry it.

The payday spreadsheet ritualLeave requests lost in chatReconciliation eating your nights
A tidy desk in early morning light: closed laptop, a neat stack of pay envelopes, a small plant
It's the 30th. The spreadsheet is open, the calculator is out, and if I get one cell wrong, someone's rent is late.

every staffing-company owner, on payroll night

The month-end ritual

Somewhere along the way, you became the ops department.

Payday means an export, a formula check, and a prayer. Leave requests arrive as chat messages and vanish under newer ones. Invoices get reconciled after dinner, line by line. And the standard fix — a second ops hire — costs money the growth hasn't earned yet.

What you get

Built in. Not bolted on.

Payroll from the record

Compensation records drive every pay run. Prorated payslips render as branded PDFs — your logo on the header, not a vendor's. A mid-month start is math the system does, not you.

Bonuses with a paper trail

A bonus gets proposed, approved, and logged before it touches a payment. No hallway promises that two people remember differently.

Bank details, gated

Bank-account and KYC verification are built in. Account numbers sit behind a gated reveal — seen deliberately, never in passing.

Leave that keeps its own books

Balances, leave types, and company holidays tracked per person. Approval modes set per department. A shared calendar shows who's out — and self-approval is blocked, full stop.

Billing that sends itself

Stripe runs client subscriptions and monthly B2B invoicing. The invoice goes out whether or not you remembered it was the first.

An audit log under everything

Every salary change, leave decision, and payment lands in the log — who, what, when. Questions get read, not reconstructed.

0
roles, scoped to the job

Role-based access means payroll sees payroll and recruiters see recruiting. Nobody browses salaries by accident.

0
self-approved leave requests

Self-approval is blocked outright. Every request routes to someone else — even the founder's.

0
log behind every change

Salary, leave, and payment changes each land in an audit log. The close of the month is a read, not a hunt.

Receipts

Straight from the live platform.

Captured from the production operation this white-label runs on — names anonymized, everything else is the product.

admin · payrollLive
Payroll console: compensation, bonuses, payslips, verification
  1. 01Flags gaps before payday
Payroll · compensation records drive every pay run
admin · leaveLive
Leave management with balances, approvals and calendar
Leave · the books keep themselves
admin · paymentsLive
Client payment plans with Stripe-backed collection
Billing · plans, progress and Stripe collection
admin · hiringLive
Internal hiring pipeline kanban
Hiring your own team — the built-in ATS
How it runs

Set it up once. Then it's just how things work.

01

Set the record once

Each person gets a compensation record — salary, bank account, KYC verification. Bank details stay behind the gated reveal from day one.

02

Let the month run

Leave requests route by department to the right approver. Balances update, the shared calendar fills in, and company holidays are already loaded.

03

Run payday from the record

Payroll draws on the records. Prorated payslips render as branded PDFs. Bonuses clear the approval flow before a payment moves.

04

Close without the hunt

Stripe sends the client subscriptions and monthly B2B invoices. Everything that changed is already in the audit log.

The back office you stop thinking about.

Records set once. Payslips that render themselves under your brand. Leave that keeps its own calendar. Invoices that go out on schedule. The month ends, the log holds the whole story, and nobody stayed late to make it true. The second ops hire can wait. It just runs.