Software sold as a product or a subscription. This is its own schema, version 2.
© 2026 System Atlas · Built by MIOSA
Free to map your own company · Members $300 a yearHow automatable each primitive is, estimated from the 160 organizations mapped in public on the Software & SaaS schema: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.
| Primitive | Layer | Automation | Peers on software | Software parts named most |
|---|---|---|---|---|
Quotes and order forms Demand: winning customers | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Sprint and capacity planning Supply: making or delivering the offer | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Procurement Supply: making or delivering the offer | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Running the service Supply: making or delivering the offer | Process | MediumLayer only | 4 of 160 mapped; too few to read | Compute (agent sandboxes) (1) |
Testing and QA Supply: making or delivering the offer | Process | MediumLayer only | 2 of 160 mapped; too few to read | — |
Code, infrastructure and licences Supply: making or delivering the offer | Data | MediumLayer only | 2 of 160 mapped; too few to read | — |
Provisioning Supply: making or delivering the offer | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Engineering delivery Supply: making or delivering the offer | Process | MediumLayer only | 1 of 160 mapped; too few to read | — |
Releases and change communication Supply: making or delivering the offer | Process | MediumLayer only | 4 of 160 mapped; too few to read | — |
Uptime and incidents Supply: making or delivering the offer | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Implementation Customers: keeping them | Process | MediumLayer only | 2 of 160 mapped; too few to read | — |
Renewals Customers: keeping them | Process | MediumLayer only | 3 of 160 mapped; too few to read | Your Turn and We Met (1) |
Onboarding and activation Customers: keeping them | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Invoicing Money: getting paid and paying | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Collections and receivables Money: getting paid and paying | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Payments and payables Money: getting paid and paying | Process | MediumLayer only | 1 of 160 mapped; too few to read | — |
Payroll Money: getting paid and paying | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Cash and treasury Money: getting paid and paying | Data | MediumLayer only | 0 of 160 mapped; too few to read | — |
Unit economics Money: getting paid and paying | Data | MediumLayer only | 0 of 160 mapped; too few to read | — |
Cloud and hosting costs Money: getting paid and paying | Data | MediumLayer only | 1 of 160 mapped; too few to read | — |
Hiring People: who does the work | Process | MediumLayer only | 4 of 160 mapped; too few to read | — |
Onboarding and training People: who does the work | Process | MediumLayer only | 1 of 160 mapped; too few to read | — |
Scheduling and capacity People: who does the work | Process | MediumLayer only | 1 of 160 mapped; too few to read | — |
Data management Systems: tools and data | Data | MediumLayer only | 1 of 160 mapped; too few to read | — |
Product analytics Systems: tools and data | Data | MediumLayer only | 4 of 160 mapped; too few to read | Reporting and Analytics (incl. Premium Analytics) (1) |
Legal and contracts administration Control: rules the company runs under | Data | MediumLayer only | 1 of 160 mapped; too few to read | — |
Management cadence Direction: deciding where it goes | Process | MediumLayer only | 0 of 160 mapped; too few to read | — |
Learning and improvement Direction: deciding where it goes | Process | MediumLayer only | 2 of 160 mapped; too few to read | — |
The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.
Counts of what public research has found and sourced, each part with its source on the organization’s profile. They say what is known, not how much of the industry exists.
Focused research on the organizations with the fewest mapped parts in software & saas; what it finds is public for everyone.