Scaling Without Size
Platforms1 drive the advantage of federating social technologies.
In From ETO to CTO, we argued that the construction industry must move away from bespoke project delivery and toward a Configure-to-Order marketplace. In What Modularity Really Means, we argued that this shift depends on shared interfaces. In Mated Physical & Social Technologies, we argued that those interfaces must be supported by social technologies such as contracts, standards, and approval pathways. This essay asks what kind of industry structure becomes possible once those conditions are in place.
In conventional economic thinking, growth is often measured by scale (more capital, more labor, more control). But in complex systems, size is a poor proxy for capacity. What matters more is the ability to coordinate complexity.
Herbert Simon showed that complex systems function more effectively when they are structured hierarchically 2 and exhibit near-decomposability.3 In such systems, subsystems are internally cohesive but only loosely coupled to one another. That makes the whole easier to evolve, repair, and scale. Hierarchy, in this sense, is not merely top-down control. It is nature’s answer to bounded rationality.4 No actor can understand or manage an entire complex system at once.5 (Sorry, architects.)
Modularity is what makes this arrangement work in practice. By separating systems into parts with defined interfaces, organizations create the conditions for specialization, iteration, and parallel development. Just as importantly, they allow smaller actors to contribute meaningfully to larger systems without taking responsibility for the whole.
These ideas apply not only to biological or digital systems, but to industry. The most effective collaborations often emerge not from central planning, but from modular trust: social technologies that establish clear interfaces, predictable roles, and contractable behaviors. Legal agreements, code pathways, platform standards, and interface specifications all help distributed actors function like parts of a larger whole. When these rules are well designed, firms can access some of the benefits of scale (efficiency, coherence, and market credibility) without merging into a single entity.
In construction, however, these principles are rarely operationalized.
Most large multifamily buildings are still delivered through bespoke contracts with a constellation of subcontractors. A plumbing subcontractor, for example, may be responsible for basement equipment, vertical risers, and the fine-grain detailing inside each dwelling unit. That span of responsibility crosses multiple levels of scale and abstraction, imposing heavy overhead in coordination, liability, and design reconciliation.
This model reflects an older social technology, shaped by craft and trade disciplines rather than modular product design. It is robust in some ways, but brittle in others. Every project becomes a new act of integration. Coordination costs stay high. Redundancy proliferates. Even technically sophisticated small firms remain constrained by the limits of their contractual and organizational reach.
A new social technology is now emerging, one that organizes construction not around trades, but around modular products and interfaces. The Modular Interface Standard enables a hierarchy grounded in Simon’s principle of near-decomposability. A bathroom pod manufacturer can focus on a single level of scale: the bathroom. It does not need to master the vertical risers or the mechanical room. Its responsibilities are bounded by the pod envelope and predefined connection points.
Modular apartment producers, in turn, can treat these pods as reliable, pluggable components. They can optimize stacking, framing, layout, and logistics with confidence that the embedded bathroom system conforms to shared tolerances, interfaces, and service expectations. Because the interfaces are stable, technical integration becomes more predictable. Business relationships become simpler. Trust shifts from legacy familiarity to adherence to shared standards.
This division of labor is not fragmentation; it is federation. Firms that participate in this system retain their independence but gain access to the advantages typically reserved for larger entities: access to high-value contracts, increased project visibility, and reputational trust. From a strategic perspective, pod and panel firms that conform to the standard begin to act like business units of avirtual conglomerate.6 Without incurring the overhead of vertical integration, they achieve the functional benefits of scale—repeatability, coordination, and market credibility.
Capital (whether deployed by a public agency or a private investor) wants both freedom and efficiency. It seeks the liberty to allocate resources flexibly, chasing opportunity, while also demanding the streamlined performance of a well-tuned machine. Yet in practice, these desires are inherently at odds: freedom thrives on optionality and diversity, while efficiency depends on narrowing choices and locking in predictable processes. The power of well-designed interface standards is that they reconcile part of this contradiction — preserving freedom at the level of the market while delivering efficiency at the level of the transaction.
What emerges is a distributed but cohesive industry structure. Firms at each scale level (pods, modules, or full buildings) can specialize, improve, and iterate without waiting for top-down integration. The system becomes more evolvable, less brittle, and better suited to the demands of speed, affordability and quality.7
At the Center for Offsite Construction, we see interface standards not just as technical protocols, but as tools for strategic organization. They allow firms to transcend their size, reduce the friction of collaboration, and participate in larger markets with greater confidence. In a complex industry, the ability to scale without size may be one of the most important innovations of all.
To learn more about how the CfOC is helping smaller offsite firms gain the advantages of scale through shared standards, clearer roles, and repeatable coordination:
- To see how smaller pod, panel, and module firms can coordinate through shared connection points instead of bespoke negotiation, see the CfOC-ICC-1220 work at “Modular Interoperability & Interface Standard” or the CfOC-ICC-1230 work at “Panel Interface Standard“
- To see how this kind of federation eventually becomes a real commercial ecosystem rather than a one-off team, explore “Software Configurator – Marketplace of Tier 1, Tier 2, & Tier 3 suppliers.”
- To see how repeatable product choices must be structured so many independent firms can participate without re-coordination each time, read the “Configurator File Type” project and the “Designing the Rule Layer” whitepaper.
- Jensen, P. (2014). Configuration of Platform Architectures in Construction (Doctoral thesis, Luleå University of Technology), p. 28. “A platform architecture defines a set of common components, interfaces, and rules that allow a variety of end products to be built, while enabling reuse and efficiency in both design and production.” ↩︎
- See Herbert A. Simon (Wikipedia) ↩︎
- Simon, 1962 “The Architecture of Complexity,” Proceedings of the American Philosophical Society. 1962. “In a nearly decomposable system, the short-run behavior of each of the component subsystems is approximately independent of the behavior of the other components, and the long-run behavior of any one component depends in only an aggregate way on the behavior of the others” ↩︎
- Simon, The Sciences of the Artificial, 1996. “Hierarchical systems are often nearly decomposable. In such systems, the interactions among the subsystems are weak, but not negligible, in the short run, and in the long run are important for the aggregate behavior of the system.” ↩︎
- Massimo Egidi, “Near-Decomposability, Organization, and Evolution: Some Notes on Herbert Simon’s Contribution” Models of a Man (pp.335-350), 2004. ↩︎
- For more, see Yochai Benkler, The Wealth of Networks: How Social Production Transforms Markets and Freedom, 2006 ↩︎
- See especially Melanie Mitchell, Complexity: A Guided Tour 2004 (page 102) “Systems that are composed of modules are often more robust to changes or failures in individual parts, because the effects of such changes are contained within modules. Modularity can also facilitate evolvability, since new modules can be added or old ones modified without disrupting the entire system.” ↩︎

