Pricing

Pricing built around teams, not seats.

Rent a Team is priced around the scope of the team you want to deploy, the business job it is covering, and the amount of coordination, review, and support involved.

Most customers start with one team, prove value in one function, and then expand into additional teams or broader coverage later.

Lite

Teams buying their first AI team

From $499/month

One team with standard scope and one clear business job

Good fit if you want to start with one focused deployment and keep the launch easy to evaluate.

  • Best for one team or one tightly defined function
  • Standard channel coverage and review model
  • Core reporting and operating visibility
  • Designed for lower-volume, easier-to-scope use cases

Performance

Teams with advanced coordination, review, or customization needs

From $1,999/month

A more tailored deployment with deeper routing logic, more stakeholders, or higher-touch support

Good fit if the process involves approvals, exceptions, or more tailored operating rules.

  • Advanced coordination and routing logic
  • Higher-touch review and support model
  • More tailored reporting and exception handling
  • A stronger base for expanding into additional team functions later

Enterprise

Organizations with multiple teams, stricter governance, or more complex deployment needs

Custom

Custom deployment for multi-team rollouts, dedicated environments, or higher-governance requirements

Good fit if you want to deploy more than one team or need a more bespoke operating model.

  • Dedicated setup and planning
  • Custom governance, approval, or review design
  • More complex deployment requirements
  • Built for broader operational adoption across functions

What affects pricing

How pricing scope is usually set

  • How clearly the business job can be scoped
  • How many handoffs, channels, or stakeholders are involved
  • How much review, reporting, and support the team needs
  • Whether you are starting with one team or planning to expand into more functions
  • Whether the deployment requires more tailored operating logic

Expansion path

Start with one team. Add more coverage later.

The first deployment does not need to cover every department. It usually works better to start with one team, judge the operational value, and expand into more business functions once the model is proving itself.

Do you charge per agent?

No. Pricing is based on team scope, operating complexity, and support rather than a simple per-agent count.

Can we start with one team and add more later?

Yes. Many customers start with one team and expand into additional functions once the first deployment proves value.

Do I need a custom deployment?

Only if the use case needs more tailoring, stronger review requirements, broader rollout planning, or multiple teams.

Is pricing fixed for every team?

No. The starting price depends on the job, the amount of coordination work involved, and how much coverage the team needs.