Business Model Design

Why this node matters

Business model design is the node where the firm's architecture of value creation, delivery, and capture is set as a system of interacting choices. The design determines what revenue is structurally available to capture, what cost dynamics operations inherit, what unit economics the EBITDA bridge can compound, and what valuation multiple the exit can command for identical operational performance. ICP and Segment Selection, Offer Creation, Price Architecture, Channel Design, and Customer Success all inherit their commercial logic from this layer. The Business Model Assessment node separately diagnoses whether the existing architecture warrants redesign. This node addresses the prescriptive question of how the design choices themselves are made.

Most Mittelstand portcos do not actively design their business model. The architecture is inherited from founding decisions made decades ago, modified incrementally as customers asked or markets changed, and revisited only when operational pain becomes structural. The visible inputs are the existing product catalogue, the established customer base, and the historical revenue mix. These variables describe the inherited model without naming the design choices that produced it, and so predict future commercial impact weakly. The economically meaningful design criteria are which segments the model serves with measurable distinctness, which design theme the architecture commits to, which revenue model captures the value created, and whether the choices reinforce each other into a coherent system.

The unexamined assumption underneath in PE operating practice is that business model design is a strategy-team concern, decided at founding, modified rarely, and not amenable to operational redesign within a hold window. Business model design is a system of present-tense choices the operating partner can actively reshape, with measurable performance effects within a single hold.

The empirical literature is unambiguous. Teece (2010), in Long Range Planning, drew the foundational distinction most practitioners blur: strategy is the plan for competitive positioning; business model is the architecture by which the firm creates, delivers, and captures value. A firm can have a strong strategy and a weak business model. The reverse is rarer. Sohl, Vroom, and Fitza (2020), analysing 917 European retailers over twelve years, confirmed empirically that business model explains 5.1 percent of variance in ROA and 7.9 percent of variance in market share, at a magnitude comparable to industry effects. Design choices are causally consequential, and the consequence is measurable.

The node operates across four design layers. Each carries a different decision weight.

Value creation architecture carries foundational decision weight. Which customer segments the model serves, what value-in-use the offer produces, and which resources and capabilities the firm must own, develop, or partner to deliver. Osterwalder and Pigneur (2010), in Business Model Generation, established the canonical nine-block framework that names these design choices explicitly. Zott and Amit (2010), in their Long Range Planning activity system perspective, demonstrated that the design themes a firm commits to (novelty, lock-in, complementarities, efficiency) systematically predict which capabilities it builds. The mechanism: value creation architecture determines what the firm is structurally capable of producing. Misaligned value-creation choices, such as a novelty-promised value proposition paired with an efficiency-centred capability portfolio, produce systematic execution friction that no operational discipline removes.

Value delivery architecture carries predictive weight. Activity system design, channel architecture, partner ecosystem, and the asset-light versus asset-heavy decision. Zott and Amit (2007), in their Organization Science study of 190 publicly listed entrepreneurial firms, demonstrated that novelty-centred design themes predict firm performance independent of strategy or industry, but that pursuing novelty and efficiency simultaneously produces diseconomies in the data. The mechanism: delivery architecture determines cost structure, operating leverage, and scalability. Asset-light models produce higher gross margins (70 to 80 percent in SaaS contexts) but lower switching costs. Asset-heavy models produce the inverse. The trade-off is structural, not operational.

Value capture architecture carries operational weight. Revenue model (transactional, recurring, usage-based, outcome-based, subscription, hybrid), cost structure, pricing logic available, and retention economics enabled. Aventis Advisors (2025), analysing 1,325 software transactions, found recurring-revenue models command 2 to 5x the EBITDA multiples of transactional models for otherwise identical financial performance. McKinsey (2025), studying 98 B2B SaaS companies, found NRR above 120 percent correlated with median EV/Revenue multiples of 21x against 9x for those below 120 percent. The mechanism: revenue model choice determines what revenue is structurally available to capture, what marginal cost dynamics the firm inherits, and what valuation effect the architecture produces at exit.

Architectural coherence carries executability weight. Internal consistency of design choices, choices-and-consequences alignment, capability fit, and strategic fit with product market. Casadesus-Masanell and Ricart (2010), in Long Range Planning, framed business model design as a set of policy, asset, and governance choices that produce either reinforcing or eroding consequences. Sohl and Vroom (2014), in Strategic Management Journal, found business model coherence, the internal consistency of design choices, predicts long-run margin more strongly than any single design element. The mechanism: incoherent business models produce structural friction at the interfaces between layers. Asset-heavy delivery paired with subscription revenue, or novelty-centred value creation paired with efficiency-centred operations, are the canonical failure modes. Coherent designs produce positive feedback loops; incoherent designs produce structural drag that operational excellence cannot overcome.

The output of the node is a primary business model architecture in which all four layers cohere: value creation served by capable resources, value delivery aligned with the chosen design theme, value capture monetising the created value through a structurally appropriate revenue model, and architectural coherence reinforcing rather than fragmenting the system. A redesign candidate list contains design choices that satisfy two or three layers but produce friction at the interfaces, requiring targeted intervention rather than wholesale redesign. A discontinuation list contains design choices that produce structural incoherence, such as mixed efficiency-and-novelty themes, transactional revenue paired with high asset intensity, or single-segment design forcing multi-segment compromises. These should be redesigned before EBITDA improvement is attempted. The selection is a precondition for every downstream node in the methodology library.

The thesis: a business model that cannot align value creation with capability, monetise through a structurally appropriate revenue architecture, and reinforce coherence across the system is not a business model. It is an accumulation of historical design decisions.