Blog

Every multi-entity structure eventually faces the same question, and the answer determines whether the structure becomes an asset or a liability. The question is where authority lives. Not where it lives on the org chart, which is the easy question, but where it lives in practice — in the small decisions that get made every day without anyone noticing, in the gravitational pull that builds up when a function gets centralized, in the slow rewriting of who decides what that happens whenever a holding company gets bigger than the firms underneath it. The hardest decision in designing the TX-LW structure was where to draw the line between the holding company and the operating firms. Draw the line in the wrong place and you get the worst of both worlds: a holding company too thin to actually help, and operating firms too constrained to actually operate. Draw the line in the right place and you get the thing that makes the platform work: real autonomy at the firm level, real leverage at the platform level, and no confusion about who decides what.

This essay is about how we drew that line, why we drew it where we did, and what we have learned about defending it. It is also about the broader principle behind the decision, which is that organizational architecture is a form of pre-commitment. You are not just designing reporting relationships. You are designing a set of constraints that will outlive the founders, that will be tested by every new hire, every new initiative, every new firm acquired into the platform. The architecture is a promise to the future about what kind of company this is. Get the promise wrong and the company drifts into something nobody chose to build.

The Drift Problem

There are a thousand wrong ways to draw the line. The most common wrong way is to let the line drift. The holding company starts with a narrow role, then a new initiative requires platform-level coordination, then a particular firm has a problem the platform decides to solve for it, then a standardization push sneaks in because it would be easier for the controller. Five years in, the holding company has accumulated authority it never explicitly took, and the firms have lost authority they never explicitly gave up. Nobody can tell you when the shift happened, but the firms can tell you it happened.

Drift is not a failure of intention. It is a failure of architecture. Every individual decision that contributes to drift is defensible on its own terms. Of course the marketing team should run the campaign centrally — it is more efficient. Of course the controller should set the chart of accounts — it is cleaner. Of course the platform should approve the new hire above a certain level — it is prudent. Each step is small. Each step is justified. The cumulative effect of the small justified steps is a company nobody chose to build, run by a holding company that has quietly become the headquarters of an operating company while still calling itself a platform.

The cure for drift is not vigilance. Vigilance fails because the people doing the drifting are not adversaries — they are colleagues solving real problems in good faith. The cure for drift is a written line, defended publicly, with a default that favors the firm whenever the line is ambiguous. The architecture has to do the work, because the people are too busy and too well-intentioned to do it for you.

What the Holding Company Does

A short list. The holding company sets the capital allocation policy — how much each firm can spend on what kinds of investment. The holding company underwrites the shared infrastructure — the technology platform, the controllership function, the marketing function, the operations leadership. The holding company is the eventual employer of the firm leadership, which means it can hire, develop, and replace firm leaders. The holding company runs acquisitions, including the diligence and the integration. The holding company owns the brand at the platform level — the TX-LW name, the shared standards, the institutional voice.

That is the list. The holding company does not own client relationships. The holding company does not own matter-level decisions. The holding company does not own staffing decisions inside a firm. The holding company does not own practice-area strategy. The holding company does not own pricing. Each of those is the firm’s.

The list is short on purpose. A long list is a confession that you have not yet figured out what the holding company is for. The holding company is for the things that scale, that benefit from centralization, that one good decision-maker can do better than ten — and nothing else. Everything else is noise that belongs at the firm level, where the people who actually know the work can make the call. If you find yourself adding a tenth or eleventh item to the holding company’s responsibilities, the right move is not to add it. The right move is to ask why it is being added, what problem it is solving, and whether the firm could solve that problem itself if it had to. Most of the time, the firm could.

What the Operating Firm Does

Everything that the holding company does not do. Practice-area strategy. Client relationships. Matter-level decisions. Staffing decisions. Pricing. Local marketing — supported by the holding company’s marketing function but driven by the firm. Vendor decisions inside the firm. Day-to-day operating choices. Compensation inside the band the holding company sets for the role. The choice of what work to take and what to decline.

The firm is a real business. It has its own P&L, its own staff, its own leadership, its own brand. It is not a profit center inside a larger company. It is not a subsidiary in the conventional sense. It is a separately operated business under common ownership. The distinction matters because it changes everyone’s incentives. A profit center inside a larger company manages to the larger company’s numbers. A real business under common ownership manages to its own numbers, with the larger company as a capital provider and infrastructure partner, not as a parent dictating quarterly targets.

This distinction is not a semantic flourish. It changes who the firm leader gets up in the morning thinking about. If the firm is a profit center, the firm leader thinks about pleasing the platform. If the firm is a real business, the firm leader thinks about serving the client. The first orientation produces firms that drift toward whatever the platform measures. The second orientation produces firms that are durably good at the actual work, because the actual work is what the firm leader is being held accountable for.

Shared Infrastructure, Separate Identities

The phrase we use most often inside the company is shared infrastructure, separate identities. The shared infrastructure is technology, controllership, marketing operations, administrative leadership, and the institutional knowledge of how to run a small professional services firm. Every firm benefits from these. The separate identities are everything that touches the client — brand, voice, work product, relationship, location, history. Every firm preserves these.

In practice this means a probate client who goes to Kreig LLC does not see TX-LW anywhere. The lawyer she meets with works for Kreig LLC. The engagement letter says Kreig LLC. The bills come from Kreig LLC. The portal is branded Kreig LLC. The client knows she is working with a small Texas probate firm. She is right. She is also benefiting from a controllership function, a technology platform, and an operations discipline that a standalone firm of that size could never afford. The shared infrastructure is invisible to her, which is exactly the point. Infrastructure that announces itself is no longer infrastructure. It is a brand collision.

