Payroll a garment factory can release without holding its breath

Attendance and payroll for a 1,200-worker garment factory, where a wrong payslip is a line stopped on the floor. The concept is built around the release process: nothing reaches payday untested.

Concept project. Designed by OnTek to show how we would solve this problem; not work done for a client. The figures are the targets it was built against.

Product: Loomwage
Industry: Manufacturing
Year: 2026
Timeline: 10 weeks

What it is built to do

The targets the build was designed and tested against. A concept, so these are design targets rather than a client’s measured results.

12
Months replayed per release
Every change checked against a year of real paydays.
1
Click to roll back
A bad release undone in one step, before payday.
1,200
Payslips in Bangla
One per worker, on their own phone, before the money lands.

Thebrief

A garment factory pays 1,200 people on piece rates, overtime and attendance bonuses, from a spreadsheet one person understands. Each month someone is paid wrong, and it is found out on the floor.

The concept is a payroll system whose releases are as dependable as its maths: every rule written down, tested against past months, and shipped only when the tests say it is safe.

How we ran it

Each step was owned by one discipline, and every one of them worked from the same plan in the same team.

01
SaaS, MVP Development
The rules, written as code
Piece rates, overtime, attendance bonuses and deductions, each as a rule that can be read and tested, fed by the biometric attendance machines the factory already has.
02
SQA, Deployment
Tested against past paydays
Twelve past months of payroll replayed on every change, so a new rule that shifts anyone’s pay by a single taka is flagged before it ships. A staged release with a one-click rollback.
03
App Development
A payslip every worker can read
A payslip in Bangla on the worker’s phone, line by line, so a question is asked before payday instead of at the gate.