HomeAI Agency AcademyLesson 38
Module 10 · Lesson 38

Manage margins, capacity, and usage

Understand labor, provider usage, support, and service limits before scaling delivery.

Last updated August 5, 202615–25 minutesFree AI agent course
What you will learn

Make a clear, safer operating decision.

You will be able to model the service capacity and margin of an agent offer without hiding variable cost or assuming a pilot will support unlimited requests.

Why this matters

Good agent work is useful before it is impressive.

An agency can win projects and still create a loss-making service if it underestimates support, review, changes, model usage, channel charges, or the time required to keep quality high.

Field note 38

Make the relationship visible.

AI AGENTS · FIELD NOTE 38Revenue − delivery − usage − support − riskTHE OPERATING MARGIN01Setup labor02Recurring support03Provider usage04Capacity limitOriginal visual framework for Manage margins, capacity, and usage.AI AGENTS · FIELD NOTE 38Revenue − delivery − usage − support − risk01Setup labor02Recurringsupport03Provider usage04Capacity limit
Use this framework to make manage margins, capacity, and usage visible before you build.
Core concepts

The language that keeps the work clear.

Gross marginWhat remains after the direct labor, provider, channel, and support costs required to deliver the service.
CapacityThe amount of client work a team can serve at an agreed quality level.
Usage limitA transparent boundary for variable model, message, voice, or integration consumption.
Service levelA realistic commitment about review, support, or response that the team can meet consistently.
The practical method

Work through the decision in order.

Track delivery effort

Measure the time spent in discovery, build, testing, client communication, review, support, and changes.

Track direct usage

Record the provider and channel cost drivers that vary with volume or complexity.

Set sensible limits

Define what usage, support, response, and change work are included before the client reaches a surprise bill.

Plan capacity by quality

Use review workload and exception volume—not sales desire alone—to decide how many clients a team can responsibly onboard.

Worked example

A realistic, bounded implementation.

An agency offers a managed voice intake service. The setup fee covers design and testing; the monthly fee covers monitoring and review; voice minutes and message usage are tracked against an agreed allowance.

After two pilots, the agency learns that clients with complex appointment rules need more exception review. It updates its capacity model and creates a higher-touch tier rather than pretending every client fits the original price.

The team protects quality by making usage and support assumptions visible, reviewing them monthly, and proposing changes before limits are exceeded.

Build it in practice

Use this copyable working template.

Adapt it to the client’s evidence, policy, people, and tools. Do not treat placeholders as approved instructions.

Setup labor: [hours/cost]. Recurring review/support: [hours/cost]. Variable usage drivers: [list]. Included limits: [list]. Quality capacity signal: [metric]. Change trigger: [condition].
Spacebrain implementation

Put the operating system around the agent.

Use workspace and client reporting, task workload, usage records from connected providers, and service reviews to understand operational cost and capacity.

Practice

Before you move on

  • Model one offer with setup, ongoing labor, usage, and support.
  • Choose one limit that prevents hidden delivery cost.
  • Write the client notice that occurs before an overage or scope change.
  • Direct cost is visible.
  • Usage and support limits are understandable.
  • Capacity is based on quality workload.
  • Pricing can change when evidence changes.

Build the operating layer around your agent.

Use the free Spacebrain workspace to keep contact context, handoffs, tasks, automation, and reporting together.

Start for free →