worldseq

Lucent

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

Stable subscription income supports a privacy-focused analytics service. Reporting lags and inconsistent query windows now threaten trust more than outright downtime.

  • Legal
  • Hiring
  • Onboarding
  • Data recovery
  • 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
  • Attribution reports

Challenges

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

ChallengeHorizon
Separate payment delays from customer loss180 days
Fund service after annual prepayments90 days
Keep recovery evidence current180 days
Keep liquidity for the recovery bill90 days
Separate recurring value from spendable cash90 days
Reconcile the retention denominator30 days
Reconcile competing recovery revisions30 days
Honor an approved renewal exception90 days
Turn paid contracts into usable service90 days
Remove overhead without losing delivery staff90 days
Recover operator access before rollback30 days
Reserve cash for concentrated exposure30 days
Prioritize affected customer work30 days
Sequence staffing behind product readiness90 days
Pause a planned release during recovery30 days
Reach customers with a verified recovery handoff30 days
Sequence a payroll reduction90 days
Restore customers in feasible batches30 days
Replan around an external platform restriction90 days
Check the price denominator90 days
Invest in reusable restoration90 days
Balance restoration speed and retained work30 days
Keep an independent recovery route30 days
Repair now and prevent recurrence90 days
Staff the binding recovery queue30 days
Test the restoration route before relying on it30 days
Separate gross retention from expansion90 days
Verify the backup and its alert route30 days
Keep a reversal window during retirement30 days
Restore support access before allocating more work30 days
Separate acquisition changes from policy effects90 days
Choose a trial policy after the evidence matures90 days
Operate through weaker website demand365 days
Retain a reserve for dependency recovery180 days
Find a paying audience133 days
Recover from missing analytics data90 days
Recover the product roadmap365 days
Clear allowance-related 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,340,572.04
Starting accounts
1,500
Monthly overhead
$29,257.15
Monthly payroll
$165,790.52
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$390,095.34Day 45
Opening tax payable; the simulator does not calculate tax law$29,257.15Day 80
Opening receivables
Outstanding amounts owed to the company.
DescriptionAmountDue
Service already earned before the episode, awaiting collection$126,780.99Day 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
760
Service work units per day
6,230
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.
76$16,579.05
SalesSales work consumes this department's capacity and incurs its recurring cost.
45.6$9,947.43
EngineeringEngineering work consumes this department's capacity and incurs its recurring cost.
243.2$53,052.97
SupportSupport work consumes this department's capacity and incurs its recurring cost.
152$33,158.10
FinanceFinance work consumes this department's capacity and incurs its recurring cost.
60.8$13,263.24
PeoplePeople work consumes this department's capacity and incurs its recurring cost.
38$8,289.53
LegalLegal work consumes this department's capacity and incurs its recurring cost.
53.2$11,605.34
LeadershipLeadership work consumes this department's capacity and incurs its recurring cost.
91.2$19,894.86
Live dashboards
Monthly price per customer
$14.70
Monthly cost per customer
$5.39
Service work units per day
1,013
Warehouse export
Monthly price per customer
$24.50
Monthly cost per customer
$2.94
Service work units per day
758
Anomaly alerts
Monthly price per customer
$9.80
Monthly cost per customer
$1.72
Service work units per day
1,238
Attribution reports
Monthly price per customer
$31.85
Monthly cost per customer
$4.90
Service work units per day
518

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.