Latest / Scaling Up with Fexingo: How Small Businesses Become Mid-Market Companies / Why Mid-Market Firms Stumble On Their First Acquisition
Transcript
- Lucas: We talk a lot about organic growth in these episodes, but there is one moment where almost every mid-market leader gets tripped up: their first major acquisition. It usually happens around the five hundred million dollar revenue mark. The company has outgrown its internal processes, so buying a competitor or a complementary tech stack feels like the only way to scale fast enough. Luna: Right, and they buy for the strategy but inherit the people. That mismatch is where the value leaks away. Lucas: Exactly. You acquire a team of twenty smart operators who are used to doing things a certain way, and you bring in fifty employees from your home office who have their own entrenched habits. Within ninety days, if you haven't managed that handoff carefully, productivity doesn't just stall—it drops. We see this pattern repeat across industries, from manufacturing to software services. Luna: So the deal closes, everyone shakes hands, and then the real work of actually making them function as one entity begins. Lucas: Precisely. And here is the thing most consultants miss: the biggest risk isn't financial modeling or even customer churn. It is the silent collapse of trust between the acquired team and the acquirer. When you integrate two companies, you are essentially asking half your workforce to learn a new language overnight. Luna: That sounds exhausting. How do they keep customers from jumping ship during that chaos? Lucas: It starts with the simplest operational detail that drives the most anxiety: compensation. If you have two sales teams selling the same product, but one uses a tiered commission structure and the other uses a flat percentage, you create immediate resentment. Salespeople will leave before they even finish their first quarter under the new plan. Luna: Wait, they really leave over commission structures? That seems like a detail you should fix before the close. Lucas: You think you should, but in practice, leadership often delays it. They want to hit the ground running on revenue, not spend three months debating quota attainment rules. But by waiting, you signal to the acquired talent that their incentives don't matter. Once that signal goes out, top performers start updating their resumes immediately. Luna: Yeah, I can see that. If my bonus structure changes without me understanding why, I'm looking elsewhere too. Lucas: And it compounds. It's not just sales. It's engineering, it's support, it's finance. Every department has its own rhythm. If the acquiring company imposes its ERP system on day one without giving the acquired team time to adapt, you get data errors, missed invoices, and frustrated clients calling support for answers that aren't in the system yet. Luna: So the tech stack becomes a weapon instead of a tool during the integration phase. Lucas: Absolutely. We saw this with a regional logistics firm that bought a smaller competitor. They migrated the acquired team to the main company's cloud platform in a single weekend. By Monday, nobody could access their old client files. Deals stalled, drivers were confused, and the CEO had to spend the rest of the month apologizing to key accounts. Luna: That is a classic example of moving faster than your operational reality allows. Lucas: It is. And the irony is that the due diligence team probably checked the code and the contracts, but they didn't map out the daily workflows. They assumed technology would translate seamlessly. It rarely does. You have to build a bridge, not just pour concrete. Luna: So what does building that bridge actually look like in the first ninety days? Lucas: It looks like assigning integration leads from both sides. Not one person from headquarters telling the acquired team what to do, but paired leaders who jointly design the transition. They sit down and figure out which processes are sacred and which ones can be standardized. They agree on a timeline that respects the acquired team's capacity to learn. Luna: That requires a level of humility from the acquiring leadership that doesn't always come naturally when you're the dominant partner. Lucas: It definitely doesn't. Leadership wants control. But control without competence is dangerous. You need the acquired team's institutional knowledge to survive the transition. If you crush their autonomy too early, you lose the very expertise you bought the company for. Luna: It's like buying a library but burning the books because you wanted the building. Lucas: That is a perfect analogy. You are buying the brains, the relationships, and the proprietary methods. If you strip those away in the name of efficiency, you are left with an empty shell. The best integrations I have seen take a phased approach. They let the acquired unit operate independently for six to twelve months while slowly weaving in shared services. Luna: Does that slow down the synergy realization? Isn't that what shareholders are pushing for? Lucas: Shareholders push for speed, yes. But speed without stability creates debt. Technical debt, cultural debt, operational debt. Eventually, you have to pay it back with interest. A slower, more deliberate integration often yields higher long-term returns because the revenue stream remains stable while the backend catches up. Luna: So stability is the hidden metric for success here, not just the quick win. Lucas: Exactly. We see mid-market firms obsess over cost-cutting synergies—trimming headcount, consolidating offices. Those are easy wins. But revenue synergies, like cross-selling products or expanding into new territories, require a cohesive front. You cannot cross-sell if your teams are fighting over territory or if your systems don't talk to each other. Luna: It seems like the hard part is getting the middle managers on board. They are the ones feeling the squeeze from both sides. Lucas: Middle management is the shock absorber. If you skip them, the whole vehicle falls apart. You need to train them specifically on change management. They need to know how to communicate the vision to their direct reports without sounding like they are just repeating corporate mandates. They need tools, not just slogans. Luna: So communication becomes a structural component of the deal, not just a PR exercise. Lucas: Yes. And it has to be frequent, transparent, and honest. If there are layoffs coming, say so early. If roles are changing, explain why. Ambiguity breeds fear, and fear kills performance. We found that companies who held weekly town halls during the first quarter of integration saw significantly lower turnover rates than those who relied on email blasts. Luna: face to face interaction matters more than written policy during a crisis. Lucas: It absolutely does. People need to see that the leadership is present and engaged. It builds psychological safety. When employees feel safe, they ask questions. When they ask questions, problems get solved. When problems get solved, the integration moves forward smoothly. Luna: This feels like a lot of human capital management disguised as a finance problem. Lucas: That is the core insight. M&A is eighty percent people and twenty percent paperwork. If you focus only on the paperwork, you will likely fail at the people side. And since the people drive the revenue, you ultimately fail financially too. Luna: So the lesson is to invest heavily in the soft skills before you sign the check. Lucas: Or at least allocate budget for them during the integration phase. Most firms underfund the post-close period. They think the deal is done once the ink is dry. But the ink is the easy part. The living together is the hard part. Luna: I wonder if there is a simple test a leader can run before committing to a deal to see if they are ready for this level of complexity. Lucas: There is. Ask yourself if your current organization is actually stable. If you are struggling to manage your existing five hundred million dollars of revenue, adding another hundred million through acquisition is usually a disaster. You need a strong foundation before you add weight. Luna: Don't use a bandage on a broken leg. Fix the bone first. Lucas: Exactly. Build your own house properly before you try to annex the neighbor's. Because once you do, you are responsible for the whole neighborhood. Luna: That is a sobering thought for any CEO eyeing a competitor this quarter. Lucas: It is. Growth is attractive, but sustainable growth requires operational maturity. Without it, you are just delaying the inevitable reckoning. Luna: Do you think mid-market firms are getting better at this, or is it still a learning curve for most? Lucas: They are getting better, but the pace of consolidation is accelerating. So the window for error is shrinking. The ones who thrive will be the ones who treat integration as a core competency, not a one-off event. Luna: A core competency that takes years to build, but can be lost in weeks. Lucas: Yes. And that is why the quiet, unglamorous work of alignment is the most valuable work a leader can do after a deal closes. Luna: It reminds me that scale is less about size and more about cohesion. Lucas: Cohesion is everything. If you hold together, you grow. If you fracture, you shrink. The math doesn't lie. Luna: So the next time we hear about a big merger, maybe we should look at the integration plan, not just the price tag. Lucas: Definitely. The price tag tells you what they paid. The integration plan tells you if they kept it. Luna: And if they didn't have a plan, did they really have a deal, or just a gamble? Lucas: Usually a gamble. And in business, we prefer calculated bets over dice rolls. Luna: Calculated bets. That is the goal. Lucas: Always. Now, if these conversations have moved your work forward in some small way, we deliberately don't run ads on these. If you want to support that choice, the link is buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Thanks for keeping the show independent and focused on the details that actually matter. Lucas: Back to the topic, though. We mentioned compensation earlier, but what about the technical side? How do you merge two different software stacks without breaking the workflow? Luna: That is the operational nightmare. Do you rip and replace, or layer on top? Lucas: Rip and replace is risky but clean. Layering is messy but safer for continuity. It depends on the criticality of the system. Luna: So there is no one-size-fits-all answer. Just careful assessment of risk versus reward. Lucas: Exactly. And that assessment starts long before the deal closes. It starts in the mind of the leader. Luna: Thinking ahead, planning for the messy middle, and respecting the people who make it work. Lucas: Respecting the people is the foundation. Everything else rests on that. Luna: So, what is the one takeaway for a leader facing this right now? Lucas: Slow down the integration speed, but increase the communication frequency. Let the culture breathe while you build the structure. Luna: Breathe first, build second. I like that framework. Lucas: It works. And it saves you from the regret of losing your best people on day ninety. Luna: Regret is expensive. Prevention is cheaper. Lucas: In this business, prevention is usually the only profitable strategy. Luna: Let's hope more leaders listen to that advice before they sign the next big check. Lucas: If they do, the mid-market landscape will be much healthier for it. We will see.