This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 12 · Lesson 12.2 · 11 min

What Each Agent Costs

Calculate the full monthly cost of each agent: subscription, usage and the human time spent supervising it.

Module 12
ROI: Proving It Paid Off

Turn a feeling into a number your partners will believe

Bruno Ashford
Bruno Ashford · Module 1201 / 12
The uncomfortable question
If you cannot say what it returns, someone will switch it off.
Bruno Ashford
Bruno Ashford · Module 1202 / 12
The method

Four numbers, one page

  1. 1Hours savedSame task, before and after
  2. 2True costSoftware, usage, supervision
  3. 3QualityRework and errors avoided
  4. 4AI P&LNet gain, payback, ROI
Bruno Ashford · Module 1203 / 12
Lesson 12.1

Measuring hours saved

Count human minutes, not machine minutes.

  • Time three real runs per task
  • Include your review and fixes
  • Value hours at loaded cost
  • Decide where the saved hours go
Bruno Ashford · Module 1204 / 12
Illustrative example

Roofing contractor quotes

BeforeAfter
Minutes per quote7020
Quotes per month4040
Hours per month4713

Illustrative numbers for teaching, not a sourced statistic.

Bruno Ashford · Module 1205 / 12
Lesson 12.2

What each agent really costs

The subscription is rarely the biggest line.

  • Share of your Claude plan
  • Tools bought only for the agent
  • Weekly supervision time
  • One-off build hours
Bruno Ashford · Module 1206 / 12
Lesson 12.3

Quality counts too

Fast and wrong is expensive.

  • Define failure per agent
  • Sample ten outputs a week
  • Rework above 25 percent: fix first
  • Count errors avoided as gains
Bruno Ashford · Module 1207 / 12
Lesson 12.4

The three formulas

  1. NetMonthly gainTotal gain minus total monthly cost
  2. PaybackMonthsBuild cost divided by net monthly gain
  3. ROIAnnualNet annual return divided by total annual cost
Bruno Ashford · Module 1208 / 12
Illustrative agency P&L

Five agents on one sheet

4 of 5paid back within two months
1switched off for high rework
1 pageto get partner approval
Bruno Ashford · Module 1209 / 12
Lesson 12.5

Score your next use cases

CriterionHigh score means
ValueMany hours per month
RepeatabilitySame steps every time
Data readinessInformation in one place
RiskLow damage if wrong
EffortQuick to build
Bruno Ashford · Module 1210 / 12
Decision rule

Keep, fix or kill

Every row ends with a decision.

  • Payback under three months: scale it
  • High rework: fix the context
  • Negative after three months: switch off
  • Pick three next, never ten
Bruno Ashford · Module 1211 / 12
Recap
Measure honestly, decide on one page, and let the numbers choose what you build next.
Bruno Ashford
Bruno Ashford · Module 1212 / 12
01 / 12

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1List every paid tool the agent touches

Start with your Claude plan (Pro, Max, Team or API usage) and add every connected service that bills you: your CRM, email platform, data tools, automation platform. Only allocate the share of each tool that exists because of the agent, not tools you would pay for anyway.

2Split shared subscription costs fairly

A single Claude plan usually powers several agents. Split it by rough share of use: if the weekly report and the follow-up routine take most of your sessions, they carry most of the cost. A simple percentage per agent is good enough; precision here changes nothing.

3Check your real usage

On a subscription plan, check the usage screen in your Claude account to see how close you run to your limits. On API billing, the Anthropic Console shows spend by day and by key, so give each automation its own key if you want cost per agent without guesswork.

Prompt for Claude
Look at the skills, subagents and scheduled routines in this project. List each one with how often it runs, roughly how much work it does per run (small, medium, large), and which external tools or connectors it uses. I will use this to allocate costs per agent.
4Add supervision time

For each agent, estimate human minutes per week spent reviewing output, approving actions, fixing mistakes and updating instructions. Multiply by the loaded hourly cost. This line is often larger than the software cost, and that is fine, as long as you see it.

5Include the build cost once

The hours you spent building the skill or routine are a one-off investment. Record them separately so you can calculate payback period later, instead of hiding them or spreading them randomly across months.

Most people think AI costs one line on the card statement. It does not. The biggest cost in most small businesses is not the subscription, it is the hour a week someone spends checking, fixing and nudging the agent.

If you ignore supervision time, you will keep agents that are secretly losing money. If you count it, you will know exactly which ones earn their seat.

Key points

  • Full cost equals software share plus usage plus supervision time.
  • Supervision time is usually the largest and most ignored line.
  • Give automations their own API keys if you want clean cost data.
  • Track build time as a one-off investment for payback.

Avoid

  • Loading the whole Claude plan onto one agent and killing a good project on paper.
  • Forgetting connected tools that were bought only for the agent.
  • Treating supervision as free because it is "just a quick look".
  • Ignoring build time, which makes payback impossible to calculate.
Real-world example: an accounting practice

An accounting practice ran three agents on one team plan: a client document chaser, a month-end checklist runner and a meeting notes summarizer. Software cost per agent was modest. But the document chaser needed 90 minutes a week of partner review because it sometimes chased clients who had already sent files. Once that supervision cost appeared on the sheet, the partners fixed the data source instead of blaming the tool, and supervision fell to 20 minutes.

Bruno Ashford Subscribe