The trade agencies are asked to make
Small studios and agencies get pushed toward a grim choice. Tools that give you
clean per-project, per-person numbers tend to get them by watching people:
periodic screenshots, keystroke counts, a productivity score next to each name.
The tools that respect your team tend to leave you reconstructing project totals
from spreadsheets and Slack.
You don't actually need surveillance to answer "how many hours went to the Acme
project this month, and who worked on it." You need structure and automatic
capture.
Structure: organisation → teams → projects
Time is organised in a hierarchy, and totals roll up through it:
![]()
- An organisation holds your teams (Design, Dev, Ops).
- Teams own projects, each usually tied to a client.
- Hours captured on a project roll up to the team, and team totals roll up to
the organisation.
A contributor sees their own time. A manager sees the team and the org-wide
roll-up — without anyone having to compile it.
Capture stays automatic — and private
The per-person numbers come from the same automatic capture the solo product
uses: a desktop client (macOS, Windows, Linux) watches each person's configured
project directories, browser extensions track work by URL, and sessions appear
on their own. Nobody starts a timer; nobody installs a surveillance agent.
![]()
The manager view answers the questions that actually matter — who's on what,
how the week is distributed, which project is eating hours — using nothing but
tracked time. There are no screenshots, no keystroke logs, and no
productivity scores. The record is what was worked on, not a judgement about
how hard someone was working.
From team hours to client invoices
Because projects link to clients and rates, those rolled-up hours aren't just a
dashboard — they're billable. Per-project and per-client totals feed directly
into invoices, auto-numbered per organisation, so the work your team tracked
becomes the bill you send the client without a re-entry step.
Real-time when it matters
For the "who's working on what right now" question, active sessions broadcast
over a WebSocket, so a live view reflects what's being tracked across the team
as it happens — useful for coordination, without it being a monitoring tool.
The takeaway
A small agency can have clean per-project and per-team roll-ups without pointing
a surveillance system at its own people. Structure the work as organisation →
teams → projects, let capture happen automatically from file edits and URLs,
keep it screenshot-free, and bill clients from the same totals your managers
review.

