worldseq

Fable

Coordinate recurring work across departments with visible ownership and approvals.

An established operations platform supports recurring processes across departments. Support and finance want to protect renewal quality while leadership improves efficiency.

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

What customers work with

  • Licensed seats
  • Workspaces
  • Approval requests
  • Recurring workflows
  • Project boards
  • Team scheduling
  • Approval inbox
  • Resource planning

Challenges

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

ChallengeHorizon
Stabilize team subscription collections180 days
Survive a weaker team acquisition year365 days
Retain a reserve for workflow dependencies180 days
Prepare service before expansion143 days
Restore recurring workflows during reporting lag90 days
Restart the collaboration roadmap365 days
Recover a team support backlog90 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,463,760.08
Starting accounts
850
Monthly overhead
$30,797.00
Monthly payroll
$174,516.34
Variable cost per account / month
$18.00
Pricing and billing
The reference price uses the default starting quantity. Each account’s bill depends on its subscribed units and offer.
Billing model
Per unit
Reference monthly price
$283.00
Trial period
14 days
Billing unit
Seat
Monthly base fee
$19.00
Monthly price per additional unit
$12.00
Default starting units per account
25
Included units
3
Opening obligations
Payments the company already owes when the challenge starts.
DescriptionAmountDue
Committed service-provider renewal$410,626.68Day 45
Opening tax payable; the simulator does not calculate tax law$30,797.00Day 80
Opening receivables
Outstanding amounts owed to the company.
DescriptionAmountDue
Service already earned before the episode, awaiting collection$133,453.67Day 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.

Small operations team
55% of the starting mix · 5–30 employees · 3–12 seats

Getting started

  1. Create a workspace
  2. Invite colleagues
  3. Complete a shared workflow

When customers see value

Shared workflow completed

Business department
35% of the starting mix · 50–500 employees · 15–80 seats

Getting started

  1. Define approval owners
  2. Import work
  3. Complete a cross-team process

When customers see value

Approval cycle completed

Cross-department deployment
10% of the starting mix · 300–3,000 employees · 100–400 seats

Getting started

  1. Approve procurement
  2. Align department owners
  3. Roll out recurring workflows

When customers see value

Multi department cycle completed

Operations

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

Starting capacity
Team hours per week
800
Service work units per day
1,140
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.
80$17,451.63
SalesSales work consumes this department's capacity and incurs its recurring cost.
48$10,470.98
EngineeringEngineering work consumes this department's capacity and incurs its recurring cost.
256$55,845.23
SupportSupport work consumes this department's capacity and incurs its recurring cost.
160$34,903.27
FinanceFinance work consumes this department's capacity and incurs its recurring cost.
64$13,961.31
PeoplePeople work consumes this department's capacity and incurs its recurring cost.
40$8,725.82
LegalLegal work consumes this department's capacity and incurs its recurring cost.
56$12,216.14
LeadershipLeadership work consumes this department's capacity and incurs its recurring cost.
96$20,941.96
Project boards
Monthly price per customer
$84.90
Monthly cost per customer
$31.13
Service work units per day
659
Team scheduling
Monthly price per customer
$141.50
Monthly cost per customer
$16.98
Service work units per day
514
Approval inbox
Monthly price per customer
$56.60
Monthly cost per customer
$9.91
Service work units per day
786
Resource planning
Monthly price per customer
$183.95
Monthly cost per customer
$28.30
Service work units per day
378

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
Seat contract
The authored contract includes three seats plus a base fee; additional seats are billable and new purchases have a seven-day procurement gate.
Modeled
ChartMogul SaaS GTM reportGitLab sales order processing
Adoption vs license
Licensed seats and participating teammates are different observations; completion of an onboarding checklist does not prove realized workflow value.
Context
GitLab customer onboarding
Modeling notes
Assumptions and simplifications in this world.
  • This is an authored generic seat-collaboration archetype. No specific company's complete operating history is claimed.
  • GitLab provides analogous procurement/adoption evidence, not direct empirical calibration for collaboration software.
  • 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.