worldseq

Anvil

Help engineering organizations adopt a governed software-delivery platform.

A developer platform has a few technical champions and several procurement-stage evaluations. Revenue targets arrive before implementation benefits are visible.

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

What customers work with

  • Licensed seats
  • Developer projects
  • Security reviews
  • Success plans
  • Build pipelines
  • Compliance reports

Challenges

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

ChallengeHorizon
Acquire opportunities that can finish procurement90 days
Unblock the first developer deployment90 days
Build capacity before developer-team growth365 days
Core deployment acceptance and earned settlement35 days
Convert earned enterprise contracts into cash90 days
Core deployment acceptance and SLA credit evidence35 days
Resolve the cross-border contracting gate90 days
Deployment and artifact specialists with a new hire60 days
Deployment and artifact specialists60 days
Find a paying audience221 days
Restore the service this week7 days
Reconcile this month's liquidity30 days
Distinguish pipeline from paid deployment365 days
Price the initial seat contract180 days
Protect runway across a long commercial cycle180 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
$985,504.08
Starting accounts
32
Monthly overhead
$12,318.80
Monthly payroll
$69,806.54
Variable cost per account / month
$160.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
$580.00
Trial period
30 days
Billing unit
Seat
Monthly base fee
$0.00
Monthly price per additional unit
$29.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$65,700.27Day 45
Opening tax payable; the simulator does not calculate tax law$12,318.80Day 80
Opening receivables
Outstanding amounts owed to the company.
DescriptionAmountDue
Service already earned before the episode, awaiting collection$53,381.47Day 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.

Startup engineering team
45% of the starting mix · 10–60 employees · 5–20 seats

Getting started

  1. Connect repositories
  2. Run a production workflow

When customers see value

Production workflow completed

Midmarket engineering organization
40% of the starting mix · 100–1,000 employees · 30–150 seats

Getting started

  1. Approve security review
  2. Sign an order
  3. Migrate teams

When customers see value

Production seat activation

Enterprise platform organization
15% of the starting mix · 1,000–10,000 employees · 200–800 seats

Getting started

  1. Approve security review
  2. Agree contract exceptions
  3. Pilot a department
  4. Expand adoption

When customers see value

Department rollout verified

Operations

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

Starting capacity
Team hours per week
320
Service work units per day
69
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.
64$13,961.31
SalesSales work consumes this department's capacity and incurs its recurring cost.
25.6$5,584.52
EngineeringEngineering work consumes this department's capacity and incurs its recurring cost.
96$20,941.96
SupportSupport work consumes this department's capacity and incurs its recurring cost.
38.4$8,376.78
FinanceFinance work consumes this department's capacity and incurs its recurring cost.
25.6$5,584.52
PeoplePeople work consumes this department's capacity and incurs its recurring cost.
19.2$4,188.39
LegalLegal work consumes this department's capacity and incurs its recurring cost.
19.2$4,188.39
LeadershipLeadership work consumes this department's capacity and incurs its recurring cost.
32$6,980.67
Build pipelines
Monthly price per customer
$174.00
Monthly cost per customer
$63.80
Service work units per day
23
Compliance reports
Monthly price per customer
$290.00
Monthly cost per customer
$34.80
Service work units per day
18

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 and procurement
The synthetic contract bills licensed seats and imposes a thirty-day procurement gate before paid conversion.
Modeled
ChartMogul SaaS GTM reportGitLab sales order processing
Success handoff
Presales handoff precedes customer kickoff; the referenced 14/30/45-day milestones are operating targets, not realized duration distributions.
Context
GitLab customer onboarding
Quote authority
Nonstandard quotes and agreements require the appropriate approval owner; the full legal document workflow is descriptive.
Context
GitLab sales order processing
Modeling notes
Assumptions and simplifications in this world.
  • Pricing, customer sizes and procurement duration are fictional contract choices.
  • Seat billing and a conversion delay execute; full GitLab source control, security and legal workflows do not.
  • 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.