The people
“My workers won't use software.”
They will — if it speaks their language, works in the shed's dead zone, and gives them something back. Most yard software fails here first: the best system in the world is worthless if the cutter won't touch it.
The mechanism: offline you can trust
Sheds have concrete walls and metal roofs; yards have dead zones. So the worker app never depends on signal: every tap is saved to the device instantly and queued. When connectivity returns, the queue drains in order — and an idempotency guarantee makes it structurally impossible for a double-tap or a replay to count the same cut twice.
The worker doesn’t take that on faith. A chip on his screen tells him, at a glance, whether his shift is safe:
- SyncedEverything is saved to the server.
- 3 syncingActions queued; sync in progress — keep working.
- 1 not syncedNeeds attention — listed plainly, with a retry button.
And because attendance ispayroll here, each day’s wage is frozen the moment it’s marked — pay history that can’t be quietly rewritten protects the worker and the owner alike. In a trade that runs on trust, the software should be the most trustworthy thing in the yard.
Seen in the product
A real product screenshot goes here: the real Hindi worker home — status toggle, My Work list, and the sync chip. We photograph the real thing or show nothing — no mock-ups, ever.
A real product screenshot goes here: a cut being logged — consumed area, slab rows, and no prices anywhere. We photograph the real thing or show nothing — no mock-ups, ever.
“Honestly — a gangsaw operator, on an app?”
He logs in with just a username his admin created — no email, no password to memorize. His screens are icons and numbers, in Hindi if he prefers. He enters what he cut; the math happens elsewhere; prices are hidden from him entirely. And the app pays him back: he sees his own attendance, his own earnings, and can request an advance from his phone. Adoption isn't a training problem — it's a respect problem, and this app was built respectfully.
Everything this covers
| Capability | What it does for the yard |
|---|---|
| Username-only login | No email, no self-signup — the admin creates access in a tap; the worker just types his name. |
| English / हिंदी | Every worker screen is fully bilingual, icon- and number-first, with the choice remembered. |
| The offline outbox | Work saves on the device and syncs when signal returns — oldest first, exactly once, never twice. |
| The sync chip | Green synced, amber syncing, red needs-attention — the worker always knows his shift is safe. |
| Task checklists | Assigned jobs as step-by-step lists, strictly in order, impossible to double-complete. |
| The cut screen | Consumed area and slab rows in; recovery, wastage, and the remnant computed — prices never shown. |
| Deliveries, forward-only | A driver sees only his own runs: In Transit, then Delivered. One tap closes the whole order. |
| My Pay | Own attendance calendar, earnings, advances, and net balance — transparency that ends pay disputes. |
| Wage snapshots | Each day's wage is frozen when attendance is marked. A later rate change never rewrites history. |
| Advance requests | Asked from the phone, approved by the admin, settled in the payroll — controlled, not chaotic. |
The honest part
The office side needs a connection to first load.Roadmap
Offline-first covers the worker's actions — cutting, tasks, deliveries — which is where signal actually dies. The admin app requires network to open its pages; full office-side offline is on the roadmap.
Decide on evidence, not on our words.
Weighing it against what you use today? See why generic ERPs lose the shop floor →