Wayfair built it in-house first. Troopr gave back 380,000 engineering hours a year.

Wayfair has engineering talent, so when its product, engineering and customer-facing teams wanted their Slack and Jira workflows automated, they built it themselves. That is the correct instinct and it is what most strong engineering organisations do first.The bots worked. The problem was everything around them. Somebody had to own them, patch them when Slack or Atlassian shipped an API change, extend them when a new team wanted a variation, and answer questions when they broke. Maintaining internal tooling is invisible work that never appears on a roadmap and never stops.Over time the maintenance pulled engineers away from the products Wayfair actually sells. The tooling was not the problem. Owning the tooling was.

Wayfair replaced the in-house bots with Troopr and standardised across teams.Engineering teams connected their Jira projects to their Slack channels, so issue context and updates arrive in Slack and actions are taken there. Customer-facing teams set up dedicated triage channels, giving each team a private space to work a request through while Troopr keeps Jira in step.Teams across departments run automated check-ins to stay current on what is happening without a status meeting. And where a team needed something specific, they configured workflow automations that trigger on a defined event and deliver the relevant chart or report into the channel that needs it.None of it required an engineer to own a bot.

An internal Wayfair estimate puts the saving at roughly 380,000 engineering hours per year across the teams currently using Troopr, valued internally in the millions.The headline number is the reclaimed time. The quieter win is that nobody at Wayfair is on call for the coordination layer any more. When Slack or Atlassian changes something, it stops being Wayfair's problem.If you are weighing building this yourself, Wayfair already ran the experiment.