Most studio models treat legal, recruiting, and design as free shared infrastructure, a pool of expertise every venture in the portfolio draws on without a line item attached to its use. The framing sounds efficient, and for the first two or three ventures it genuinely is. But infrastructure funded by nobody's specific budget is not free, it is subsidized, and every subsidy has a point where what it is subsidizing outgrows what it can cover. Nobody writes that point down, because writing it down would mean admitting the pool was never built to scale indefinitely in the first place.
The pool was sized for two ventures
A shared legal function built to handle contract review for one venture, then two, absorbs the marginal work of a second without anyone noticing the absorption happen. The lawyer's calendar has slack, the recruiter's pipeline has room, the designer's queue has gaps between projects, and that slack is the subsidy itself. Serving four ventures at the same quality as one was never a deliberate choice. It was a byproduct of the pool being underused early on, and underuse gets mistaken for permanent spare capacity.
The fourth venture is where the arithmetic actually breaks, because it is no longer drawing on slack, it is drawing on time that used to belong to venture one. Nobody reallocates that time on purpose. The legal function keeps answering every request in the order it arrives, the recruiter keeps sourcing for whichever role shouted loudest that week, and the queue lengthens for everyone by roughly the same small amount, which is exactly why nobody can point to a single cause when someone finally asks what changed.
Degradation shows up as delay, not denial
Nobody gets told the shared design function is now overcommitted. What happens instead is that the brand deck that used to come back in four days comes back in nine, and the ninth day gets attributed to that particular request being more complex, or the designer having a busy week, or the venture's own team not briefing clearly enough. Every individual delay has a plausible individual explanation attached to it. The pattern only becomes visible if someone lines up all four ventures' turnaround times side by side, and almost nobody ever does that.
The same thing happens to recruiting quality before it happens to recruiting speed. A pool serving one venture can afford three rounds of vetting on a candidate; a pool serving five ventures under the same headcount starts quietly cutting a round, not as policy but as the only way to clear the backlog. The hire who would have been screened out two ventures ago now gets through, and the venture that inherited that hire has no way of knowing the bar moved underneath it without anyone deciding to move it.
The subsidy does not disappear on a schedule. It thins out quietly until the ventures depending on it start absorbing costs nobody ever billed them for.
Nobody owns the decision to taper
The reason the subsidy never gets scheduled to end is that no single role is responsible for noticing it should. Studio leadership is watching venture performance, not shared-service load. Each venture's operator is watching their own turnaround times, not the four other ventures competing for the same recruiter's attention, and has no visibility into anyone else's queue either. And the shared function itself has every incentive to keep saying yes, because saying no to any one request looks like that function failing, rather than a structural signal that the pool has been oversubscribed for months.
This is a version of a pattern that shows up across venture-portfolio structures generally, where the venture portfolio gets managed as a set of individual bets without anyone tracking the shared substrate those bets are quietly standing on. Each bet gets reviewed on its own metrics, and the substrate gets reviewed never, because it does not show up on any single venture's dashboard, and nobody is specifically tasked with raising it either. It only shows up in aggregate, and aggregates are exactly what a portfolio built around individual accountability is structurally bad at producing.
The fix is a decision, not a top-up
The obvious response is to hire another lawyer, another recruiter, another designer, and treat the shortfall as a staffing problem. That fixes the queue for a while. It does not fix the underlying issue, which is that nobody ever decided what the shared pool was actually meant to cover, at what venture count, at what quality bar, and what happens past that count. Adding headcount without answering that question just resets the clock on the same undocumented subsidy, due to expire again the moment a sixth venture arrives.
The real failure here is not that shared services got overloaded, it is that they were never priced as a decision in the first place. Pooling legal, recruiting, and design across ventures is a legitimate structural choice, but only if someone names the capacity it was built for, the venture count it was sized against, and the point at which a venture graduates to dedicated resourcing of its own. Left undocumented, the pool behaves like a subsidy that quietly reallocates itself from the ventures that built it to whichever venture asked most recently, and calls the result efficiency.
