Skip to content
Agents tracked: 501 Releases (7d): 777 Agent status: no reported issuesSince last limit reset: Claude 10d · Codex 8d For AI agents: Markdown Updated Nov 21, 2026
Case study EmpowerResults as reported by Factory

How Empower cut incident response time with Factory Droids

Fintech company Empower used Factory's platform and Review Droid for incident diagnostics, QA impact analysis, product questions and automated code review. As reported by Factory, response and review times fell.

The problem

Empower's engineers work across the US, New Zealand, South America, Canada and Australia, which slowed code reviews and QA. Incident response was also slow, and product and engineering had knowledge gaps between them.

How they did it

  1. Used AI-assisted diagnostics during incident response.
  2. Generated automated risk assessments to estimate the QA impact of changes.
  3. Let product managers ask questions about the codebase in natural language.
  4. Ran Review Droid on pull requests to enforce best practices and protect database schema integrity.

Results as reported by Factory

  • As reported by Factory: incident response time was reduced 'by up to 40%'.
  • Delays in product-to-engineering Q&A were reduced 'by up to 50%'.
  • PR created-to-approval times were often reduced 'as much as 50%'.

These figures are as reported by Factory in Factory case study ↗ (Apr 7, 2025). Factory sells the product used here. AgentGid did not measure or independently verify them.

Takeaway. Point an agent at your incident diagnostics and cross-team codebase questions, not only at writing code.
AgentGid's take

This suits an engineering org with distributed teams, an existing incident process and a real PR backlog, plus someone to wire diagnostics and review rules into it. Treat the 40% and 50% figures as vendor-reported, and note Droid has a Gid Score of 15 (rank 29) with downloads slowing. For a cheaper, open-source route, Pi is Free (OSS), though model costs apply.

The agent used here

Similar use cases

Guides