Achievers switched from PagerDuty and productized reliability on Microsoft Teams with Rootly.
- Microsoft Teams
- native incident response where engineers already work
- AI summaries
- keep stakeholders informed without interrupting responders
Having all the context, information, and required people in the same place, automatically, really helped us streamline the process to make sure we’re not missing something.
Stefan KolesnikowiczPrincipal SRE at Achievers
On this page
Achievers is a leading employee experience platform that helps organizations across 190 countries. Reliability is foundational to the product: outages or degraded performance directly impact engagement and trust for 4.3M+ employees using the platform worldwide.
Founded: 2002 in Toronto, Canada
Size: ~1200 employees
Before Rootly: Fragmented tools and manual workflows
Before adopting Rootly, Achievers’ incident management process was minimal and highly fragmented. The team relied on a combination of PagerDuty, Atlassian Statuspage, and other tools stitched together to manage incidents. This made it difficult to ensure incidents were properly tracked, prioritized, and managed.
Post-incident work was especially challenging. Root cause analyses lived in multiple places:
- SharePoint
- Jira
- Confluence
With no centralized system of record. The workflow was manual, involved many people, and created significant operational toil.
Why Achievers chose Rootly
Achievers needed a tool that could unify incident response into a single system while integrating seamlessly with the tools engineers already used every day. Just as importantly, it needed to work natively with Microsoft Teams, where most incident communication already happened.
Rootly stood out as the only platform that combined feature parity across incident management with deep Microsoft Teams support, while also integrating with monitoring tools like New Relic.
“There hasn’t been any other tool that we’ve been able to find that actually has this feature parity with Rootly and incident management with MS Teams.”
Stefan Kolesnikowicz, Principal SRE at Achievers
The result was a true single pane of glass for incidents, timelines, and follow-ups.
Capturing incident context where work already happens
Because Teams is central to how Achievers operates, capturing incident communication automatically was critical. With Rootly, conversations, updates, and decisions are easily added to an incident timeline without manual effort.
“Having the AI Rootly summary feature allows us to quickly summarize what is happening in an incident and pass it to internal stakeholders.”
Stefan Kolesnikowicz, Principal SRE at Achievers
During high-severity incidents, executives often join calls asking for real-time updates. Rootly’s AI-generated incident summaries allow the SRE team to quickly share accurate context without pulling responders away from mitigation work.
A seamless migration with immediate impact
Thanks to Rootly’s assistance, Achievers moved from PagerDuty and Atlassian Statuspage with minimal effort from engineers. Tooling and libraries made it easy to translate existing configurations, including infrastructure-as-code.
“The overall quality of addressing bugs has really improved since using Rootly. We’re able to get deeper insight into what’s going on and see more trends.”
Stefan Kolesnikowicz, Principal SRE at Achievers
Since adopting Rootly, Achievers has seen measurable improvements in incident follow-through, bug resolution quality, and operational visibility. Patterns and trends across incidents are now easier to identify, helping teams address systemic issues instead of repeatedly fixing symptoms.
Treating reliability as a product
From an SRE perspective, Rootly has helped ensure incidents are treated with the priority they deserve, from detection through resolution and learning. By tracking incidents end-to-end in a single system, the team has reduced manual toil and ensured issues aren’t repeated over time.
“If you have a way to scope out all your incidents and track them over time and display that to your business, you’re really getting your point across that reliability is an important part of the product.”
Stefan Kolesnikowicz, Principal SRE at Achievers
More importantly, Rootly enables Achievers to communicate the value of reliability to the broader business through metrics, trends, and impact analysis.
By consolidating incident management into a single pane of glass, Achievers has transformed reliability from a reactive function into a product-level discipline. With Rootly, the SRE team has reduced operational toil, improved incident learning, and given the business clear visibility into why reliability matters, and where to invest next
More customer stories
KnowBe4 switched from PagerDuty and turned Incident Response into a repeatable, predictable system with Rootly.
- 40%
- reduction in time to resolve
- 90%
- completion for retrospectives
Poll Everywhere switched from PagerDuty, cut on-call tooling costs and made response faster with Rootly.
- 50%
- faster time to first response for off-hours alerts.
- 60%
- fewer unnecessary wake-ups / secondary rollovers.
Webflow shutdown PagerDuty to use Rootly to build a proactive reliability culture.
- Lower
- MTTR through consistent, measurable incident workflows
- Greater
- visibility into incident trends across teams and services