Springworks runs 50+ check-ins across a fully remote engineering org

Springworks is around 300 people and fully remote. Every team ran a daily standup, and since the pandemic every standup was a video call with the whole team on it.At small scale that is fine. As the team count grew, the cost stopped being linear. Each call pulled a group of engineers out of focus at a fixed hour, and each one needed a project manager to organise it, run it, write up what was said, and chase the action items afterwards.The PMs were spending their week on meeting logistics. The engineers were spending their mornings waiting for their turn to speak. And neither group could argue for cancelling, because the visibility the standup produced was genuinely necessary.They needed the output without the meeting.

Springworks moved every standup into Slack with Troopr Check-ins, and kept going until more than 50 were running across different teams and projects.Team members answer with a click. Troopr compiles the report with everyone's responses alongside their issues and recent activity from Jira, so the update carries evidence rather than recollection. Absences, individual and team-wide, are handled automatically rather than by someone remembering who is out.Stakeholders get one consolidated view of everything happening across all teams on a given day, which no arrangement of separate standup calls could have produced.Teams also run sprint retrospectives the same way, which turned process improvement into something that happens rather than something that gets scheduled and then dropped.

Springworks saves roughly 3 hours a week for every project manager on meeting logistics, and roughly 30 minutes a day for every team member.More than 50 live check-ins is the number to pay attention to. It is what happens when the thing works well enough that teams adopt it without being asked, and it is a scale of deployment that a standup tool bolted onto a stack does not reach.