worldseq

Vela

Give product teams an integrated analytics, experimentation and observability toolkit.

A stable developer-tool portfolio must maintain data quality during ingestion bursts. Some customers see several products as one critical operational dependency.

  • Hiring
  • Growth
  • Reliability
  • Finance
Explore challengesHow to play

What customers work with

  • Event batches
  • Enabled products
  • Feature flags
  • Billing limits
  • Feature flags
  • Session replay
  • Error monitoring
  • Experiment analysis

Challenges

7 published briefs. Each describes the decision to make, the time available, and the constraints on a successful outcome.

ChallengeHorizon
Preserve cash through usage billing disruption180 days
Operate through a developer-demand slowdown365 days
Reserve resources for ingestion dependencies180 days
Find a paying audience115 days
Recover ingestion with incomplete reporting90 days
Restart the devtools roadmap365 days
Clear metered-product support pressure90 days

Starting financials

The company before the challenge begins. These are authored starting conditions in USD; results from a particular attempt belong to that run.

Starting finances
USD amounts before a challenge begins.
Opening cash
$2,956,512.00
Starting accounts
1,200
Monthly overhead
$36,956.40
Monthly payroll
$209,419.60
Variable cost per account / month
$26.00
Pricing and billing
Subscription price before usage adjustments. Actual charges depend on usage and the plan’s billing policy.
Billing model
Usage tiers
Starting subscription price
$99.00
Trial period
21 days
Billing unit
Event
Listed usage rate
$0.25
Included units
1,000
Opening obligations
Payments the company already owes when the challenge starts.
DescriptionAmountDue
Committed service-provider renewal$492,752.00Day 45
Opening tax payable; the simulator does not calculate tax law$36,956.40Day 80
Opening receivables
Outstanding amounts owed to the company.
DescriptionAmountDue
Service already earned before the episode, awaiting collection$160,144.40Day 12

Customers

Who uses the product, what getting started involves, and what makes it useful.

The starting customer mix. Shares describe the modeled audience, not an exact customer count. Getting-started steps describe each customer archetype. Available actions and task objectives define which activities are simulated.

Independent builder
60% of the starting mix · 1–5 employees · 1–10 events

Getting started

  1. Install an SDK
  2. Inspect a first event

When customers see value

First diagnostic query

Product engineering team
30% of the starting mix · 10–200 employees · 20–150 events

Getting started

  1. Instrument a product
  2. Configure a feature flag
  3. Evaluate an experiment

When customers see value

Experiment decision recorded

Platform organization
10% of the starting mix · 100–2,000 employees · 200–1,000 events

Getting started

  1. Agree data pipeline ownership
  2. Enable multiple products
  3. Set billing limits

When customers see value

Production observability used

Operations

Team capacity, recurring costs, and products that depend on one another.

Starting capacity
Team hours per week
960
Service work units per day
62,700
Team
Each department shares its available time across company work.
DepartmentHours / weekMonthly payroll
GrowthGrowth work consumes this department's capacity and incurs its recurring cost.
96$20,941.96
SalesSales work consumes this department's capacity and incurs its recurring cost.
57.6$12,565.18
EngineeringEngineering work consumes this department's capacity and incurs its recurring cost.
307.2$67,014.27
SupportSupport work consumes this department's capacity and incurs its recurring cost.
192$41,883.92
FinanceFinance work consumes this department's capacity and incurs its recurring cost.
76.8$16,753.57
PeoplePeople work consumes this department's capacity and incurs its recurring cost.
48$10,470.98
LegalLegal work consumes this department's capacity and incurs its recurring cost.
67.2$14,659.37
LeadershipLeadership work consumes this department's capacity and incurs its recurring cost.
115.2$25,130.35
Feature flags
Monthly price per customer
$29.70
Monthly cost per customer
$10.89
Service work units per day
900
Session replay
Depends on Workflow.
Monthly price per customer
$49.50
Monthly cost per customer
$5.94
Service work units per day
696
Error monitoring
Depends on Workflow.
Monthly price per customer
$19.80
Monthly cost per customer
$3.47
Service work units per day
1,080
Experiment analysis
Depends on Insights, Archive.
Monthly price per customer
$64.35
Monthly cost per customer
$9.90
Service work units per day
504

Sources and modeling limits

Public operating material grounds the mechanics. It does not make this fictional company a measured reproduction of a real business.

Public sources behind this fictional company. Modeled rules affect the simulation; context explains the business it draws from.

Payment ledger
An invoice, attempted payment and collected cash are distinct records; refunds cannot exceed the collected charge.
Modeled
Stripe refundsSaaS Subscriptions and Customer Churn v1.0.0
Provider delivery
Provider webhooks can be delayed, duplicated or reordered. This catalog's reporting lag is an approximation of visibility, not a complete Stripe webhook emulator.
Context
Stripe webhook deliveryStripe subscription webhook behavior
Usage billing
The synthetic paid account has an included monthly event-batch allowance and charges excess units.
Modeled
PostHog product analytics pricing
Product portfolio
Independent product adoption and product-level budgets are represented as resources; the initial engine aggregates their billing into one account meter.
Context
PostHog product analytics pricing
Modeling notes
Assumptions and simplifications in this world.
  • One synthetic meter unit is a batch of 1,000 events. Price and allowance are authored, not a copy of PostHog pricing.
  • The twenty-one-day paid evaluation is fictional; it does not claim that PostHog's real permanent free allowance expires.
  • Company populations, segment shares, staffing, compensation and behavioral coefficients are authored sensitivity inputs, not observed records from the reference businesses.
  • Paid core-capacity quotes reuse the authored normalized-unit terms in growth-model.json: setup, delivery delay, upfront payment and recurring hosting are enforced. AWS guidance grounds provisioning mechanics, not these fictional prices or throughput coefficients.
  • Company populations, payroll, adoption, churn, obligations and incident probabilities are explicit authored sensitivity inputs; public sources ground mechanisms, not transferable effect estimates.
  • All eight departments have enforced capacity and recurring costs. Paid addon products have independent billing, capacity and dependency graphs against the same economic customer identities.
  • Activation checklists and named value events describe customer archetypes, not individually tracked product actions. Generic onboarding work changes conversion behavior; explicit delivery hours and readiness requirements apply only where a company or task configures onboarding mechanics.
  • Opening receivables were earned before day zero. Cash, earned service, deferred revenue and dated liabilities reconcile separately. Initial cash covers the stated authored runway before customer receipts and obligations.