Standard architecture: Software & SaaS
How information is recorded, decided on and fed back. Mostly data and decisions, with information fed back.
Standard architectureThe parts at least half of the organizations in Software & SaaS have, as many as 13 of them run all together. Counted from public, sourced parts only; each organization below links to the parts it was counted on.
- Organizations running it
- 13
- Of their industry
- 42%
The pattern
What every instance has, in order
- DecisionsMarket and positioningin 100% of instancesthen
- ProcessProduct or service designin 100% of instancesthen
- DecisionsGovernance and decision rightsin 100% of instances
Coloured arrows: a flow of that type seen between the two at instance organizations. Grey arrows: order only.
Structure
Element
Share of instances
Companies
Variant · where they differ
Member
Variants, couplings and instances
Every level, number, source and dimension: Member, $300 a year.
Couplings · what comes together
Member
Variants, couplings and instances
Every level, number, source and dimension: Member, $300 a year.
Entropy
Where it runs rough
Operating-reality findings at instance companies: workarounds, manual hand-offs, bottlenecks.
- Suppliers and partners2 findingsDependency 1 · Dependency (public record) 1 · at 2 companies
- Governance and decision rights1 findingDependency 1 · at 1 company
Seen across
Where it holds
Industries
Business model
- subscription46%
- product8%
Size
- 1000+ people15%
- 201-500 people8%
Region
- United States69%
- Australia8%
- China8%
- France8%
- United Arab Emirates8%
Instances
The 13 companies it was seen at
Member
Variants, couplings and instances
Every level, number, source and dimension: Member, $300 a year.