Managing Multi-Brand Studio Operations for Permanent Equity

At Total Ventures, we do not build to flip. We are a permanent-equity company, which means every product we acquire or build stays in the portfolio indefinitely. This long-term horizon fundamentally changes how we approach multi-brand studio operations. When you own a single product, you can afford to be precious about its specific architecture. When you own five, ten, or twenty, your primary challenge is not just growth, but the cognitive load of maintenance.

Our model relies on a lean structure: one owner and an AI workforce. To make this sustainable, we have to be disciplined about our operational stack. We operate multiple brands from a unified foundation, making deliberate choices about where we share resources and where we allow for divergence.

The Philosophy of the Shared Stack

In traditional venture-backed startups, the goal is often to build a unique, defensible moat around a single product. In a permanent-equity portfolio, the moat is the efficiency of the operation itself. We view our portfolio as a fleet of ships. While each ship has a different destination and cargo, they should all use the same engine design, the same fuel, and the same navigation tools.

Effective multi-brand studio operations require a "default-to-shared" mentality. If we are shipping a new feature for one portfolio company, we first ask if that feature can be abstracted into our core library. This approach allows our AI workforce to maintain a high velocity. When an AI agent understands the underlying architecture of one product, it effectively understands them all. This reduces the time spent on context switching and minimizes the surface area for bugs.

When to Share: The Infrastructure Layer

We standardize everything that does not contribute directly to the brand’s unique value proposition. For most digital products, the "boring" parts are identical. There is no competitive advantage in having five different ways to handle user authentication or three different methods for processing payments.

Authentication and User Management

We use a single identity provider across the portfolio. This allows us to maintain a unified view of our users and simplifies the process of launching new products. If a user has an account with one of our properties, the friction to join another is significantly reduced. From an operational standpoint, it means we only have one set of security protocols to monitor and one set of API integrations to maintain.

Billing and Subscription Logic

All our products utilize a standardized billing wrapper. Whether a product is a monthly SaaS or a usage-based tool, the underlying logic for handling renewals, dunning, and tax compliance is the same. This uniformity is critical for our multi-brand studio operations because it allows us to generate portfolio-wide financial reports with minimal manual intervention. We can see the health of the entire company in a single dashboard because the data schema is consistent.

Data Storage and Logging

We utilize a managed data layer and a centralized logging service. By using a consistent relational database structure across products, we can reuse data migration scripts and backup routines. When we find a performance bottleneck in one product, the fix is usually applicable to the others. This is the essence of building in public: we share the lessons learned in one corner of the portfolio to strengthen the entire foundation.