The first time you walk through a small professional services firm with an eye for the systems underneath, the dominant feeling is archaeology. Layer on layer of software accreted over decades. A practice management tool the partner picked when she went solo in 2009. A billing system the office manager added when the firm hit a million in revenue. A document repository that came in because a paralegal liked it. A bookkeeping platform an accountant recommended once. None of them are wrong, exactly. Each one solved a problem that was real at the moment it was installed. The problem is that no one ever zoomed out and asked whether the collection, taken as a whole, was a coherent operating system or a museum of past emergencies. Almost always, it is the museum.
Small professional services firms run on systems. The reason most of them do not run well is that the systems are accidental — assembled over fifteen years from whatever the partner happened to be using when she went solo, plus whatever the office manager added when something broke, plus whatever the IT person who came in once recommended before he disappeared. The firm runs on these systems the same way an old house runs on its plumbing: it works until it doesn’t, and when it stops working, nobody knows where the shutoff is.
When we acquire a firm, the systems audit is one of the first things we do. It is also one of the longest. The point is not to replace everything — replacing everything in a firm is how you destroy a firm. The point is to figure out what is actually load-bearing, what is decorative, and what is actively making things worse. The audit produces a map. The map is the foundation of every operational improvement that follows, because without the map, every improvement is a guess. Most firms operate without a map. We refuse to.
The 80/20 of Back-Office Infrastructure
There is a relatively short list of systems that every small professional services firm needs to run well. A practice management system that actually models the work. A document management system that the team trusts. A billing system that ties back to the work product. A client portal that clients will use. A financial system that produces real management reporting. A secure way to handle email, files, and credentials. And the integration layer that holds it all together.
Most small firms have rough versions of each of these. The problem is rarely that any one of them is missing. The problem is that they do not talk to each other. The billing system has one version of the client list. The practice management system has a different one. The email system has a third. The bookkeeping software has a fourth. Reconciling these takes hours every week and introduces errors that nobody catches until a client calls.
The deeper problem with un-integrated systems is not the time they consume. It is the cognitive tax they impose on the people doing the work. Every disconnection requires a human to hold two facts in her head and verify they match. Multiply that by twenty disconnections, across a team of fifteen people, across a workday — and a meaningful fraction of the firm’s collective brain is spent on reconciliation that adds no client value. The disconnections also create the silent failure mode that small firms are most vulnerable to: the small inconsistency that does not get noticed for six weeks and produces a bill that is wrong, a deadline that is missed, or a document that does not match the file. Integration is not a luxury. It is a precondition for the firm being able to think about anything else.
Integration Is the Product
What we actually deliver to the firms in our family is integration. We do not pick the fanciest practice management software and roll it out everywhere. We pick the system that fits the firm’s practice area and we make sure it is integrated with the rest of the stack so that data flows automatically, billing reconciles automatically, client communications log automatically, and the firm leader can see what is going on without asking three different people for three different reports.
The cost savings from this are real but they are not the point. The point is that integration removes the cognitive overhead of the firm. The firm leader stops thinking about which system has the truth. The intake coordinator stops re-typing the client’s information into four different places. The bookkeeper stops chasing down what happened to a payment because the system shows it. Every minute that the firm spends on this kind of internal reconciliation is a minute it is not spending on clients.
Integration also produces a second-order effect that most firms underestimate: it changes what kinds of questions the firm can ask itself. A firm with integrated systems can ask, “which practice area has the longest cycle time from intake to first deliverable?” and get an answer in five minutes. A firm with disconnected systems cannot ask the question at all, because answering it would require a paralegal to spend two days pulling data from four places, and nobody is going to spend two days answering a question that the firm has never asked before. The integrated firm gets to be curious about itself. The disconnected firm gets to be opinionated about itself. The first kind of firm improves over time. The second kind of firm just gets older.
What We Will Not Do
We will not build custom software when commercial software exists. We have watched too many firms get into the software-building business by accident and ruin themselves. The right answer is to pick the best commercial product, configure it carefully, and pay the subscription. The wrong answer is to hire developers and start writing code.
We also will not chase trends. The list of systems above is boring. It has been boring for fifteen years and it will be boring for the next fifteen. Boring systems that the team trusts beat exciting systems that the team has to learn every time. Stability has a value that does not show up in software demos.
The temptation to build custom software is one of the most reliable failure modes in professional services operations. It usually begins innocently. A senior partner identifies a workflow that no commercial tool quite handles. A developer in the firm’s family offers to build a quick solution. Six months later, the firm has a piece of software that mostly works, that depends on the developer to maintain, and that has become a load-bearing part of the firm’s daily operations. Twelve months later, the developer is busy with something else, the software has bugs nobody can fix, and the firm is back to manual workarounds — only now the manual workarounds are stacked on top of a custom system that nobody fully understands. The right discipline is to write the workflow down, look for the commercial tool that comes closest, accept the seventy or eighty percent fit, and configure around the gap. The seventy percent solution that is maintainable is dramatically better than the hundred percent solution that is fragile.
Where AI Fits
AI fits inside the existing systems, not on top of them. A bookkeeping system that has AI helping with categorization is more useful than a separate AI tool that you have to copy data into. A document management system that surfaces relevant prior work using embeddings is more useful than a chatbot that you have to prompt manually. The integrations that mattered five years ago still matter; AI just makes some of the steps inside those integrations faster and more accurate.
We are deploying AI inside the firms we own, but quietly. The firms do not advertise it to clients. The associates do not introduce it as “AI-powered.” It is just that the work happens faster, the responses come quicker, the documents have fewer mistakes, and the firm has more capacity. The technology recedes into the background of the work, which is where it belongs.
The reason we deploy AI quietly is not modesty. It is durability. Tools that announce themselves to clients become part of the firm’s brand promise, and brand promises tied to specific tools age badly. Five years from now, the specific AI tool that the firm advertised will be obsolete, replaced by something better, and the firm will either have to update its brand promise constantly or have to defend an obsolete tool against newer competitors. Tools that work silently behind the firm’s existing brand do not have this problem. The firm’s promise is to deliver quality work efficiently. The tool helps the firm keep that promise. If the tool changes, the promise does not. This is a small distinction with large consequences, and it is the one that separates firms that use AI well from firms that performatively use AI badly.
The Hidden Cost of Software Sprawl
One of the patterns we see in firm after firm is what we call software sprawl. A firm of twelve people will have forty-three software subscriptions, each one renewed automatically, each one used by one or two people, each one creating a small data island that has to be reconciled with everything else. The total annual spend is meaningful — often six figures — and the productivity drag is larger still. The sprawl happens because every individual subscription decision was rational at the time it was made. The aggregate is irrational, but no one is responsible for the aggregate.
The cure for software sprawl is the systems audit, repeated annually. Walk through every subscription. Ask who uses it. Ask what would happen if it disappeared. Most firms discover, on the first audit, that they can eliminate twenty to thirty percent of their subscriptions without losing any capability the firm actually relies on. The savings are real, and the simplification is even more valuable. A firm that runs on seven well-chosen systems is faster, clearer-thinking, and more resilient than a firm running on forty-three. The discipline of choosing what not to run is, paradoxically, what gives the firm its actual operating capacity. The maximalist firm thinks it has more capability because it has more tools. The minimalist firm thinks it has more capability because it has fewer distractions. The minimalist firm is correct.
Why This Matters
A small firm cannot afford the systems work we are describing here. The math does not work for a four-person practice. The math starts to work at a platform of firms, because the same controller, the same systems architect, the same integration work serves multiple firms at once. This is the whole rationale for the holding company structure. The systems are the asset. The firms are the customers. The clients are the beneficiaries.
This is also the part of the platform thesis that is genuinely defensible against larger competitors. Big firms have enormous systems teams but very little ability to deliver bespoke configurations to small practice areas. Small firms have intimate knowledge of their practice areas but no ability to invest in proper systems. A platform that combines the practice-area intimacy of the small firm with the systems-investment capacity of the larger one occupies a real and durable position in the market. The systems work, in other words, is not back-office plumbing. It is the strategic differentiator dressed up as plumbing — which is the most reliable way to build a durable advantage, because nobody copies the things that look boring.
What to Do Monday Morning
List every system the firm uses. Every one. Subscriptions, internal tools, spreadsheets that are load-bearing, the email aliases that route to the wrong place. Get them on one page. The act of listing them is, by itself, a small revelation, because no firm leader has ever counted before, and the count is always larger than expected.
Identify the disconnections. Where does the same client appear in two different systems with two different attributes? Where does a deadline get tracked in three places? Where does a payment have to be entered twice? The disconnections are the work. Closing them is what produces the integration that compounds.
And finally, do not buy anything new until you have eliminated something old. The discipline of one-in-one-out is what keeps software sprawl from accreting back. Every new tool has to displace an old one, or the firm has to make an affirmative decision to expand the surface area. Most of the time, the firm decides not to expand. That decision is the one that, year after year, keeps the operating system clean enough to actually be an operating system rather than an archaeology site.