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: 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%'.
As reported by the source (Factory case study); AgentGid did not measure these figures.
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
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 …
Script Gemini CLI in your terminal: explain logs, write commits, document files
Gemini CLI's headless mode takes piped input and returns plain text or JSON. That makes it usable inside shell scripts, aliases and CI jobs.
Explanations of failures from piped logs, and commit messages generated from staged diffs.
Build a CI-health monitoring agent with the Claude Agent SDK and GitHub MCP
In this Anthropic cookbook notebook, an agent gets the official GitHub MCP server and is told to look over recent CI runs. It reports failing jobs, flaky patterns and recommended …
A status summary of recent CI runs and what triggered them.
