DryFit scenarios
Each scenario is a complete YAML config — success event, positive and negative signal paths, scale parameters, noise probabilities. Pick one, run the generator, get a PostgreSQL dataset plus ground_truth.json ready to grade any detector output.
PostHog Web (baseline)
→ purchase
Generic SaaS activation (baseline)
Telegram Chat
→ event_signup
Chat engagement / retention
Contact / record-based SaaS
→ contact_created
Contacts, leads, subscribers, accounts managed
Credits / token-based
→ credits_purchased
Credits consumed, tokens used, compute units
Event-volume SaaS
→ custom_event_tracked
Events tracked, data points ingested, log lines
Feature-gated (tiered) SaaS
→ upgrade_clicked
Plan tier / feature access level
Freemium-to-paid
→ trial_started
Free-tier limit hits that drive paid conversion
Hybrid (seat + usage)
→ compute_hours_used
Seats plus usage overage
Platform / marketplace
→ listing_published
Listings, storefronts, connected accounts, integrations
Revenue-share / take-rate
→ commission_calculated
Revenue processed, bookings, GMV through platform
Seat-based SaaS
→ seat_activated
Active seats / users
Storage-based SaaS
→ file_uploaded
GB stored, records managed, files hosted
Transaction / volume-based SaaS
→ payment_completed
Transactions processed, GMV, payments
Usage-based (metered) SaaS
→ job_completed
API calls, compute hours, messages, requests
Combined coverage (all models)
→ upgrade_clicked
Union of event types across all business models
Not sure which scenario to start with?
The PostHog Web baseline is the simplest. The combined-coverage scenario exercises every event type across every business model — good for stress-testing agents that need to generalize.
← Back to DryFit overview