Navigating Mergers and Acquisitions in the Technology Industry — Open Source CXO Ep. 7 | Active Logic
In the second of two episodes with Ben Kittrell, CTO at Quext, the conversation dives into one of the most disruptive events a technology leader can face: a merger or acquisition. Ben speaks from direct experience — he was VP of Engineering at Homebase.ai when the company was acquired by Quext, and he navigated the transition from acquired company leadership to CTO of the combined organization. This isn’t theoretical M&A strategy; it’s a firsthand account of what happens when two technology organizations become one.
Mergers and acquisitions are common in the technology industry, but honest accounts of what they look like from the inside — especially from the technology leadership perspective — are rare. Ben provides that perspective with candor, covering the organizational, technical, and deeply human dimensions of the process.
The episode covers everything from the initial acquisition announcement through team integration, technology platform decisions, and the long-term work of building a unified engineering culture from two distinct organizations.
Key Insight: The Acquisition Experience From Inside the Acquired Company
Being acquired is a fundamentally different experience from acquiring. Ben describes what the Homebase.ai acquisition by Quext looked like from his team’s perspective, and the honesty is valuable for any technology leader who might find themselves in a similar position.
The initial announcement creates immediate uncertainty for every employee. Will my role still exist? Will the new company value the work we’ve built? Will the engineering culture change? These questions are not abstract concerns — they directly affect retention, productivity, and morale from the moment the acquisition is announced. Ben describes the emotional reality: even when the acquisition makes strategic sense and the terms are favorable, the loss of organizational identity is real. Engineers who built Homebase.ai’s technology were proud of what they created, and being absorbed into a larger entity threatened that identity.
Ben’s approach during this period was anchored in transparency and advocacy. He couldn’t promise specific outcomes because many decisions were above his authority. But he could share what he knew, acknowledge what he didn’t know, and actively advocate for his team’s interests in conversations with Quext leadership. The most important thing: being genuinely honest about uncertainty rather than offering false reassurance. Engineers are good at detecting when leadership is sugarcoating, and being caught in false optimism destroys trust faster than honest uncertainty.
For technology leaders building custom software products, the M&A landscape is a reality that should inform how you think about your career and your team. Understanding what acquisitions look like from the inside prepares you to lead through them effectively.
Key Insight: Technology Integration After an Acquisition
Two companies merging means two technology platforms, two architectures, two sets of tools, and two engineering cultures that must somehow become one. Ben describes this process in practical terms and doesn’t minimize the difficulty.
The first challenge is assessment: genuinely understanding what the other company built. Not just the high-level architecture diagrams, but the actual code quality, the technical debt, the undocumented tribal knowledge, and the real (not stated) system capabilities. Both organizations tend to overestimate the quality of their own systems and underestimate the quality of the other’s. Ben describes the process of conducting honest technical assessments that cut through organizational pride on both sides.
The platform consolidation decisions are among the most consequential and politically charged. Which company’s technology becomes the foundation? Which systems get deprecated? These aren’t purely technical decisions — they carry organizational identity, career implications, and emotional weight. An engineer whose system gets deprecated feels like their work is being rejected, regardless of the technical rationale.
Ben’s approach: making platform decisions based on transparent technical criteria while being deliberately empathetic about the human impact. He invested time in explaining the rationale for decisions, ensuring engineers from both organizations understood why specific platforms were chosen, and creating roles for engineers whose original systems were being deprecated. For organizations that rely on cloud infrastructure and complex web applications, the integration challenges multiply with system complexity.
Key Insight: Team Integration and Organizational Change Management
Merging two engineering teams is fundamentally a human problem, not a technical one. Ben describes the interpersonal dynamics that emerge when two groups of engineers are told they’re now one team — and why ignoring these dynamics guarantees failure.
The “us vs. them” dynamic is natural and persistent. Engineers from the acquiring company feel ownership and authority. Engineers from the acquired company feel like guests in someone else’s house. These feelings exist regardless of what leadership says about “equal partnership” or “best of both worlds” — the power dynamic is real, and pretending otherwise insults everyone’s intelligence.
Ben’s strategy addressed this directly. Rather than pretending the power dynamic didn’t exist, he acknowledged it and took concrete steps to distribute authority and decision-making across both legacy organizations. Engineers from Homebase.ai were given leadership roles in the combined organization based on expertise, not legacy affiliation. Technical decisions were made by the people closest to the problem, regardless of which company they originally came from. And he was deliberate about creating shared experiences — projects that required genuine collaboration between people from both organizations — to build the relationships that eventually replace organizational loyalty with team loyalty.
The timeline for genuine integration is longer than most organizations expect. Ben estimates that it took roughly a year before the “Homebase.ai people” and the “Quext people” labels faded and the team functioned as a genuinely unified organization. Leaders who expect integration in a quarter are setting themselves up for disappointment and making decisions that prioritize speed over durability.
Key Insight: Communication and Emotional Intelligence in Transitions
The hardest part of leading through an acquisition isn’t making technical decisions or reorganizing teams. It’s managing the emotional reality of organizational change for dozens or hundreds of people whose professional lives have been disrupted by a decision they had no role in making.
Ben describes the communication cadence he established during and after the acquisition. Regular updates — even when the update was “we don’t have new information yet” — were essential for maintaining trust. Silence during uncertainty is interpreted as either incompetence or deception, neither of which supports a productive transition. He held frequent team meetings, maintained open one-on-one schedules, and created explicit channels for questions and concerns.
Emotional intelligence in this context means recognizing that different people process organizational change differently. Some engineers are energized by the new opportunity and frustrated by what they see as others’ resistance to change. Others are grieving the loss of the organization they helped build and need time to process before they can engage productively with the new reality. Both responses are legitimate, and leaders who only validate one — typically the “let’s move forward” perspective — alienate the people whose institutional knowledge and deep system understanding are most critical for successful integration.
Ben’s advice for technology leaders: develop your emotional intelligence before you need it. The middle of an acquisition is not the time to learn how to have difficult conversations, read emotional dynamics in a room, or sit with someone else’s distress without trying to fix it. These are skills that require practice, and the leaders who navigate acquisitions most effectively are the ones who invested in developing them long before the deal was announced. For anyone leading software development teams, emotional intelligence is a core competency, not a nice-to-have.
Key Insight: Career Navigation Through Organizational Disruption
Ben’s personal trajectory — from VP of Engineering at an acquired company to CTO of the combined organization — is instructive for technology leaders thinking about their own careers in an industry where M&A is a constant.
His advice is practical: don’t treat an acquisition as something that happens to you. Treat it as a strategic situation that requires active navigation. This means understanding the acquiring company’s goals, identifying where your skills and knowledge are most valuable in the new organization, building relationships with the acquiring company’s leadership, and positioning yourself as part of the solution rather than a remnant of the old organization.
But Ben is also honest about the limits of this advice. Sometimes the acquisition creates a role that’s a genuine fit and sometimes it doesn’t. Sometimes the cultural integration works and sometimes it doesn’t. The strategic navigation matters, but so does the honest assessment of whether the new organization is a place where you want to build your career. Staying out of obligation or inertia when the fit is wrong serves neither you nor the organization.
Takeaways
- Transparency beats false reassurance during acquisitions. Engineers detect sugarcoating instantly, and being caught in it destroys trust.
- Technology integration decisions carry emotional weight. Deprecating a platform feels like rejecting the people who built it — address that directly.
- Genuine team integration takes roughly a year. Expecting it in a quarter creates pressure that damages the outcome.
- Silence during uncertainty is interpreted as incompetence or deception. Regular communication — even without new information — maintains trust.
- Develop emotional intelligence before you need it. The middle of an organizational transition is not the time to learn these skills.
- Navigate acquisitions actively, not passively. Understand the new organization’s goals and position yourself as part of the solution.
