Product

Product

Why we price by completed runs, not seats

Why we price by completed runs, not seats

Seat pricing punishes the teams agents help most. Here’s how run-based pricing works and what counts as a run.

Seat pricing punishes the teams agents help most. Here’s how run-based pricing works and what counts as a run.

Portrait of Ines Calloway

Ines Calloway

5 min read

Abstract data illustration for “Why we price by completed runs, not seats”

If an agent does the work of a queue, charging per seat makes no sense. The people using Cairn are often the ones building agents, not the ones the agents replace.

What counts as a run

A run is one trigger processed to a result — a ticket resolved, an invoice matched, a request granted. Runs that fail on our side are never billed, and shadow-mode runs count at a fifth of the rate.

Predictable bills

  • Every plan includes a run allowance

  • Hard and soft spending limits per workspace

  • Alerts at 50%, 80% and 100% of your allowance

We want the bill to track value. If agents aren’t completing work, you shouldn’t be paying for them.

Portrait of Ines Calloway

WRITTEN BY

Ines Calloway

Co-founder & CEO

Ines ran support operations at a public payments company before co-founding Cairn. She writes about running agents in production and what changes when software finishes the job.

Field notes

One email a month. Only the useful parts.

Lessons from running agents in production, new templates and the releases worth knowing about. Unsubscribe in one click.

Create a free website with Framer, the website builder loved by startups, designers and agencies.