Factory Launches Agent Effectiveness to Prove Its Droids Actually Ship Faster
Factory's new Agent Effectiveness dashboard links Droid AI sessions to cycle time, work intent, and shipped artifacts -- giving engineering leaders their first real ROI signal
- Factory launches Agent Effectiveness -- a new analytics layer linking Droid AI sessions to cycle time, work intent, and shipped artifacts.
- Three dashboards: Throughput (cycle time vs. usage), Output (session intent breakdown), and Attribution (spend traced to specific issues and PRs).
- Integrates with Jira, Linear, GitHub, and GitLab; telemetry exportable via OpenTelemetry to existing observability stacks.
- Addresses a real enterprise pain point: AI coding tool costs now run $200-$600/month per engineer, but most orgs lack a single dashboard showing what changed.
- Factory context: $1.5B valuation, $150M Series C, Droids deployed at Nvidia, Adobe, EY, MongoDB, and Bayer.
- Currently in private preview -- enterprise customers can request access via their account team.
Factory just launched Agent Effectiveness, a new analytics layer inside Factory Analytics that connects its AI coding agents -- called Droids -- to actual engineering outcomes. The pitch is simple but pointed: knowing how many Droid sessions your team ran is not the same as knowing whether those sessions made your software ship faster.
"How has AI actually accelerated my organization?" is the question behind every enterprise AI investment review. Token counts and API calls don't answer it. Leadership wants to know whether developers are more productive and whether the cost is justified. Agent Effectiveness is Factory's attempt to close that gap.
What Factory's Droids actually do
Factory's Droids platform handles the full software development workflow -- writing code, running tests, reviewing pull requests, generating documentation, and managing deployment. Where most AI coding tools respond to prompts, Factory's Droids are designed to own engineering workflows end to end.
Factory ships a coordinator agent that decomposes work and dispatches to specialized Droids -- code, review, docs, test, and Knowledge -- with explicit role boundaries rather than one generalist agent. Its Linear and Jira integrations turn tickets into the native unit of work, so the Droid swarm picks up issues with acceptance criteria, comments, and linked context already attached. That tight integration with existing project management tools is exactly what makes Agent Effectiveness possible: the system already knows what work was planned, so it can measure what actually shipped.