The separation of identities is not a marketing posture. It is an operational commitment. The firm has its own engagement letters because the firm is the legal counterparty. The firm has its own bills because the firm is the economic counterparty. The firm has its own portal because the firm is the relationship counterparty. The holding company is not the counterparty to anything client-facing. The holding company is the counterparty to the firm.

Why the Architecture Looks This Way

The architecture is shaped by what scales and what does not. Technology scales. Centralized controllership scales. Marketing operations scale. Real estate, vendor management, insurance, banking — all of these scale. The shared infrastructure is the things that scale.

Client relationships do not scale. Practice expertise does not scale across practice areas. Trust does not scale. Reputation does not scale. The identity of being a small Texas firm that knows its clients and serves its community does not scale. These are the things we keep at the firm level, because the moment we try to scale them, they break.

The deeper logic is that there are two fundamentally different kinds of value creation happening inside any professional services platform, and they obey different laws. Infrastructure value compounds with scale — every additional firm makes the controller more leveraged, the technology platform cheaper per seat, the operations playbook more refined. Relationship value compounds with depth — every additional year of working with a client makes the lawyer more useful, every additional case in a practice area makes the firm more expert, every additional referral in a community makes the firm more durable. The first kind of value rewards centralization. The second kind of value punishes it. A well-designed platform separates the two and lets each compound in its own way. A poorly designed platform tries to centralize both and ends up with infrastructure that scales beautifully and relationships that quietly atrophy.

This is the architectural insight that drove every other decision. If you accept that infrastructure and relationships obey different laws, then the holding company has to be designed to handle one kind of value and the operating firms have to be designed to handle the other. They cannot be the same organization with different labels. They have to be different organizations with different cultures, different incentives, and different ways of measuring success. The line between them is not a convenience. It is a recognition of two different physics.

What Happens When the Line Is Tested

Every quarter, something happens that tests the line. A platform-level initiative would be easier if the firms standardized. A firm-level decision would be easier with platform-level approval. We default to the line as written. The platform does not standardize firms; the platform supports firms in being themselves. The firm does not seek platform approval; the firm decides and the platform reads the report.

The tests rarely look like power grabs. They look like efficiency arguments. Wouldn’t it be easier if all the firms used the same intake form? Wouldn’t it be cleaner if all the firms followed the same engagement letter template? Wouldn’t it be smarter if the platform reviewed pricing above a certain threshold? Each of these questions is reasonable in isolation. Each of these questions, answered yes, moves the line. Five years of reasonable yeses produce an unreasonable structure. The answer to almost all of these questions is no, and the reason is not that the question is bad. The reason is that the architecture is more valuable than the local efficiency the question is asking us to capture.

Holding the line costs us speed sometimes. We are willing to pay that cost because the alternative is the slow drift toward the kind of consolidated platform we explicitly chose not to be. The architecture is the discipline. The discipline is what makes the firms durable.

The Counter-Argument, Honestly Stated

The honest counter-argument to this architecture is that it leaves money on the table. A more consolidated platform would capture more of the operating leverage. A more standardized firm network would be easier to sell, easier to scale, easier to manage. The conventional roll-up playbook produces bigger numbers faster, at least on paper, and the people who run those platforms are not stupid. They have read the same books we have.

We have decided that the money left on the table is the price of admission to a different game. The consolidated platform optimizes for short-term operating leverage and long-term fragility. The relationships get thinner, the firm-level expertise gets diluted, the people who actually know how to do the work leave because they no longer recognize the firm. The platform looks great in a deck and feels hollow on the inside. We are not building for the deck. We are building for the client who will be a client in ten years, and that client wants a firm that still feels like a firm, not a branch office of a consolidated operator.

There is also a humility argument. We do not actually know what the optimal level of consolidation is. Nobody does. What we know is that consolidation is easy to do and hard to undo, and that a structure with strong firm-level autonomy preserves the ability to consolidate later if we decide we want to. The reverse is not true. A consolidated platform cannot retroactively manufacture firm-level identity and relationship depth. The architecture we have chosen is the more reversible one. In a world where we cannot be certain we are right, the more reversible architecture is the wiser bet.

What to Do Monday Morning

If you are designing a multi-entity structure, write the line down. Not in a slide. In a document that you would be comfortable showing every firm leader and every platform employee, that says here is what the holding company decides and here is what the firm decides and here is what we do when the two disagree. The act of writing it down forces a precision that the slide does not. The act of publishing it commits you to defending it.

Keep the holding company’s list short. If it is more than five or six things, you are probably building a consolidated operator and calling it a platform. Be honest about which one you are building, because the two require different leadership, different incentives, and different stories told to the people you are trying to hire.

Default to the firm when the line is ambiguous. Centralization is a one-way ratchet. Decentralization is a posture you have to maintain on purpose, every quarter, against the constant pressure of small efficiency arguments. The default has to lean in the harder direction, because the easier direction will win the rest of the time on its own merits.

And finally, audit the line annually. Not the org chart. The actual line. Where did decisions get made this year that the architecture says should have been made somewhere else? Where did the platform reach into a firm? Where did a firm punt to the platform something that was its own to decide? The audit is not a punishment exercise. It is a recalibration. The drift is constant. The discipline is the answer.