System Atlas

Chaosium

CompanySoftware PublishersMapped from public sources

Chaosium is a company in software publishers, based in United States.

Its public map holds 1 components across 9 parts of the business, 0 flows and 2 recorded numbers, drawn from 1 open-web source. Who stands behind each item: 3 from the system atlas registry.

Layer health
What is known, per layer
  • People0 of 5 primitives
  • Process0 of 23 primitives
  • Software0 of 5 primitives
  • Data0 of 10 primitives
  • Decisions0 of 15 primitives

01How it is built

Open any part to see its primitives and how many components sit in each. Pick a node for its flows, drag to move, pinch or scroll to zoom, or go full screen.

Sign in free to see the full public map

You are seeing the 9 parts and their primitives. A free account opens all 1 components, 2 numbers and 0 flows, each with its source.

Every primitive inside its part of the business

View
Navigate
Lens
Part of the businessDemand: winningcustomers0 of 6 mappedPart of the businessSupply: making ordelivering theoffer0 of 12 mappedPart of the businessCustomers: keepingthem0 of 7 mappedPart of the businessMoney: gettingpaid and paying0 of 10 mappedPart of the businessPeople: who doesthe work0 of 6 mappedPart of the businessSystems: tools anddata0 of 7 mappedPart of the businessControl: rules thecompany runs under0 of 6 mappedPart of the businessDirection:deciding where itgoes0 of 4 mappedPart of the businessSpecific to thiscompany1 of 1 mappedIdeal customer and positioningNot mapped yetPipeline generationNot mapped yetSalesNot mapped yetPackaging and pricingNot mapped yetQuotes and order formsNot mapped yetSubscription agreementsNot mapped yetProduct managementNot mapped yetSprint and capacity planningNot mapped yetProcurementNot mapped yetSuppliers and partnersNot mapped yetRunning the serviceNot mapped yetTesting and QANot mapped yetCode, infrastructure a…Not mapped yetProvisioningNot mapped yetProduct roadmapNot mapped yetEngineering deliveryNot mapped yetReleases and chan…Not mapped yetUptime and incidentsNot mapped yetImplementationNot mapped yetCustomer supportNot mapped yetCustomer successNot mapped yetCustomer dataNot mapped yetRenewalsNot mapped yetOnboarding and activationNot mapped yetChurn and expansionNot mapped yetInvoicingNot mapped yetCollections and receivablesNot mapped yetPayments and payablesNot mapped yetPayrollNot mapped yetRevenue recognition and closeNot mapped yetPlan and burnNot mapped yetCash and treasuryNot mapped yetSubscription billingNot mapped yetUnit economicsNot mapped yetCloud and hosting costsNot mapped yetOrg structureNot mapped yetHiringNot mapped yetOnboarding and trainingNot mapped yetPerformance and payNot mapped yetScheduling and capacityNot mapped yetPolicies and cultureNot mapped yetCore system of recordNot mapped yetCommunication toolsNot mapped yetIntegrationsNot mapped yetMetrics and board reportingNot mapped yetData managementNot mapped yetSecurity and accessNot mapped yetProduct analyticsNot mapped yetLicences and registrationsNot mapped yetRegulatory complianceNot mapped yetInsurance and riskNot mapped yetLegal and contrac…Not mapped yetHealth, safety and environmentNot mapped yetData protection and securi…Not mapped yetStrategy and goalsNot mapped yetGovernance and decision rightsNot mapped yetManagement cadenceNot mapped yetLearning and improvementNot mapped yetComponent · lockedMember
Dimensions
What the map shows most
  • Information100%
  • Technical70%
  • Energy20%
  • EconomicNot seen
  • TimeNot seen
  • HumanNot seen
  • PowerNot seen
  • EntropyNot seen
  • ScaleNot seen
  • SpatialNot seen
Reading the map
What each box means
  • VerifiedConfirmed by the organization or a primary source
  • Self-reportedStated by the organization, not checked
  • InferredRead from public signals by research
  • Not mappedPart of the industry schema, nothing found yet
  • LockedExists on the map; opens with a free account or as a Member

02Parts of the business

Each part of the business with the primitives in it: how many components the public map holds for each, and which are not mapped yet.

  • Demand: winning customers

    0 of 6 mapped
    • Ideal customer and positioningNot mapped
    • Pipeline generationNot mapped
    • SalesNot mapped
    • Packaging and pricingNot mapped
    • Quotes and order formsNot mapped
    • Subscription agreementsNot mapped
  • Supply: making or delivering the offer

    0 of 12 mapped
    • Product managementNot mapped
    • Sprint and capacity planningNot mapped
    • ProcurementNot mapped
    • Suppliers and partnersNot mapped
    • Running the serviceNot mapped
    • Testing and QANot mapped
    • Code, infrastructure and licencesNot mapped
    • ProvisioningNot mapped
    • Product roadmapNot mapped
    • Engineering deliveryNot mapped
    • Releases and change communicationNot mapped
    • Uptime and incidentsNot mapped
  • Customers: keeping them

    0 of 7 mapped
    • ImplementationNot mapped
    • Customer supportNot mapped
    • Customer successNot mapped
    • Customer dataNot mapped
    • RenewalsNot mapped
    • Onboarding and activationNot mapped
    • Churn and expansionNot mapped
  • Money: getting paid and paying

    0 of 10 mapped
    • InvoicingNot mapped
    • Collections and receivablesNot mapped
    • Payments and payablesNot mapped
    • PayrollNot mapped
    • Revenue recognition and closeNot mapped
    • Plan and burnNot mapped
    • Cash and treasuryNot mapped
    • Subscription billingNot mapped
    • Unit economicsNot mapped
    • Cloud and hosting costsNot mapped
  • People: who does the work

    0 of 6 mapped
    • Org structureNot mapped
    • HiringNot mapped
    • Onboarding and trainingNot mapped
    • Performance and payNot mapped
    • Scheduling and capacityNot mapped
    • Policies and cultureNot mapped
  • Systems: tools and data

    0 of 7 mapped
    • Core system of recordNot mapped
    • Communication toolsNot mapped
    • IntegrationsNot mapped
    • Metrics and board reportingNot mapped
    • Data managementNot mapped
    • Security and accessNot mapped
    • Product analyticsNot mapped
  • Control: rules the company runs under

    0 of 6 mapped
    • Licences and registrationsNot mapped
    • Regulatory complianceNot mapped
    • Insurance and riskNot mapped
    • Legal and contracts administrationNot mapped
    • Health, safety and environmentNot mapped
    • Data protection and security assuranceNot mapped
  • Direction: deciding where it goes

    0 of 4 mapped
    • Strategy and goalsNot mapped
    • Governance and decision rightsNot mapped
    • Management cadenceNot mapped
    • Learning and improvementNot mapped
  • Specific to this company

    1 of 1 mapped
    • Outside the industry schema1 component

The 1 components behind these counts, with what each one is and where it was found, are on the full public map.Sign in free to see it

03Software and interfaces

The systems the organization runs on, as the public map records them, and screens of its product found on the open web or published by it.

No software is on the public map yet.

04Flows

What moves between the parts of the business: money, information, work, material, energy and control. Select a node on the map and switch to Flows to follow one.

No flows are on the public map yet.

05Key figures

The numbers on the public map, each with how sure it is and the page it came from.

No figures are public yet. Unknown, not zero.

06Sources and evidence

Only what anyone could find on the open web appears here: company sites, job boards, reviews, registries and press. Private material never shows on a public page.

Evidence
How sure each item is
  • Verified0
  • Self-reported0
  • Inferred3
  • Low confidence0
Sources most relied on
  • wikidata.org3 items
Research runs
None recorded
Last run
None recorded
Contributors
None recorded
Agent uploads
None recorded
Pages read
None recorded
Open-web sources cited
1

07Similar organizations

Others in software publishers first, then other companies.

08Claim or correct