Charge your SaaS tenants on outcomes, not flat-rate seats

Four primitives that fix outcome-based SaaS billing

Each one closes a margin gap that subscription tools can't. Wire them in once and your SaaS platform has commercial superpowers from the first tenant onboarded.

Per-tenant cost cap in one POST

Out-of-the-box SDK in Node.js and Python. Configure the per-tenant cap once; Rev rejects over-cap usage and reports the cost side-by-side with the renewal outcome bonus.

// Configure a per-tenant cost cap on the SaaS billing tier
const tier = await rev.pricing.createTier({
  agent_id: 'enterprise-billing-v2',
  base_fee: 0.10,          // $0.10 per workflow run
  usage_rate: 0.00003,     // per unit consumed
  outcome_bonus: 4.00,      // $4.00 per renewed seat
  cost_cap_usd: 0.50,       // per-tenant ceiling
  currency: 'USD',
});

// Meter every tenant usage event — returns the OK billable event
const event = await rev.meter.emit({
  agent_id: 'enterprise-billing-v2',
  customer_id: tenant.id,
  units: usageCount,
  outcome: 'pending',
});

// Resolve the tenant outcome — bonus posts on renewal, refunds on churn
if (renewalClosed) {
  await rev.outcomes.resolve(event.id, 'success');
} if (churned) {
  await rev.outcomes.resolve(event.id, 'failure');
}

Rev vs subscription-firstSaaS billing

Stripe metered billing, Chargebee, and Maxio charge on schedule. They can't do per-tenant cost caps or reconcile a hindsight outcome. This is the gap Rev fills for SaaS platforms.

The common pattern: keep Stripe, Chargebee, or Maxio for invoicing and revenue recognition, wire Rev for outcome-based metering. The services compose — Rev sits in front of charging as the pricing engine, and behind your tenant workflows as the per-tenant usage layer.