A team-workload transparency platform: see invisible work, the true load and your costliest clients

The extra work an employee does shows up nowhere. When planned work runs late, only the delay is visible - not the hours that went into helping colleagues, waiting and interruptions. Shadowy gives a place to say it without it sounding like an excuse

• Posting receipts and invoices for a colleague - 135 entries, 113 hours
• Scanning documents for another team - the most common kind of help
• Entering a bank statement by hand when the automatic import failed
• Employer reports and correspondence with the tax authority outside one's role
• Onboarding a new hire - 54 minutes on average each time

Workload is planned by official duties, but the team works by the real ones. So the plan doesn't hold, and the reason shows up in no report. It gives a manager two things there's otherwise nowhere to get: which process repeats often enough that fixing it is cheaper than enduring it, and which person carries more than it looks from the outside

• 82 recurring processes: the same category with the same client three or more times
• Three people carry 59% of all logged time - the other seven the rest
• The busiest has 153 hours, the lowest 8 - in the same team
• 42 different categories: the work is far more fragmented than the plan suggests
• July 217 h, August 240 h - the load is growing, not fluctuating

On a fixed service fee a client can be unprofitable for months, and it only surfaces at year end - if at all. When the team's time is tied to a client and multiplied by an hourly rate, the overrun becomes visible in the same month it happens - and so does how unevenly the portfolio is really split

• The five largest clients take up 30% of all team time
• The largest client - 58 hours in two months, the next 37
• The median client - 2.4 hours: most of the portfolio is small
• 17 clients under one hour, 15 clients over ten
• Invoice posting and issuing - 140 entries, 139 hours in total
• A third of entries are under 15 minutes - the ones nobody counts

If a team sees the tool as surveillance, they won't use it, and the data is worthless. So visibility is limited by role, and the employee decides what goes into the system

• A manager sees their own team's approved entries - not other teams'
• Screen activity, keystrokes and private conversations are not logged at all
• The AI only makes a draft - nothing is saved without the employee's approval
• After the pilot the data can be exported, and after the retention period it is deleted