Purpose This article seeks to advance a novel service network perspective, based on the service‐dominant logic, designated as service‐dominant networks (SDN). Design/methodology/approach Service‐dominant logic components serve to build and describe SDN. Specifically, resources and actors are key components, combined with activities and the process by which they become resources. A case study details the features of SDNs. Findings Service‐dominant networks exhibit unique, previously unaddressed features. According to the service‐dominant logic, components only become resources when they are integrated; thus, they disappear as resources after their integration, which means SDNs are fugacious: they (be‐)come and go. In addition, SDNs comprise one or more main intended activities that explain their existence, though these intended activities do not necessarily initiate any particular SDN. Rather, other critical incidents can initiate SDNs. Research limitations/implications The features of SDNs proposed in this article have not been a focus of prior research. In particular, the dynamics and fugaciousness of SDNs are challenges for research and management. Originality/value This article offers the first proposal of a novel, service‐dominant network perspective. In a very general and abstract form, it identifies the features of SDNs.
Stored only when both papers are in the corpus — 62 citations exist upstream.