A GPS Time Clock App That Made Small-Business Payroll Defensible

Small businesses were running payroll on trust and transcription, with managers assembling hours by hand every cycle. Geofenced punches now work offline and arrive as QuickBooks-ready data.

Start your project

The build

WagePunch is an employee time clock and workforce platform aimed at small and growing businesses, published by AppSoftUS.

Aipxperts built it over roughly eighteen months: a NestJS backend, two React applications for managers and employees, and mobile clock-in with GPS and geofencing. The commercial idea behind it was narrow and deliberate. Give small teams the accountability features that normally sit inside expensive enterprise workforce suites, at a price a ten-person business will actually pay.

The problem

The businesses WagePunch targets were running payroll on trust and transcription. Managers chased paper timesheets and spreadsheets, had no live view of who was actually on site, and spent hours each cycle assembling payroll data by hand. The problems compound in a specific order:

Hours were self-reported, so there was no evidence behind a disputed shift.

Nobody could see the workforce in real time, so absences surfaced late.

Payroll preparation was manual re-entry, which is both slow and where errors enter.

The alternatives that solved this properly were priced for enterprises, not for a business with fifteen people.

There was also a build constraint that shaped everything: an existing product and an existing customer base already had data in a legacy database. This was not a greenfield project pretending to be one.

What we built

We built the platform around a single principle. A punch is only useful if it carries evidence, and payroll data is only useful if it arrives somewhere payroll actually happens.

Mobile clock-in that works offline

Employees punch from their phone even without a connection. Punches queue locally in SQLite on the device and sync when it reconnects, so the record survives the gap. Field and site-based work does not reliably have signal, and a time clock that fails without it is not a time clock.

GPS and geofence verification

Each punch carries location evidence, which turns a self-reported hour into a defensible one. This is the feature that makes the rest of the payroll chain trustworthy.

Manager workforce view

A live picture of who is on site, who is late and who has not appeared, in one React application built for the person running the shift. Dashboard counts update over Server-Sent Events rather than being refreshed by hand.

Timesheets, overtime and time-off

Automatic timesheet assembly with overtime calculation, plus PTO requests and manager approval flows, so the exceptions live in the same system as the hours.

Expense capture with receipts

Expenses recorded against the same employee record, with receipt capture on the phone.

QuickBooks Online integration

Payroll-ready data flowing directly into QuickBooks Online, removing the re-entry step that caused most of the original errors.

Separate admin application

A third React build for platform administration, kept apart from the manager and employee experiences because the three roles want genuinely different screens.

The outcome

The pricing point is the commercial result, not a feature note. Verified, geofenced time tracking with payroll integration is normally an enterprise purchase. Delivering it at a small-business price is what the product is for.

Before
managers chased paper timesheets and spreadsheets, had no real-time view of who was on site, and spent hours preparing payroll data by hand, often while paying for software priced well above what a small business needs.
After
employees clock in from their phone even offline, managers see the whole workforce at a glance with GPS and geofence accountability, and payroll-ready data flows into QuickBooks at fifteen to twenty dollars per user per month rather than enterprise pricing.

Tools and Technologies

NestJS
TypeScript
React 18
Flutter
MySQL
Redis
Bull queues
SQLite offline queue
Server-Sent Events
Firebase
Sentry
QuickBooks Online

Planning something similar?

If your hours are self-reported and your payroll is retyped, both problems have the same fix.

Start the conversation