Where your time actually goes

Active-time measurement that reports sessions, average and longest session, all-time hours, which module you live in, and which customer or job took the most of your attention.

What it is

A quiet beacon measures active time — not a tab left open — and rolls it into per-session records with per-module and per-record breakdowns. The stat tiles then answer questions an owner cannot otherwise answer: how many sessions, how long the average one runs, the longest single stretch, total hours, the module with the most time in it, and the customer or job with the most time on it.

Also called: usage stats · time tracking in the app · which client took the most time · session stats

See it
Where your time actually goes
Won
43%
Avg cycle
13d
Pipeline
$633k
JanSep
The six stat tiles — Sessions, Avg session, Longest session, Time in platform, Most time in, Most time on — StatTiles in AchievementLadder.tsx. Sample data — no customer information appears here.
How it works
  1. 1A page_view is recorded whenever the active view changes, tagged with the canonical module id
  2. 2A heartbeat every 30 seconds counts only while the tab is visible AND the person has moved in the last two minutes
  3. 3Events batch and flush every 30 seconds, and on tab hide or unload via sendBeacon so the last slice is not lost
  4. 4One session id per browser tab, rotated after 30 minutes idle so a lunch break does not read as a 90-minute session
  5. 5Platform staff working inside a tenant are excluded — that is not the tenant using the product
  6. 6The record in focus is captured by NAME only, never by id
Why we built it

Owners buy software and then have no honest read on whether anyone uses it, and the usual measure — a tab left open on somebody's second monitor — reads as eight hours of work that never happened. Time is counted only while the tab is in front of the person and they have actually moved in the last couple of minutes, and a session ends after half an hour idle, so lunch does not become a ninety-minute stretch. What comes out is sessions, average and longest session, hours all in, the part of the app you live in, and which customer or job took most of your attention. It records names, never internal identifiers, and it never slows the app down to do it.

The problem
  • Time spent per customer or per part of the business is invisible
  • Naive usage tracking counts an abandoned open tab as work
Sound familiar?
What you get
Real active time, not tab-open time
The module and the customer that consume the most attention are named
Numbers feed both the builder's own milestones and the agency's health view

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →