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
- Used AI-assisted diagnostics during incident response.
- Generated automated risk assessments to estimate the QA impact of changes.
- Let product managers ask questions about the codebase in natural language.
- 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.
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
Blackstone cut dev onboarding to minutes with Factory Droid
Blackstone, the alternative asset manager, runs Factory's Droid agents inside its own data center and uses them across the whole software lifecycle: code review, testing, document…
Getting a new developer set up and contributing to the codebase went from up to two weeks to minutes using Factory and dev containers, as reported by…
How Datadog tested Codex code review by replaying past incidents
Datadog ran Codex against old pull requests that had contributed to incidents, to check whether AI review would have caught the risk. After the test, it rolled Codex review out wi…
As reported by OpenAI: Codex 'found more than 10 cases, or roughly 22% of the incidents' examined, where engineers said its feedback would have made …
League halved product cycle times with Claude Code and overnight agent teams
League, which builds member health apps for health plans and providers, rolled Claude out company-wide and moved its engineers to Claude Code. Small pods now ship production code …
Cycle times from idea through pull request cut in half in the four months after the Accelatron, as reported by Anthropic.
Guides
Best Claude Code Alternatives in 2026: Open-Source, Cheaper and Multi-Model
The strongest alternatives to Claude Code, grouped by why you are switching: price, model choice, open source or a different workflow. Live usage and prices for each.
AI Coding Agent Pricing Explained: Claude Code, Cursor, Codex and Copilot (2026)
What Claude Code, Cursor, OpenAI Codex, GitHub Copilot and other coding agents really cost: plan prices, usage limits, subscription vs API billing, and how to estimate your monthly bill.