Key details

  1. Agent Pro uses consumption-based pricing.
  2. Legora describes consumption credits, usage visibility and spend controls.
  3. The broader Legora platform is not presented as a pure public self-serve usage product.
  4. No universal public credit-unit rate supports a reliable cost-per-task calculation.
  5. Independent reporting describes the move as consumption pricing layered onto existing commercial relationships.

What builders should take away

  1. If you are adding agentic features to SaaS, model variable inference/tooling cost separately from user seats before choosing packaging.
  2. Expose budgets, alerts and usage attribution before scaling consumption-priced features across an organization.
  3. Avoid marketing a simple cost-per-task figure unless customers can reproduce it from public unit rates and metering rules.
  4. Track gross margin by workload class, not just account, because agent usage can vary sharply among customers with the same seat count.

What changed

Legora has introduced a consumption-based pricing model for Agent Pro while keeping its broader platform commercial model intact. The company emphasizes consumption credits, real-time usage visibility and spend controls rather than a simple per-seat price for the agent workload.

Why it matters

AI agents can have materially higher and less predictable variable compute costs than traditional SaaS features. Separating agent usage from seats gives vendors a way to align revenue with cost, but it also shifts budgeting risk toward customers unless usage measurement and controls are clear.

Agent economics are being unbundled from seats

Legora's public materials describe Agent Pro as consumption-priced, while its broader platform remains sold through commercial contracts rather than a fully public self-serve price card. The distinction matters because customers can add AI workload cost without adding human users.

Controls become part of the product

Legora highlights real-time usage visibility and spend controls. In a consumption model, those controls are not admin polish: they are part of whether customers can safely deploy an agent across teams and matters without surprise bills.

Public unit economics are still incomplete

Legora does not publish a universal public conversion from credits to a standard customer cost per task. That means outsiders cannot responsibly calculate a representative effective price per legal workflow from public materials alone.

The broader lesson is architectural, not vendor-specific

For AI SaaS builders, the case illustrates a hybrid pattern: retain predictable platform or seat economics where they fit, meter expensive agentic workloads separately, and give customers tooling to understand and constrain usage.

Timeline

2026-08

Legora details Agent Pro consumption pricing

Legora published its rationale and controls for consumption-based Agent Pro pricing.

What to watch next

  • Whether Legora publishes more transparent credit conversion or rate-card information.
  • How customers respond to separate agent consumption charges at renewal.
  • Whether legal AI competitors converge on seats, consumption, outcomes or hybrid packaging.

Still unclear

  • Legora's public materials do not disclose a universal credit-unit rate, so external estimates of effective task economics would be speculative.
  • Customer contracts may differ materially by account size and negotiated terms.

Sources

Direct reading behind this dossier.

3 sources
Terms of Service
Legora primary

Commercial terms context for platform fees and consumption credits.