worldseq

Riff

Help creators and agencies publish approved content reliably across social channels.

Creators arrive through educational content but many never connect a second channel. The founder is choosing between more acquisition and completing first-week activation.

  • Legal
  • Hiring
  • Onboarding
  • Collections
  • Data recovery
  • Growth
  • Reliability
  • Finance
Explore challengesHow to play

What customers work with

  • Connected channels
  • Scheduled posts
  • Approval queues
  • Client workspaces
  • Approval workflow
  • Campaign reporting

Challenges

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

ChallengeHorizon
First channels before more traffic90 days
Finish the first publishing week90 days
Prepare for a creator launch year365 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
Correct a purchase order and match bank cash40 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
Avoid renewing a low-utilization minimum40 days
Find a paying audience101 days
Restore the service this week7 days
Reconcile this month's liquidity30 days
Separate signups from paid customers365 days
Price the creator promise180 days
Collect before committing the runway180 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
$492,752.04
Starting accounts
120
Monthly overhead
$6,159.40
Monthly payroll
$34,903.27
Variable cost per account / month
$4.50
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
$24.00
Trial period
14 days
Billing unit
Channel
Monthly base fee
$0.00
Monthly price per additional unit
$6.00
Default starting units per account
4
Included units
0
Opening obligations
Payments the company already owes when the challenge starts.
DescriptionAmountDue
Committed service-provider renewal$32,850.14Day 45
Opening tax payable; the simulator does not calculate tax law$6,159.40Day 80
Opening receivables
Outstanding amounts owed to the company.
DescriptionAmountDue
Service already earned before the episode, awaiting collection$26,690.74Day 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 creator
55% of the starting mix · 1–3 employees · 1–3 channels

Getting started

  1. Connect a channel
  2. Publish a scheduled post

When customers see value

Scheduled post published

Small business marketing team
30% of the starting mix · 5–50 employees · 3–8 channels

Getting started

  1. Connect business accounts
  2. Approve a weekly calendar

When customers see value

Weekly calendar completed

Multi-client agency
15% of the starting mix · 8–120 employees · 10–40 channels

Getting started

  1. Create client workspaces
  2. Secure client approval
  3. Publish across clients

When customers see value

Client calendar delivered

Operations

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

Starting capacity
Team hours per week
160
Service work units per day
246
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.
32$6,980.65
SalesSales work consumes this department's capacity and incurs its recurring cost.
12.8$2,792.26
EngineeringEngineering work consumes this department's capacity and incurs its recurring cost.
48$10,470.98
SupportSupport work consumes this department's capacity and incurs its recurring cost.
19.2$4,188.39
FinanceFinance work consumes this department's capacity and incurs its recurring cost.
12.8$2,792.26
PeoplePeople work consumes this department's capacity and incurs its recurring cost.
9.6$2,094.20
LegalLegal work consumes this department's capacity and incurs its recurring cost.
9.6$2,094.20
LeadershipLeadership work consumes this department's capacity and incurs its recurring cost.
16$3,490.33
Approval workflow
Monthly price per customer
$7.20
Monthly cost per customer
$2.64
Service work units per day
78
Campaign reporting
Depends on Workflow.
Monthly price per customer
$12.00
Monthly cost per customer
$1.44
Service work units per day
58

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
Channel billing
The synthetic paid plan charges for connected channels, with a fourteen-day trial.
Modeled
Buffer published pricing
Publishing dependencies
Publishing can fail by upstream provider and media type; authorization expiry and approval queues are catalog resources, not complete provider API implementations.
Context
Buffer AWS incident write-upBuffer Bluesky degradation write-up
Modeling notes
Assumptions and simplifications in this world.
  • Fictional customer and channel counts are authored, not Buffer customer microdata.
  • The engine executes channel-based billing; it does not implement real social posting APIs or Buffer's complete free plan.
  • 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.