# Agent Effectiveness

Measure how much faster your engineering organization ships with Factory, and connect agent spend to the work it produces.

Agent Effectiveness measures how much faster your engineering organization ships with Factory, and connects agent spend to the work it produces.

Most teams that adopt AI coding agents can tell that work is moving faster, but they have a hard time proving it. Survey-based estimates of "how long would this have taken before AI" are unreliable, and existing delivery metrics show how fast work moves without showing how much of that speed came from agents.

Agent Effectiveness answers that question from data your organization already produces: sessions in Factory, and issues, projects, and pull requests in the tools your teams already use.

---

## How it works

Agent Effectiveness reads from your connected project management, issue-tracking, and source control integrations, then links agent activity to the work those tools track. As agent spend is applied, cycle times on projects, issues, and pull requests change measurably, and teams use the recovered time either to take on more work or to raise the bar on the work they already have.

Analysis happens at the organization level and requires no per-repository configuration.

---

## What it measures

<PropertyList>
  <Property name='Throughput'>
    How cycle times on projects, issues, and pull requests change as agent spend is
    applied, and which projects, pods, and users the change is concentrated in.
  </Property>
  <Property name='Output'>
    Where effort is going, using session intents to classify work and compare the split
    of engineer time and Factory Standard Credits against your targets.
  </Property>
  <Property name='Attribution'>
    The link between an individual session, the work stream it belongs to, and the issues,
    projects, and artifacts it produced.
  </Property>
</PropertyList>

See the [Effectiveness dashboard](/agent-effectiveness/dashboard) for how each view is presented in the Factory App.

---

## Session intents

A session intent is a classification of what a session was for, such as feature development, maintenance, bug fixing, or exploration. Intents let you compare planned allocation against actual allocation during the quarter rather than after it.

When the mix drifts from your targets, the Output view surfaces the drift while there is still time to act on it.

---

## Attribution and local signals

Attribution connects a session to the concrete work it produced. It relies on local signals, which record the association between a session and the repository work it touched, so an organization-level number can be traced back to specific issues, projects, and artifacts.

<Note>
  Attribution and the Output view only cover the systems you connect. Connect every issue
  tracker and source control provider your teams use so coverage is complete.
</Note>

---

## Other usage and adoption metrics

Agent Effectiveness focuses on delivery speed and the link between spend and shipped work. Adjacent measures are documented separately:

| Measure | Where it lives |
| :------ | :------------- |
| Factory Standard Credits consumption, tool usage, user activity, productivity, and per-user metrics | [Analytics API](/api-reference/analytics) |
| Self-hosted OpenTelemetry metrics export and cost management | [Telemetry and analytics](/enterprise/telemetry-and-analytics) |

---

## Requirements

Agent Effectiveness requires organization-level integrations plus the Advanced Analytics enterprise control. See [Enable Agent Effectiveness](/agent-effectiveness/setup) for the full setup.

<Note>
  Agent Effectiveness is in Private Preview. To request access, fill out the form at <a href="https://factory.ai/contact">factory.ai/contact</a> or contact your Factory account team.
</Note>

<RelatedLinks>
  <RelatedLink href='/agent-effectiveness/setup' title='Enable Agent Effectiveness'>
    Connect integrations and turn on Advanced Analytics.
  </RelatedLink>
  <RelatedLink href='/agent-effectiveness/dashboard' title='Effectiveness Dashboard'>
    Explore the Throughput, Output, and Attribution views in the Factory App.
  </RelatedLink>
  <RelatedLink href='/api-reference/analytics' title='Analytics API'>
    Query credits consumption, tool usage, and per-user productivity metrics.
  </RelatedLink>
  <RelatedLink href='/enterprise/telemetry-and-analytics' title='Telemetry and Analytics'>
    Export metrics to your own observability stack over OpenTelemetry.
  </RelatedLink>
</RelatedLinks>