# Dryfit Scenario: Usage-based (metered) SaaS

> Metered SaaS where revenue scales with consumption. Positive signals are completed jobs and compute cycles; negative signals are stalled usage.

*Source: [https://www.getbeton.ai/oss-tools/dryfit/scenarios/posthog-usage-based/](https://www.getbeton.ai/oss-tools/dryfit/scenarios/posthog-usage-based/)*

**Scenario kind:** posthog_usage_based
**Use-case kind:** metered
**Value metric:** API calls, compute hours, messages, requests
**Config file:** `configs/posthog_usage_based_mvp.yaml`
**Dataset id:** `posthog_usage_based_mvp_v1`

## Scale

- Accounts: 320
- Users per account (mean): 4
- Sessions per user (mean): 9
- Duration: 30 days

**Success event:** `job_completed` (account)

## Research metrics

- Usage velocity
- Quota consumption
- Usage acceleration

## Positive signals (ground truth)

- **request_to_job_completion** (count 95): `api_request → job_completed`
- **message_compute_job** (count 45): `message_sent → compute_hours_used → job_completed`

## Negative signals (ground truth)

- **request_compute_stall** (count 70): `api_request → compute_hours_used`
- **message_only_repeat** (count 65): `message_sent → message_sent`