SiteSphere
Construction timesheet and payroll, built for the EBA.
A multi-tenant timesheet, payroll and invoicing platform for Australian electrical contractors working under enterprise agreements: web, iOS, Android and API, live in production with its launch customer's real crews.
| Owner | SiteSphere Pty Ltd |
| Sector | Construction and payroll |
| Scope | Web app, iOS and Android apps, API, admin and client portals |
| Stack | Next.js, Expo, Fastify, Supabase, Claude + Gemini, Fly.io |
| Status | Live: sitesphere.com.au, App Store and Google Play |
| Timeline | Around four and a half months to production |
The brief
Australian electrical contractors run payroll under enterprise agreements that generic timesheet apps simply do not understand: RDO accruals, six allowance regimes, site allowances scaled by project value, travel schemes, inclement weather rules. The job was to build software where the agreement itself is first-class data, launched alongside T1 Electrical Solutions in Melbourne.
What we built
Workers submit time from their phones. Individual timesheets collate automatically into one crew sheet per site per day, and the person who approves it is the client's own on-site representative, over an SMS magic link with no app and no account. Admins take approved time through payroll and invoicing. Six roles, each with its own surface, across web, mobile and a client portal.
- Pay engine models the enterprise agreement clause by clause, with a calculation trail from every dollar back to its clause
- AI agreement ingestion: upload the EBA as a PDF and the platform extracts pay tables, allowances and rules section by section for human review
- Offline-first mobile: a durable sync queue and on-device geofence math, so a worker with no signal can still start a compliant timesheet
- Pay privacy by construction: monetary fields are stripped from every payload that reaches workers, supervisors or clients
Engineering that holds up
Offline approval is handled honestly: a supervisor signing off without signal attaches a fingerprint of exactly what they approved, and if the sheet changed before the sync landed, the server refuses the stale approval and routes it for re-review instead of silently applying it. The platform runs 92 database tables under row-level security, ships type-checked from database to mobile, and deploys through a gated pipeline with automatic rollback.
In production
SiteSphere cut over to production within two months of the first commit and both mobile apps are published in the Australian app stores. The launch customer runs real projects on it today, and the support loop is direct: production issues have been reproduced, fixed and shipped same-day. This is the lab model working at full depth: a company, a product and its operations, built end to end.