Latest / Scaling Up with Fexingo: How Small Businesses Become Mid-Market Companies / Why Mid-Market Firms Stagnate After Five Years
Transcript
- Lucas: The most dangerous moment for a mid-market company is right after it stops feeling like a startup and before it feels like a corporation. You are somewhere in between, which means you have lost the founder's intuition but haven't built the systems to replace it. Luna: It is that gap where everything relies on memory instead of process. If your key operator takes a sick day, does the whole supply chain freeze? Lucas: Exactly. And by September twenty fourth twenty twenty six, we are seeing this pattern repeat across logistics, specialty manufacturing, and even software services. The revenue grows, but the underlying operational rhythm fractures because nobody documented the playbook while they were busy closing deals. Luna: So the problem is not growth itself, but the lack of institutional memory during that rapid expansion phase. Lucas: Right. Let me share a quick update with you. If these conversations have moved your work forward in some small way, consider supporting us directly. Listener contributions keep this show ad-free and allow us to dig deeper into cases like this one. You can find us at buy me a coffee dot com slash fexingo. It really helps sustain the research behind these episodes. Luna: I appreciate that support. It allows us to continue exploring these nuanced business dynamics without commercial distractions. Lucas: Let's get back to the core issue. I was reviewing a case study from a regional freight broker last month. They crossed five hundred million dollars in annual revenue, yet their onboarding time for new dispatchers actually increased by forty percent year-over-year. Luna: That seems counterintuitive. Usually more resources mean faster training. What broke the process? Lucas: The founder had been training everyone personally for eight years. When he stepped back to focus on strategic partnerships, there was no written guide. New hires had to shadow three different veterans, each with conflicting methods. So efficiency dropped simply because the knowledge was tribal rather than systemic. Luna: Tribal knowledge is fragile. Once those veterans leave or retire, the entire operational model evaporates. Lucas: Precisely. And this happens most frequently around the two hundred employee mark. That is when informal communication channels become too noisy. You cannot just walk down the hall anymore. You need written protocols, but writing them requires time that leaders feel they do not have. Luna: They are always putting out fires. Who has the bandwidth to document what already works? Lucas: That is the paradox. They think documenting slows them down. But in reality, undocumented processes create constant rework. Every time someone asks a question that should be answered by a handbook, that is lost productivity. Over a year, those minutes add up to hundreds of thousands of dollars in wasted labor. Luna: So the cost of documentation is actually an investment in preventing future inefficiency. It pays for itself quickly. Lucas: Absolutely. Consider a mid-sized medical device manufacturer I consulted with recently. They implemented a simple rule: if a process happens more than twice a week, it gets documented. Within six months, their error rate in quality control dropped by fifteen percent. Luna: Fifteen percent is huge for quality control. Did they struggle to get staff to participate in writing these guides? Lucas: Initially, yes. Engineers hate writing. They see it as administrative bloat. But we shifted the approach. Instead of asking them to write manuals, we asked them to record short video walkthroughs of their specific tasks. Then junior staff could watch and pause whenever they needed clarification. Luna: Video feels less permanent and less intimidating than a formal policy document. It lowers the barrier to entry. Lucas: It does. And it captures nuance that text often misses. Tone, context, and troubleshooting steps come through naturally. The trick is keeping the library organized so people can actually find what they need. Otherwise, you just create a digital junk drawer. Luna: Organization is key. A messy wiki is worse than no wiki at all. How do they maintain relevance over time? Lucas: You assign ownership. Every piece of content needs a designated owner who reviews it quarterly. If the process changes, the owner updates it within forty-eight hours. If it stays static, it gets archived. This prevents the database from becoming outdated and unreliable. Luna: Accountability drives maintenance. Without an owner, documents rot silently until someone discovers they are obsolete. Lucas: Correct. And this brings us to another critical factor: leadership modeling. If the CEO refuses to use the system, nobody else will. Leaders must publicly reference the documentation during meetings. Saying 'let's check the standard protocol' reinforces its value far more than any memo ever could. Luna: Modeling behavior is powerful. It signals that the system is real, not just HR compliance theater. Lucas: Exactly. It shifts the culture from improvisation to execution. Now, let's talk about technology integration. Many mid-market firms try to solve this with expensive enterprise software suites. But often, simpler tools work better for teams under three hundred people. Luna: Why would simpler tools outperform complex enterprise solutions in this context? Lucas: Complexity kills adoption. If your team spends twenty minutes figuring out how to log a process change, they won't do it. Simple, intuitive platforms with search functionality encourage daily use. The goal is frictionless access to information. Luna: Frictionless access ensures usage. If it's easy, people will actually consult it when problems arise. Lucas: Yes. And this ties back to our earlier point about tribal knowledge. By making information accessible, you reduce dependency on specific individuals. This also improves retention, because employees feel empowered rather than dependent on mentors. Luna: Empowerment boosts morale. People want to solve problems independently, not wait for permission or guidance every step of the way. Lucas: Spot on. Another layer to consider is the feedback loop. Documentation should not be static. Teams should report bugs or outdated steps directly through the platform. This turns users into contributors, creating a living system that evolves with the business. Luna: A living system sounds much more sustainable than a static manual. It adapts as the company scales. Lucas: It does. And this adaptability becomes crucial when you face external shocks. During supply chain disruptions last year, companies with agile documentation recovered faster because they could rapidly update procedures without waiting for top-down directives. Luna: Resilience comes from decentralization. When front-line workers have the tools to adjust quickly, the organization responds nimbly. Lucas: Exactly. Decentralized decision-making speeds up response times. However, there is a risk. If everyone can change anything, chaos ensues. That is why governance matters. You need clear boundaries on what can be changed locally versus what requires executive approval. Luna: Boundaries prevent chaos. Clear rules on authority ensure stability while allowing flexibility. Lucas: Right. Think of it like traffic laws. You want drivers to make split-second decisions, but within a framework that keeps everyone safe. Too many red lights slow you down; too few cause accidents. Balance is everything. Luna: A great analogy. The balance between autonomy and control defines successful mid-market operations. Lucas: Indeed. One final consideration is metrics. How do you know if your documentation effort is working? Track onboarding time, error rates, and internal support ticket volume. If these numbers improve, you are building operational resilience. Luna: Measurable outcomes prove ROI. Leaders need data to justify continued investment in process improvement. Lucas: Data convinces skeptics. Once you show that documentation reduces costs and increases speed, resistance disappears. It becomes obvious that this is not bureaucracy, but infrastructure. Luna: Infrastructure supports growth. Without it, scaling feels like running on a treadmill—lots of effort, little progress. Lucas: That is the perfect image. Mid-market firms must stop viewing processes as constraints and start seeing them as enablers. The next time you feel overwhelmed by complexity, ask yourself what part of your operation lacks a clear playbook. Luna: Identifying the gaps is the first step toward fixing them. Which department is currently relying too heavily on memory? Lucas: Usually sales or customer success. Those are high-turnover areas where knowledge loss hurts most immediately. Start there. Document the win. Share it. Watch the efficiency spike. Luna: Starting with the highest impact area yields quick wins that build momentum for broader implementation. Lucas: Momentum is contagious. Once one team sees the benefit, others follow. It transforms the culture from reactive to proactive. Luna: Proactive cultures anticipate problems rather than reacting to them. That is the ultimate competitive advantage. Lucas: Agility beats size. Companies that master this balance will dominate their sectors for decades to come. Luna: Or stagnate if they ignore the structural demands of growth. Where do you see this trend heading next? Lucas: ai assisted documentation will likely become standard. Tools that auto-generate summaries from meeting notes or code commits could eliminate the manual burden entirely. Imagine if your team never had to write a single procedure again. Luna: That would shift the focus from creation to curation. Humans would verify accuracy rather than draft content. Lucas: Exactly. Verification becomes the new skill. Ensuring ai generated insights align with reality will be crucial. It changes the role of leadership from writer to editor. Luna: Editing requires judgment. That human element remains irreplaceable in guiding organizational direction. Lucas: True. Technology amplifies human intent. As long as leaders provide clear direction, these tools will accelerate growth rather than hinder it. Luna: Intentionality drives success. Whether manual or automated, the goal remains building a resilient, adaptable organization. Lucas: And that resilience is what separates survivors from leaders. The question is whether you will build that foundation today or regret it tomorrow.