You Can Buy the Company. You Still Have to Keep the People.

There is a reassuring moment in any acquisition when the lawyers finish, the numbers reconcile and someone produces a presentation explaining why the deal makes sense.

Unfortunately, the people who actually deliver the work were not necessarily consulted by the presentation.

My conversation with John Laughlin, owner, president and CEO of CTI, kept returning to that gap: the difference between buying a business and building an organisation that people want to remain part of.

John entered the audiovisual industry as an accountant. The job was supposed to be a stepping stone before he pursued a restaurant business. Instead, he became interested in the installations, the events, the technology and the customers. Accounting expanded into project work, sales and, eventually, ownership.

It is a useful reminder that careers are often explained backwards with considerably more certainty than they contained at the time.

The company behind the spreadsheet

John does not dismiss financial diligence. He can read the accounts. He understands why investors find the AV industry attractive.

But when he evaluates an acquisition, he wants to understand the organisation behind the revenue. Who works there? How do they work together? What makes them successful? Will they want to stay?

That last question is more commercially important than it can sound.

A customer may trust an engineer who understands the room, a project manager who solves problems or a salesperson who keeps promises. The company name helps, but it does not replace those relationships.

If the acquisition disrupts the team, the buyer may discover that the revenue was less securely attached to the corporate structure than the deal model implied.

John's test is strikingly human: when employees go home after the acquisition, do they think their working lives have improved?

That is not a substitute for due diligence. It is part of understanding what you bought.

Clear culture, flexible execution

CTI's approach to culture is explicit. John describes a document that explains how the company works, makes decisions and expects people to behave. He talks about teaching it directly to acquired teams.

There is nothing especially gentle about his language. He expects people to work hard, contribute and take care of customers. He also acknowledges that the environment will not suit everyone.

The interesting distinction is between clarity and rigidity.

John says an acquisition playbook needs flexibility because each acquisition is different. Treating every business identically can become its own mistake.

The principles need to be understood. The circumstances still need to be examined.

That matters because “culture” can become an excuse for avoiding both tasks. It can mean a vague collection of agreeable words, or it can mean that everyone must copy the founder's habits. Neither tells a project team what to do when the delivery is late and the customer is waiting.

The person may be in the wrong job

Another useful part of the conversation concerns performance.

John's starting point is effort, attitude and trust. If those are present but the person is struggling, he looks at leadership, training and the role itself.

That does not mean every employee can succeed at every task. It means failure in one role is not sufficient evidence of a complete absence of talent.

He describes moving people within CTI and finding that some became highly capable contributors in a different position.

We are strangely comfortable with the opposite process: take someone who is excellent at a particular job, promote them into an entirely different one, provide limited preparation, then act surprised when the result is disappointing.

The employee is described as having failed. The job design rarely receives the same level of scrutiny.

John's experience with acquisitions adds another caution. Some people who impressed him during interviews did not deliver as expected. Others he had underestimated became strong performers.

Being good at describing work and being good at doing it are related skills. They are not interchangeable.

A reliable product is the starting point

Manufacturers should pay attention to John's expectations of vendors.

A dependable product with a suitable warranty is necessary. It is not the entire partnership.

He wants manufacturers to help CTI educate its people, develop opportunities and execute work successfully. The relationship needs to make the integrator better at serving the customer.

That is an unusually useful definition of channel value. It shifts the conversation away from how much share of wallet a manufacturer would like to receive and towards what it contributes to earning that share.

For an integrator, training also has a practical limit. A team cannot maintain equal depth across an unlimited number of vendors. Knowing a smaller set of solutions thoroughly can be more valuable than having superficial familiarity with everything.

The system works. Does the experience?

The discussion of AV and IT convergence provides the broader context.

John expects straightforward deployments to remain accessible to IT organisations and other providers. More complicated environments need a different combination of skills.

A network test can show that devices communicate. It cannot, by itself, prove that a presenter can deliver an important meeting without distraction or that the room works as its users expect.

Technical reliability and human experience belong in the same conversation.

That helps explain why relationships matter so much. Customers depend on people who understand the intended result and can deliver it when the moment matters.

Keep learning. Keep changing the plan.

John is enthusiastic about continuing education, certifications, books and CTI's internal learning programme. His questions about university concern cost, time and purpose; they are not an argument against learning.

The same distinction runs through his view of leadership.

A strategy should respond to new information. A company's expectations around trust, effort and responsibility should be clear enough to guide people while that strategy changes.

It is a practical way to think about growth: build an organisation that learns without making everyone renegotiate the basic rules each morning.

You can buy the contracts, the equipment and the company name. Keeping the people who make them valuable remains a daily job.

Explore the conversation with John Laughlin at B4Obvious, and subscribe on YouTube for more decisions that only look obvious afterwards.