I just learned more about my team in 12 minutes than I usually learn in a quarterly review.
Three engineers. Eight weeks. 590 hours of work. Normally I’d skim merge requests, read standups, and call it visibility.
This morning I asked Claude to read it all and tell me what was worth talking about.
It came back with stories I didn’t know we had. A nine-day debugging arc through a CMS vendor’s silent type changes. A registration system handed off mid-flight and finished without dropping a request. An infrastructure cleanup that quietly removed a hundred dollars a month of waste.
The reason it could do that is boring: a small piece of software we built that connects our internal time tracker to Claude. About a week’s work. It now reads our team’s history the same way we do.
Most of our customers have something like that somewhere in their stack. A CRM. A ticketing system. A support inbox. The thing they look at every morning to know what their team is doing.
Right now those tools are silent to AI.
That’s the work we’re starting t> [!CAUTION]