Standard architecture: Consumer apps
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 Consumer apps have, as many as 5 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
- 5
- Of their industry
- 100%
The pattern
What every instance has, in order
- DecisionsMarket and positioningin 100% of instancesmoney
- DecisionsPricingin 100% of instancesthen
- ProcessProduct or service designin 100% of instancesthen
- PeopleOrg structurein 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
Retention and renewal
40%
2
Lead generation
20%
1
Quality control
20%
1
Scheduling and capacity
20%
1
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 partners1 findingDependency (public record) 1 · at 1 company
Seen across
Where it holds
Industries
- Consumer apps100%
Business model
- subscription100%
Size
- 1000+ people20%
- 201-500 people20%
Region
- United States80%
- Australia20%
Instances
The 5 companies it was seen at
Member
Variants, couplings and instances
Every level, number, source and dimension: Member, $300 a year.