Onsite — From Paper Logs to Real-Time Financial Visibility

The Rest of the System

Every project got its own Dashboard — attendance, material, labour cost, party details, transactions, and project health in one screen. Attendance gave workers visibility into their own daily earnings, reducing payment disputes. The Material Log digitized the paper register; Transactions became a single ledger for money in and out across every party. Parties & Library, Tasks, Photos & Documents, and Reports rounded out the day-to-day tooling.

Company Profile — a public, shareable profile in the spirit of an Upwork or Fiverr profile — was my idea, greenlit by the founders, and became one of the four ground-up modules. Estimations let owners build quotations and track them from lead to acceptance, with clients commenting directly on line items. Access & Roles and Company Analytics gave owners controlled, company-level visibility across all projects.

Impact

BOQ feature usage rose 30%+ and estimation generation rose 60%+ after the redesign, with founders reporting a meaningful drop in manual invoice work. Onsite holds a 4.5 rating on Google Play, and post-redesign reviews pointed at exactly what the project set out to fix — usability and trust in the numbers.

“Our finance team now uses the web app daily without needing support.” “I can finally see what’s happening across projects without calling my site supervisors.”

Reflection

Working without a dedicated research team meant founders’ domain knowledge did the work user interviews usually would — enough to move fast, though I’d still want real supervisor and owner interviews if I revisited this. What I’m most confident about is the progress-per-location decision: the slower, more expensive version to build, and the one that didn’t break the first time a project got messy. The product has kept evolving on top of that same core structure — the best evidence I have that the foundation held.