worldseq

Quarry

Provide trustworthy website and conversion reporting for small teams and agencies.

Commerce customers are growing traffic and asking for richer conversion reports. The company must distinguish temporary traffic peaks from sustainable usage upgrades.

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

What customers work with

  • Tracked sites
  • Event batches
  • Conversion goals
  • Shared dashboards
  • Live dashboards
  • Warehouse export
  • Anomaly alerts

Challenges

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

ChallengeHorizon
Rebalance a slow acquisition quarter180 days
Grow agency analytics without choking ingestion90 days
Reallocate after mature evidence133 days
Save the analytics renewal cohort90 days
Manage a year of allowance pressure365 days
Choose sales growth or instrumentation help180 days
Pay for analytics growth sustainably365 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,012,070.76
Starting accounts
820
Monthly overhead
$21,557.90
Monthly payroll
$122,161.44
Variable cost per account / month
$9.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
$49.00
Trial period
30 days
Billing unit
Event
Listed usage rate
$0.00
Included units
100
Opening obligations
Payments the company already owes when the challenge starts.
DescriptionAmountDue
Committed service-provider renewal$201,207.08Day 45
Opening tax payable; the simulator does not calculate tax law$21,557.90Day 80
Opening receivables
Outstanding amounts owed to the company.
DescriptionAmountDue
Service already earned before the episode, awaiting collection$93,417.57Day 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 site owner
60% of the starting mix · 1–5 employees · 1–4 events

Getting started

  1. Install tracking
  2. Verify first incoming events

When customers see value

First verified report

Commerce marketing team
25% of the starting mix · 10–150 employees · 5–20 events

Getting started

  1. Install tracking
  2. Configure revenue goals
  3. Reconcile campaign totals

When customers see value

Campaign report reconciled

Analytics agency
15% of the starting mix · 5–80 employees · 20–80 events

Getting started

  1. Add client sites
  2. Invite client stakeholders
  3. Deliver reports

When customers see value

Client report delivered

Operations

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

Starting capacity
Team hours per week
560
Service work units per day
4,087
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.
123.2$26,875.52
SalesSales work consumes this department's capacity and incurs its recurring cost.
84$18,324.22
EngineeringEngineering work consumes this department's capacity and incurs its recurring cost.
140$30,540.36
SupportSupport work consumes this department's capacity and incurs its recurring cost.
67.2$14,659.37
FinanceFinance work consumes this department's capacity and incurs its recurring cost.
33.6$7,329.69
PeoplePeople work consumes this department's capacity and incurs its recurring cost.
28$6,108.07
LegalLegal work consumes this department's capacity and incurs its recurring cost.
28$6,108.07
LeadershipLeadership work consumes this department's capacity and incurs its recurring cost.
56$12,216.14
Live dashboards
Monthly price per customer
$14.70
Monthly cost per customer
$5.39
Service work units per day
554
Warehouse export
Depends on Workflow.
Monthly price per customer
$24.50
Monthly cost per customer
$2.94
Service work units per day
414
Anomaly alerts
Depends on Workflow.
Monthly price per customer
$9.80
Monthly cost per customer
$1.72
Service work units per day
677

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
Traffic grace
Two consecutive billing periods over the allowance lead to an upgrade notice and seven-day grace period before restriction.
Modeled
Plausible subscription plans
Trial
A thirty-day trial does not require a payment method.
Modeled
Plausible subscription plans
Query semantics
Visitor totals depend on requested metrics and report windows; the real provider's 600-request hourly API quota is descriptive here.
Context
Plausible Stats API
Modeling notes
Assumptions and simplifications in this world.
  • A billing event unit represents a synthetic batch of 1,000 incoming events; this scale is authored and explicit.
  • The engine enforces usage grace but does not implement a full analytics query engine or exact provider proration.
  • 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.