Home›AI Agency Academy›Lesson 02
Module 01 · Lesson 02

The economics of a useful agent

Measure an agent by the business constraint it improves, not by how impressive the demo looks.

Last updated August 5, 2026•15–25 minutes•Free AI agent course
What you will learn

Build an agent economics worksheet

You will be able to connect an agent to a practical value hypothesis: less waiting, fewer dropped requests, more completed work, better quality, or protected team capacity.

Why this matters

Good agent work is useful before it is impressive.

A client cannot use ‘it saves time’ as a decision. They need to know whose time, which delay, what changes in the workflow, and what evidence would show that the service is worth keeping.

Core concepts

The language that keeps the work clear.

BaselineWhat happens today before the agent: volume, delay, error rate, conversion, or effort.
Value driverThe specific operational change, such as fewer missed calls or a faster first response.
Cost to serveImplementation time, model and channel usage, monitoring, and human review.
Risk-adjusted valueA gain is not useful if it creates avoidable complaints, unsafe action, or rework elsewhere.
The practical method

How to build an agent economics worksheet

Start with one metric

Pick the closest useful metric to the workflow: time-to-first-response, qualified appointments, resolved requests, or correction rate.

Measure the baseline

Collect a short, honest sample before promising an improvement.

State the mechanism

Explain exactly how the agent could change the metric: capture context, route sooner, answer a common question, or reduce re-entry.

Price the responsibility

Include launch effort, ongoing checks, channel fees, and a reasonable review cadence in the offer.

Worked example

Worked case: the economics of a useful agent

A clinic receives 70 appointment requests each week. Front-desk staff reply in batches, so some people wait until the next day.

The initial value hypothesis is not ‘AI will grow revenue.’ It is ‘a consent-aware web agent captures the right appointment details, gives an approved response immediately, and puts complete requests into the scheduling queue.’

The clinic compares response time, completed requests, staff corrections, and patient complaints for four weeks. Only then does it decide whether to expand.

Build it in practice

Complete the working artifact

Baseline: [current number]. Constraint: [delay, loss, error, or capacity issue]. Mechanism: [what the workflow changes]. Metric: [measure]. Cost to serve: [setup + ongoing]. Review date: [date].
Practice

Before you move on

  • Write a baseline for one workflow without guessing.
  • Choose one primary outcome metric and one quality guardrail.
  • List the operating costs that must be visible to the buyer.
  • The value claim has a measurable mechanism.
  • A quality or safety guardrail sits beside the outcome metric.
  • Usage and review costs are not hidden.
  • No revenue result is presented as guaranteed.

Lesson progress

Finished this lesson?

Save your place on this device so it is easy to pick up where you left off.

Not marked complete yet.