> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enfors.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The Leader lens

> The macro picture — what is my AI workforce doing and costing?

The Leader lens answers the question every executive has about AI: *what is my workforce
doing, and what is it costing me?* It needs no dashboard-building and no SQL.

## Live workspace view

The moment you open Enfors, you see the whole workspace **live**:

* how many agents are **connected** and how many are **active**,
* how much **work** has run today,
* how much it's **costing**,
* and a **breakdown of outcomes**.

One glance gives you the state of the entire AI workforce.

<Frame caption="The live workspace view">
  <img src="https://mintcdn.com/enfors/vp6oPmBU7YFgD-tH/images/live-workspace.svg?fit=max&auto=format&n=vp6oPmBU7YFgD-tH&q=85&s=cea2b5d48375fc99d77ca80dda48fc01" alt="Live workspace overview" width="1200" height="750" data-path="images/live-workspace.svg" />
</Frame>

## Pulse briefings

[Pulse](/concepts/pulse-reports) generates reports any leader can read — daily, weekly,
or monthly, plus deep dives. A weekly briefing shows what was developed, total spend,
**cost per shipped value**, and where the effort went (development, research, bug fixes,
coordination, product management) — weighted by real decisions.

<Frame caption="A weekly Pulse briefing">
  <img src="https://mintcdn.com/enfors/EStKoMAmv9k4MqOd/images/pulse-weekly.svg?fit=max&auto=format&n=EStKoMAmv9k4MqOd&q=85&s=f7c5e588fcaa607cb1743fb92aa6b786" alt="Weekly Pulse briefing" width="1200" height="750" data-path="images/pulse-weekly.svg" />
</Frame>

## Ask, don't build dashboards

The real shift: a leader doesn't need another dashboard. You simply **ask**. From inside
Claude Code or Cursor you can type a question in plain English —

> show me what the team produced in the last three days

— and Enfors queries the [decision ledger](/concepts/decision-ledger) directly (no SQL),
lets you follow up and explore hypotheses, and can render a shareable report.

See [Ask Enfors](/using/ask-enfors) for how to set this up.

<Frame caption="A generated report — per-member breakdown, cost, PII redacted, needs-attention">
  <img src="https://mintcdn.com/enfors/EStKoMAmv9k4MqOd/images/generated-report.svg?fit=max&auto=format&n=EStKoMAmv9k4MqOd&q=85&s=f408ece45bff418d96380e12de904951" alt="Generated leadership report" width="1200" height="750" data-path="images/generated-report.svg" />
</Frame>

A generated report typically includes general metrics, a **per-team-member breakdown**
(what each did and what it cost), and **highlights** — including a "needs attention"
section that might flag, say, a configuration script that turned out to be **rework**.

## Where to go next

<CardGroup cols={2}>
  <Card title="Ask Enfors" icon="comments" href="/using/ask-enfors">
    Connect Claude Code / Cursor and query in plain English.
  </Card>

  <Card title="Builder lens" icon="magnifying-glass" href="/using/builder-lens">
    When a number raises a question, drill into the decision behind it.
  </Card>
</CardGroup>