Growth

This section asks a simple question: once an agent can complete useful work, how does one successful task become repeat usage, account expansion, and revenue growth?

Agent products resemble SaaS in some ways, but the center of gravity is different. SaaS often tracks logins, seats, and feature usage. Agent products should pay closer attention to whether tasks are completed successfully, whether users delegate adjacent work, and whether the customer starts treating the agent as an organizational capability.

Growth Starts With The First Successful Task

Activation should not mean signup, installation, or first login. Trust begins when the user asks the agent to do useful work and accepts the result.

That has two consequences:

  • The first task should be stable; do not choose a highly uncertain task just to showcase capability.
  • After activation, help the user discover adjacent tasks quickly, or the first success may remain a one-off trial.

See Activation Path.

Expansion Has Three Paths

Agent product expansion can be split into three paths:

PathWhere growth comes fromMain risk
Seat expansionMore people use the same agentActivation quality drops in new teams
Workflow expansionThe same users delegate more task typesNew workflows are less reliable
Capacity expansionMore task volume, concurrency, or service levelUsage grows faster than margin improves

These paths reinforce each other: more workflows create more capacity demand; more capacity and value give sales or customer success a reason to pursue account-level expansion.

See Expansion Mechanisms.

Growth Quadrants

Split by existing/new users and existing/new workflows:

DimensionExisting workflowNew workflow
Existing usersIncrease stable frequencyExpand into adjacent task types
New usersAcquire users into validated scenariosExplore new scenarios

The quadrants require different operating motions:

  • Existing users × existing workflow: improve speed, accuracy, trigger timing, and everyday entry points.
  • Existing users × new workflow: expand through adjacent recommendations, example tasks, and small pilots.
  • New users × existing workflow: route acquisition into the most reliable first task.
  • New users × new workflow: highest risk; better as experimentation than the main growth engine.

Boundaries

  • Metrics defines whether growth is healthy: successful tasks, quality, retention, and unit economics.
  • Pricing turns growth into revenue: subscription, usage-based, hybrid models, and tiers.
  • Playbooks turns growth into operating motions across customer success, support, sales, and engineering.
Was this page helpful?