worldseq

Flare

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

The company is moving from creators to multi-client teams while carrying legacy price commitments. Sales requests could displace self-service product work.

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

What customers work with

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

Challenges

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

ChallengeHorizon
Sequence agency commercial readiness180 days
Sequence acquisition around collection101 days
Adapt beyond independent creators90 days
Staff the multi-client transition180 days
Choose the next commercial investment90 days
Reprice without losing the creator base365 days
Rebuild the annual agency transition plan365 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
$1,693,835.10
Starting accounts
480
Monthly overhead
$16,938.35
Monthly payroll
$95,983.99
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
$120.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
20
Included units
0
Opening obligations
Payments the company already owes when the challenge starts.
DescriptionAmountDue
Committed service-provider renewal$124,214.57Day 45
Opening tax payable; the simulator does not calculate tax law$16,938.35Day 80
Opening receivables
Outstanding amounts owed to the company.
DescriptionAmountDue
Service already earned before the episode, awaiting collection$73,399.52Day 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
440
Service work units per day
763
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.
61.6$13,437.76
SalesSales work consumes this department's capacity and incurs its recurring cost.
44$9,598.40
EngineeringEngineering work consumes this department's capacity and incurs its recurring cost.
105.6$23,036.16
SupportSupport work consumes this department's capacity and incurs its recurring cost.
61.6$13,437.76
FinanceFinance work consumes this department's capacity and incurs its recurring cost.
44$9,598.40
PeoplePeople work consumes this department's capacity and incurs its recurring cost.
35.2$7,678.72
LegalLegal work consumes this department's capacity and incurs its recurring cost.
35.2$7,678.72
LeadershipLeadership work consumes this department's capacity and incurs its recurring cost.
52.8$11,518.07
Approval workflow
Monthly price per customer
$36.00
Monthly cost per customer
$13.20
Service work units per day
312
Campaign reporting
Monthly price per customer
$60.00
Monthly cost per customer
$7.20
Service work units per day
230
Asset library
Monthly price per customer
$24.00
Monthly cost per customer
$4.20
Service work units per day
384

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.