Latest / Scaling Up with Fexingo: How Small Businesses Become Mid-Market Companies / Why Mid-Market Firms Lose Control of Their Tech Stack
Transcript
- Lucas: If you walk into the headquarters of a company that just crossed fifty million in revenue, you’ll notice something strange. The sales team is firing on all cylinders, the product roadmap is clear, but the people who actually run the day-to-day operations look exhausted. It’s not because they’re working harder. It’s because their technology stack has become a labyrinth. Luna: Right. And usually, that labyrinth was built intentionally, one good reason at a time. Nobody wakes up wanting chaos. Lucas: Exactly. We call it the best of breed trap. When a company is small, you use whatever tool works today. Maybe that’s a spreadsheet for inventory, a generic CRM for leads, and a separate project management app for engineering. Each tool is great in isolation. But by year three, those tools stop talking to each other. The data lives in four different places, and no one person owns the single version of the truth. Luna: So the founder ends up spending three hours a day manually reconciling numbers instead of making strategic decisions. Lucas: That’s the baseline cost. But the real damage is deeper. Let’s look at a specific case from last quarter involving a mid-sized industrial manufacturer. They had adopted twelve different SaaS applications across finance, logistics, and HR. On paper, each department was happy. In reality, they were spending two hundred thousand dollars a year just on API connectors and manual data entry fixes. That’s money burned before it even hits the P&L as labor. Luna: Two hundred thousand dollars just to keep the lights on digitally? That sounds like a massive opportunity cost. Lucas: It is. And here is the kicker: the CEO didn’t know about it until an external consultant audited their IT spend. The expense wasn’t hidden in one line item. It was spread across subscription fees, part-time contractor hours, and delayed shipments caused by inventory discrepancies. When you have too many point solutions, your operational rhythm fractures. You lose the ability to see the whole board. Luna: So how do you fix it without disrupting the teams that rely on those specific tools? Lucas: You start by admitting that integration is not a feature. It’s a core competency. Most mid-market firms treat software procurement like shopping. They go to conferences, talk to peers, and pick the shiny new thing. But at the mid-market stage, you need an architecture mindset. You need to ask: does this tool solve a unique competitive advantage, or is it just table stakes? If it’s table stakes, you buy the platform that integrates with everything else, even if it’s slightly less specialized. Luna: That’s counterintuitive. Everyone wants the best tool for their specific job, not the most connected one. Lucas: I get that instinct. But let me give you a concrete rule we use when advising clients. If the software doesn’t help you differentiate your customer experience or protect your margin, it’s infrastructure. And infrastructure should be boring. It should be standardized. You want your ERP, your CRM, and your payroll system to talk to each other seamlessly. Everything else can be modular, but the backbone must be unified. Luna: So the move is from specialization to cohesion. Is that hard to sell to department heads who love their niche apps? Lucas: It is. That’s where leadership gets tested. You have to show them that their favorite app is creating more work for them than it’s saving. I had a client, a digital marketing agency, who refused to switch from five different scheduling tools to one integrated suite. They thought it would limit their flexibility. Six months later, they realized they were wasting forty hours a week switching contexts and exporting reports. The friction wasn’t in the tool; it was in the handoffs. Luna: And those handoffs are where errors happen. A missed email, a double-booked meeting, a mispriced invoice. Lucas: Precisely. Those micro-errors compound. They erode trust internally and externally. So, here is the framework for the listener who is sitting in that chair right now. Step one: map every active subscription against its user base. Identify the duplicates. Step two: calculate the total cost of ownership, including the hidden labor of maintenance. Step three: prioritize consolidation around one core operating system. Luna: What if you can’t afford to rip and replace everything at once? Cash flow constraints are real at this stage. Lucas: Then you phase it. You don’t boil the ocean. Pick the pain point that is costing you the most money or causing the most customer complaints. Fix that integration first. Prove the ROI. Then move to the next layer. But you must have a roadmap. Otherwise, you’re just adding another brick to the maze. Luna: That makes sense. Treat it like a renovation, not a demolition. Lucas: A renovation. Yes. And while we are talking about renovations, I want to pause for a moment to talk about how we keep this conversation going. If these conversations have moved your work forward in some small way, consider supporting the show directly. It helps us continue producing ad-free episodes that focus on the nuts and bolts of business growth. You can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Just a quick note of support from listeners who value deep, practical analysis. Luna: We really appreciate it. It keeps the research rigorous and the editing tight. Lucas: Back to the stack. There is one more layer to this that people often miss. Culture. When you consolidate your tech stack, you are forcing collaboration. You are saying that the data belongs to the company, not to the department. That can feel threatening to middle managers who derive power from hoarding information. Luna: Oh, absolutely. If my only value is that I’m the only one who knows how to update the legacy spreadsheet, consolidating the system threatens my job security. Lucas: Spot on. So the technical fix requires a cultural narrative. You have to frame consolidation as empowerment, not surveillance. You tell your team: we are removing the busywork so you can do the high-value work. We are giving you better data faster. If you position it as giving them superpowers instead of taking away their toys, adoption skyrockets. Luna: That’s a powerful reframe. It shifts the dynamic from control to enablement. Lucas: It does. And let’s look at the metrics. How do you know if you’ve succeeded? It’s not just about lower subscription costs. It’s about speed. Time to insight. When a leader asks, what did our net retention look like last month, how long does it take to answer? In a fragmented stack, it takes days. In a consolidated one, it takes seconds. That speed changes the quality of decisions. Luna: Decisions made in seconds are better than decisions made in days, especially in a volatile market. Lucas: Agreed. Now, let’s address the build versus buy question again, because it ties into this. Some founders say, well, off-the-shelf software doesn’t fit our unique process. So they build custom dashboards. Here is the hard truth: unless your proprietary algorithm is your main source of revenue, do not build custom software for internal operations. Maintainability is a nightmare. When your developer leaves, your dashboard dies. Luna: Or worse, it becomes a black box that no one understands except the person who left six months ago. Lucas: Exactly. You inherit technical debt that grows interest every single day. Stick to the proven platforms. They update themselves. They have security compliance built-in. They have support tickets you can open. Custom builds are for your product, not your plumbing. Luna: Plumbing that needs to flow smoothly, otherwise the whole house floods. Lucas: Perfect analogy. So, if you are listening to this and you suspect your tech stack is the bottleneck, start with the audit. Map the flows. Find the friction. And remember, simplicity scales. Complexity collapses. As you grow past that fifty million mark, your systems need to handle volume, not variety. Variety is for startups. Volume is for enterprises. Know which game you are playing. Luna: It’s a reminder that what got you here won’t get you there, especially when the tools are involved. Lucas: Right. The tools that helped you survive may be the ones that kill your growth if you don’t evolve them. It’s about intentionality. Every dollar spent on software should have a clear line of sight to operational efficiency or customer delight. If it doesn’t, cut it. Luna: Clean cuts are better than slow bleeds. Lucas: They are. And as we wrap up, I want to leave you with a question to ponder over the weekend. Look at your own calendar. How many times did you have to switch tabs, copy-paste data, or chase down a colleague for a missing file today? Count it. That number is your tax on inefficiency. Can you reduce it by ten percent next month? Luna: That’s a practical metric. Not just revenue, but time reclaimed. Lucas: Time is the only resource you can’t buy back. So reclaim it. Clean up the stack. Simplify the workflow. And watch how much lighter the operation feels. Luna: Here’s to simpler systems and clearer decisions. Lucas: To that. We will see you in the next one.