Latest / Scaling Up with Fexingo: How Small Businesses Become Mid-Market Companies / How Mid-Market Firms Fix Their Operating Rhythm
Transcript
- Lucas: There is a very specific type of exhaustion that sets in when a company crosses the fifty million dollar threshold. You stop being able to hear every conversation in the building, but you still have too many people asking you for decisions. The founder used to know what was happening because they were in the weeds. Now, they are sitting in a boardroom looking at dashboards that feel three weeks old. Luna: It’s the visibility gap. They traded direct line of sight for layers of management, but those layers often just pass information up without adding context or filtering noise. So the leader gets data, not insight. Lucas: Exactly. And most companies try to fix this by hiring more analysts or buying fancier software. But I want to talk about something simpler today: the weekly operating rhythm. Not a strategic offsite, not a town hall, but the ten-hour block a week where the leadership team actually looks at the numbers and solves problems together. It sounds boring, but it is the single highest leverage activity a mid-market firm can adopt. Luna: Because it forces accountability? If you show up to the same table every Monday with the same metrics, you can’t hide behind excuses anymore. Lucas: Right. Let me give you a concrete example. A regional logistics provider here in the Midwest hit forty-five million last year. They were growing fast, but margins were getting squeezed by fuel costs and labor turnover. The CEO told me he spent forty hours a week putting out fires, yet he couldn’t tell you why his customer churn rate had ticked up by two percent. He didn’t have a rhythm. He had a calendar full of ad-hoc syncs. Luna: So they implemented a structured weekly review? Did it work immediately? Lucas: Not immediately. It took about six weeks before they stopped treating it like another meeting. The first thing they changed was the agenda structure. Instead of each department head giving a five-minute update on what they did last week, they started with a fifteen-minute review of the top three risks facing the business. Risks, not updates. Updates can be emailed. Risks require discussion. Luna: That shifts the dynamic entirely. You’re moving from passive reporting to active problem-solving. But does that mean canceling all other meetings? Lucas: No, but it means decoupling information sharing from decision making. Most leaders confuse the two. They think if everyone knows the same thing, they are aligned. But alignment happens when you agree on what to do next. In this logistics case, they carved out one hour strictly for cross-functional blockers. If sales says marketing isn’t generating qualified leads, and marketing says sales isn’t following up, that debate happens in real-time with the CEO present. No post-meeting emails. Just resolution. Luna: I love that. It stops the blame game because the leader is there to facilitate, not just listen. What about the data side? How do they ensure they aren’t arguing over spreadsheets during that hour? Lucas: This is where most fail. They send the deck twenty minutes before the meeting. By then, nobody has read it, so the first thirty minutes are spent explaining the slides. The rule for this logistics firm was simple: pre-read materials sent forty-eight hours in advance. If you haven’t read it, you don’t speak until someone briefs you. It sounds harsh, but it saves two hours of wasted time. The actual meeting becomes pure analysis. Luna: Yeah, I’ve been in meetings where half the room is scrolling through their phone while someone reads PowerPoint bullets. It’s painful. So the pre-read creates discipline. Lucas: It creates efficiency. And here is the second part of the rhythm: the action item tracker. Every decision made in that weekly block must have an owner, a deadline, and a definition of done. No vague actions like 'improve communication.' That’s useless. It has to be 'John calls Sarah by Wednesday to confirm the new pricing tier.' Then, the next week, you spend the first ten minutes reviewing last week’s actions. Did they happen? If not, why? That creates a closed-loop system. Luna: It turns promises into trackable outcomes. Which means the leader can step back slightly because they trust the system? Or do they micromanage the tracker? Lucas: If they micromanage the tracker, they will kill the rhythm. The leader’s job is to ask tough questions about the blockers, not to chase individuals. In the logistics example, the CEO stopped asking 'Did you finish your task?' and started asking 'What is stopping you from finishing your task?' That subtle shift changes the tone from policing to coaching. It signals that the rhythm is a support mechanism, not a surveillance tool. Luna: That’s a crucial distinction. Coaching vs. policing. Because if employees feel watched, they’ll just pad the reports. If they feel supported, they’ll bring real problems to the table. Lucas: Precisely. And that brings us to the cultural impact. When you have a consistent rhythm, transparency becomes the default. You stop hiding bad news because you know you have to address it in front of peers every Monday. It reduces political maneuvering. People realize they can’t spin their way out of a missed target when the whole leadership team is watching the dashboard. Luna: So it actually improves morale? Even though it sounds intense? Lucas: It does, once the initial shock wears off. Ambiguity is stressful for high performers. They want to know what matters. A clear operating rhythm tells them exactly what the priorities are for the week. It reduces anxiety. In the logistics firm, employee retention actually improved after six months of implementing this. Not because pay went up, but because people felt less confused about their role in the bigger picture. Luna: Clarity is a benefit. I hadn’t thought about that angle. Usually, we focus on the financial upside, but psychological safety matters too. Lucas: It definitely does. Now, let’s talk about the practical setup. You need a dedicated facilitator for these meetings. Often, it’s the COO or the Chief of Staff. The CEO should participate, but they shouldn’t run the meeting. If the CEO runs it, everyone waits for their cue. If a facilitator runs it, the team owns the conversation. The facilitator keeps time, enforces the pre-read rule, and ensures every action item is captured. Luna: So the CEO has to get comfortable not leading the charge? That can be hard for founders who are used to driving everything. Lucas: It is hard. But necessary. The founder’s energy is better spent on external stakeholders—customers, investors, key partners—rather than moderating internal debates. By handing off the facilitation role, the founder models trust in the management team. It signals that the system works without them hovering. It’s a test of maturity for the leadership group. Luna: And if the system fails? If the facilitator isn’t good enough? That’s a risk too. Lucas: Good point. You rotate facilitators sometimes, or you train them rigorously. But mostly, you coach them. The facilitator doesn’t need to be the smartest person in the room; they just need to be the best at keeping the process clean. Think of them as the referee, not the player. If the referee lets fouls slide, the game gets messy. If they enforce the rules consistently, the game flows. Luna: I like that metaphor. Referee vs. player. It keeps ego out of the equation. Lucas: Ego is the enemy of good rhythm. Here is another tip: keep the meeting short. One hour max for the core review. Two hours if you include deep-dive workshops on specific topics. Anything longer and attention spans drop. Fatigue kills execution. If you find yourself running overtime consistently, it means your pre-read materials are insufficient or your decision-making framework is unclear. You have to fix the inputs, not extend the time. Luna: So length is a symptom of poor preparation. Makes sense. What about remote teams? Does this work differently across time zones? Lucas: It works harder. Remote teams lack water-cooler conversations, so you need more intentional touchpoints. But you also have to be stricter about cameras-on or video-participation to maintain engagement. In the logistics case, they had offices in three states. They used a digital whiteboard for the risk review, so everyone could see the issues being prioritized in real-time. It created a shared visual context that email never could. Luna: Visual context is huge for remote work. If you can’t see the person’s face, you need to see the problem clearly. Lucas: Exactly. Now, I want to pause here briefly. If these conversations have moved your work forward in some small way, honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It helps keep this show independent and ad-free, which matters to both of us. Thanks for considering it. Luna: Yeah, it really does make a difference. We appreciate it. Back to the rhythm. Lucas: Let’s go back to that risk review. Why risks? Why not opportunities? Opportunities are important, but risks are urgent. In a mid-market firm, survival usually depends on fixing leaks before you try to drill new holes. Once the top three risks are identified and owners assigned, you can pivot to opportunities. But you always start with the threats. It grounds the strategy in reality. Luna: It prevents optimism bias. Leaders tend to want to talk about wins. Talking about losses first feels counterintuitive but keeps everyone honest. Lucas: It does. And it builds resilience. If you regularly discuss failure modes, you normalize learning from mistakes. That’s a huge cultural shift for traditional companies that punish error. Here, error is just data for the next week’s review. It’s iterative improvement. Luna: Iterative improvement. So the rhythm isn’t a static report; it’s a feedback loop that evolves the business. Lucas: Spot on. And that evolution compounds. Week one might be chaotic. Week four might be smoother. By week twelve, the leadership team moves faster because they share a common language and a common set of priorities. They stop duplicating work. They stop stepping on each other’s toes. It’s operational harmony. Luna: Harmony is a great word for it. It sounds almost musical, but it’s actually quite mechanical. Structured, repeatable, reliable. Lucas: Mechanical reliability enables creative freedom. When the basics are handled by a solid rhythm, the team has mental bandwidth to innovate. You can’t brainstorm new product lines if you’re stressed about whether payroll will clear on Friday. The rhythm stabilizes the foundation so the superstructure can grow. Luna: So it’s about stability enabling speed. Got it. Do you think every mid-market firm needs this? Or is there a size where it becomes overhead? Lucas: Below twenty million, maybe it’s overkill. You can probably handle it via Slack or a quick stand-up. But once you cross that fifty million mark, the complexity exceeds informal communication. The cost of misalignment starts to outweigh the cost of the meeting. So yes, by fifty million, it’s not optional. It’s infrastructure. Luna: Infrastructure, not overhead. I like that framing. It’s like laying plumbing. You don’t see it, but without it, the house floods. Lucas: Perfect analogy. And just like plumbing, if you ignore it, the repairs later are much more expensive. So the question for listeners is: where is your company on this spectrum? Are you still relying on charisma and hustle, or have you built the pipes? Because eventually, hustle runs out. Luna: Hustle is finite. Systems are scalable. I think that’s the takeaway. Lucas: It is. And once you build the system, you can scale without losing your soul. Or at least, without losing your mind. Which is worth something too. Luna: Definitely. Thanks for walking us through the mechanics, Lucas. Lucas: Anytime. Let’s see if we can get our own rhythms sorted out before we hit sixty million. Luna: Deal. I’ll start drafting the pre-reads. Lucas: Please do. I’m terrible at reading ahead. Luna: We all know that. Lucas: Fair enough. See you next week. Luna: See you.