Expansion Mechanisms

Expansion means existing customers pay more during the contract period. For agent products, expansion should not be read as revenue growth alone. Decompose whether growth comes from more users, more workflows, or more capacity.

Three Expansion Paths

Seat Expansion

Expand by user count. A customer starts in one team, then rolls the agent out to more teams or the whole company.

  • Fits: personal productivity, engineering, research, writing, and internal assistant products.
  • Trigger: internal word of mouth, collaboration needs, or managers wanting a shared work pattern.
  • Risk: new teams may have different task types, permissions, and habits; activation quality does not automatically copy.

Workflow Expansion

Expand by task type. The customer starts with one class of tasks, then delegates adjacent work.

  • Fits: most enterprise workflow agent products.
  • Trigger: users repeatedly complete one task type and start asking, “can it also do X?”
  • Risk: the new workflow may have different inputs, tools, quality standards, and liability boundaries, so completion rate and cost need fresh measurement.

Workflow expansion often reveals agent product depth better than seat expansion: the same user is willing to delegate more work, which means trust is increasing.

Capacity Expansion

Expand by capacity. The same user and workflow require higher task volume, concurrency, longer context, stronger models, or higher service levels.

  • Fits: subscription and hybrid models with tiers, quotas, concurrency, or service levels.
  • Trigger: customers approach current limits or move the agent into more critical daily work.
  • Risk: if capacity expansion only increases resource consumption without higher price or efficiency, unit economics deteriorate.

How The Paths Reinforce Each Other

Three-axis expansion flywheel Agent products expand across three reinforcing axes: workflow depth, capacity demand, and seat coverage Seat 1 team Few depts Company-wide Enterprise more seats → more workflow surface area Workflow 1 workflow 3 workflows 8 workflows Depth ceiling more workflows → higher token usage Capacity Entry capacity Team capacity Enterprise capacity Custom Time → The three axes compound multiplicatively, not linearly. A mature customer advances on all three simultaneously. Capacity upgrades raise account value → trigger CS or sales motion → drive wider team adoption and close the loop.

A healthy expansion path is usually a loop, not a straight line:

stable first task
  -> repeated use of one workflow
  -> adjacent workflow recommendation
  -> higher volume and service requirements
  -> larger tier or enterprise contract
  -> more teams willing to adopt

If quality drops anywhere in this chain, expansion can become a churn signal: a failed new workflow, a hard stop at a quota boundary, or a larger bill without a clear value explanation all erode trust.

Early Signals

Expansion signals are best read in combination rather than as one threshold that automatically triggers sales.

SignalMeaning
Repeated use of the same workflowWork has entered a daily rhythm
Adjacent workflows tried naturallyThe user is moving more tasks over
Stable task success rateExpansion will not immediately amplify quality issues
Human-review rate remains controlledRisk checks are not consuming the efficiency gain
Capacity usage approaches the current plan boundaryUpgrade demand exists, but margin must be checked
Internal referrals appear inside the customerSeat-expansion window is opening

Common Mistakes

  • Pursuing seat expansion while ignoring workflow depth per user.
  • Waiting until the customer hits a hard capacity stop before discussing upgrade.
  • Pushing upsell while quality or retention signals are already declining.
  • Buying expansion with discounts before confirming post-expansion task margin.

Cross-Section Connections

Was this page helpful?
Edit on GitHub