I was working through the details of bringing a small team in-house. Purchase price, salaries, org chart, who reports to whom. Normal acquisition stuff. And I caught myself thinking about it like a hiring decision. How many people, at what cost, doing what work.
But we weren’t hiring. We were acquiring.
The distinction matters, and I think it matters more in the auction industry than most people realize.
When you hire someone, you’re renting their skills for as long as they stay. The moment they leave, whatever wasn’t documented or embedded in a system walks out with them. That’s not cynical, it’s structural. I wrote about this a few weeks ago in a different context: the relationships someone builds on your platform become yours, but the person is always rented. Everyone is.
An acquisition is different because you’re buying the system, not just the person who runs it. A client book built over fifteen years. An operational playbook that runs fifty auctions without anyone reinventing the process. A regional brand that banks and attorneys call first. A technology stack that compounds with every auction. These aren’t skills someone carries in their head. They’re institutional assets, and institutional assets survive the people who built them.
Most auction companies are small. One to five people, often a sole proprietor or a family operation. The top 20% doing 80% of the volume looks different, ranging from regional firms up to publicly traded companies with thousands of employees. But the single-point-of-failure problem runs through all of them, just at different scales. In a five-person shop, the owner IS the system. If they stop, everything stops. In a larger operation, maybe one person carries the key banking relationships, or one person understands the technology, or one person holds the operational playbook together. The industry doesn’t talk about this in polite company. If your key person leaves, do the relationships stay? Does the playbook survive? Do you own a platform or a login to someone else’s?
The companies pulling ahead right now aren’t doing it by adding people one at a time. They’re building systems that work whether or not any single person shows up on Monday. Proprietary bidder databases. Operational workflows that scale. Client relationships embedded in the company, not in one person’s phone. The fastest way to build a system like that is sometimes to buy one that already works.
That’s the real question when an acquisition lands on your desk. Are you buying a system that outlasts the people, or are you buying expensive employees with a term sheet instead of an offer letter? The answer changes everything about how you negotiate, how you integrate, and what you expect to still have in five years.
Here’s what I keep sitting with.
The person selling capability usually values it clearly. They know what they built and what it’s worth. The buyer often undervalues it because they’re thinking in headcount terms. Three people at X salary for Y years. That math misses the point. The salary is the cost. The system is the asset. And assets compound in ways that headcount never does.
But there’s a tension. The person who built the client book, who knows which attorney sends the best leads and which bank workout officer actually returns calls, that person is still rented. Always. The Rolodex stays when they leave. The judgment behind it doesn’t. Same with operations. The playbook stays. The instinct for when to deviate from the playbook doesn’t. Same with technology. The code stays. The reasoning behind the code doesn’t.
So when does the system become more valuable than the person who built it? That’s the test. If your key person left tomorrow and the system stayed, how much capability did you actually lose? If the answer is “most of it,” the acquisition bought headcount wrapped in an asset purchase. If the answer is “some, but we can keep building,” the acquisition bought real capability.
I think this is where the auction industry is headed. The companies that figure out whether they’re acquiring capability or hiring headcount will make better decisions about growth, about partnerships, about which relationships to cultivate and which systems to own. The ones that keep thinking in headcount terms will keep renting what they should be building.
The assets that compound in a business are the ones you own. That’s true for bidder databases. It’s true for brand. It’s true for client relationships. And it turns out it’s true for the team that builds everything else.