Chase Agents pricing

Pricing for teams buying automation infrastructure: actions, automations, seats, API access, and enterprise platform support. Start small and expand as automations become more valuable to the business.

Plans

• Solo Plan — $9.99/month. For solo founders who want to automate repetitive work without hiring or managing a team.
• Pro Plan — $99/month. For teams who need scale, collaboration and technical flexibility.
• Business Plan — $499/month. For teams running high-volume automations who need advanced limits and support for production workflows.

Pricing FAQ

How should we think about pricing as we adopt Chase Agents?

Think about pricing in three layers: how many actions you need to run, how many automations you need to operate reliably, and how many seats you need across the team. Higher tiers add platform capabilities like API access, governance, and rollout support once Chase Agents becomes core infrastructure.

When should a team move from free to a paid plan?

Move up when the work is no longer experimental. If your team is depending on actions to run consistently, needs shared seats, or is putting real automations into production workflows, you are in paid-plan territory.

What actually changes at a higher plan?

Higher plans are for teams running more volume and more operational complexity. You get more room for actions and automations, more seats, and access to deeper platform capabilities like API access, governance controls, and enterprise support.

How do actions, automations, and seats relate to each other?

Actions represent execution volume, automations represent the workflows you are operationalizing, and seats represent who can build, operate, and manage that system. Most teams feel pricing pressure in that order: first usage, then automation footprint, then team access.

When does API access matter?

API access matters once Chase Agents becomes part of your broader system architecture, not just a UI-driven tool. Teams usually care about it when they want to trigger workflows programmatically, integrate more deeply with internal systems, or standardize around the platform.

Can we start small and expand later?

Yes. The point is to start with a narrow operational use case, prove it, and then add actions, automations, and seats as the system becomes more valuable to the business. You do not need to buy for the end state on day one.

What does enterprise support usually include?

Enterprise support is for teams that need more than software access. It usually means rollout guidance, governance help, API planning, security reviews, SSO requirements, SLAs, and custom integration support around business-critical workflows.