# Dryfit Scenario: PostHog Web (baseline)

> The minimum-viable PostHog scenario. A generic event stream with a two-step conversion funnel and corresponding negative path. Good starting point for signal-detection benchmarking before moving to business-model-specific variants.

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

**Scenario kind:** posthog_web
**Use-case kind:** baseline
**Value metric:** Generic SaaS activation (baseline)
**Config file:** `configs/posthog_mvp.yaml`
**Dataset id:** `posthog_mvp_v1`

## Scale

- Accounts: 500
- Users per account (mean): 4
- Sessions per user (mean): 10
- Duration: 30 days

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

## Research metrics

- Baseline conversion rate
- Funnel drop-off

## Positive signals (ground truth)

- **billing_then_purchase** (count 80): `page_billing → purchase`
- **invite_then_api_key_then_purchase** (count 35): `invite_teammate → api_key_created → purchase`

## Negative signals (ground truth)

- **billing_dropout** (count 70): `page_billing → page_pricing`
- **pricing_only_stall** (count 110): `page_pricing → page_pricing`