Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Operational Velocity

Operational Velocity artwork

Ep 14. The Wrench in the Machine: Technology as Operational Leverage

Sep 8, 202637 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Technology doesn't create value by existing in your business. It creates value when deployed against a specific constraint, with a defined metric, and someone accountable for delivering it. In this episode, Gautam Basu draws a hard line between technology as operational leverage, where it genuinely moves the P&L and technology as narrative, where it mostly moves the slide deck. From warehouse robotics delivering 2x productivity gains in weeks, to ERP implementations burning through 50-70% failure rates, to the one question that clears every boardroom fastest. This is the unsentimental, data-grounded case for deploying technology like a wrench, not a vision. The Operational Leverage Test. The three use cases actually moving EBITDA right now. And the four failure modes that have cost PE-backed businesses more money than most sponsors want to admit. If you're about to approve a technology budget, this episode is the conversation to have first. Show Notes The context. We're in a PE environment where multiple expansion is largely gone, leverage is structurally harder, and median hold periods have hit 5.8 years - the longest on record. EBITDA margin expansion through genuine operational improvement is the primary remaining value creation lever. Technology is central to that - when deployed correctly. The Operational Leverage Test. Four questions that should precede any technology investment decision: What is the constraint? What is the metric? What is the payback period? Who is accountable? If you can't answer all four before the contract is signed, don't sign it yet. Three use cases genuinely moving the P&L right now. Warehouse automation and fulfilment robotics - including the Staples Canada case where AMR deployment doubled productivity from 42 to 82 units per hour within weeks and cut cycle time by 70%. Inventory visibility and working capital release - the quieter, often higher-return play. And predictive maintenance - where IoT-enabled sensor monitoring has cut unplanned downtime by 60% in 90 days in documented deployments. Three failure modes the vendors won't mention. Buying a solution before diagnosing the problem - including McKinsey's documented case of a consumer goods company spending over $150M on a fully automated warehouse built on the wrong demand assumptions. Change management treated as an afterthought - only 21% of mid-market businesses provide adequate technology training to their people (Eurostat 2024). And integration fantasy - where "we have an open API" meets a decade of legacy systems that were never designed to talk to each other. The operating partner's lens. The pattern where the technology agenda is driven by what the sponsor needs to believe rather than what the business actually needs - and the 90-day diagnostic model that separates the 83% who hit their ROI targets from the majority who don't. Key data cited in this episode: Median PE purchase multiples: 11.8x EBITDA in 2025 (McKinsey Global Private Markets Report 2026) Median PE hold periods: 5.8 years, longest on record (PitchBook / BDO 2025 Private Equity Survey) ERP implementation failure rate: 50-70% (multiple sources, consistent across RubinBrown, Third Stage Consulting, NetSuite research) Among organisations that conducted ROI analysis before implementation: 83% met or exceeded ROI expectations (ERP statistics research, Bluelinker / Jacopo.ee 2025) Warehouse automation market: $31.2B globally in 2025, growing at ~17% CAGR (Synkrato 2026) Logistics robots sold globally in 2025: 450,000+ vs. 75,000 in 2019 - a 500% increase in six years (The Network Installers / SellersCommerce 2026) Staples Canada / Locus Robotics: 42 to 82 UPH, 70% cycle time reduction (Locus Robotics case study, February 2026) AMR payback periods: under 24 months in most commercial deployments; under 12 months in high-volume e-commerce (Locus Robotics) Unplanned downtime reduction via predictive maintenance: 60% in 90 days (documented case, virtualworkforce.ai 2025) ERP training gap: 73% of large EU enterprises provide ICT training; only 21% of SMEs (Eurostat 2024) Companies using ERP consultants report 85% success rate vs. 50% overall (RubinBrown / NetSuite) Referenced frameworks and models: The Operational Leverage Test (Constraint → Metric → Payback → Accountable Owner) Theory of Constraints (Goldratt) - constraint identification Robotics-as-a-Service (RaaS) as a capital structure shift for mid-market automation Email for Inquiries Operational Velocity is for education and general information only and is not investment, financial, legal, or tax advice, and nothing in it is a recommendation to buy or sell any security. The views expressed are the host's own, the company and figures discussed are drawn from public sources believed reliable but not guaranteed, and you should do your own research and consult a qualified professional before making any decision.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_00Great returns are in luck. They're built on the floor. Operators and investors always pushing for more. From the deal sheet signed to the systems in place. Speed without precision is just running a race. Operational velocity where execution sets the pace.

SPEAKER_01Hey, welcome to the Operational Velocity Podcast. Let me tell you about a company I know. It's an industrial distributor, solid business, roughly about 40 years old. It was family-owned, and recently it was backed by a private equity company. And they did everything right in the deal process. They had clean books, it's a reasonable multiple, and there was a real growth thesis there. And then about six months into year one of the value creation plan, a new operating partner stands up in front of the leadership team and announces, and I'm only slightly paraphrasing here, that the company is embarking on a digital transformation journey.

SPEAKER_01Digital transformation journey, those three words right there, that's where the money started to disappear. 18 months later, they spent the better part of 2 million euros on a new ERP implementation that was six months overrun, three times over budget, and had somehow managed to make their order fulfillment slower than it was on the old system. And the old system, to be fair, was running on a server that looked like it had survived a minor war.

SPEAKER_01But at least it was doing what it was supposed to do. And the new system, it had a dashboard, actually a very beautiful dashboard, but nobody was really sure what the dashboard was measuring. But it was there. It was modern and it had dark mode. Dark mode, that's what 2 million euros bought them. Now, before I go further, let me be clear about what this episode is not. This is not a Ludite manifesto.

SPEAKER_01I'm not here to tell you technology is bad or that you should run your warehouse on spreadsheets and a prayer. Though I have met companies that do exactly that, and some of them are, believe it or not, remarkably profitable, which is a whole nother conversation. What I'm here to do is draw a very hard, very deliberate line between two completely different things that the business world has somehow decided are the same thing.

SPEAKER_01The first thing is that technology deployed as operational leverage, meaning you've identified a specific constraint, you choose a tool, you define some specific metrics, and you held someone specifically accountable for the outcome. And the technology is a wrench. You know exactly what bolt you're tight in. And the second thing is technology that's deployed as a narrative, meaning you need to tell a story to your board, your investors, or your own anxiety.

SPEAKER_01And the story needed to include the word digital or AI or transformation, the technology as a prop. And the outcome at best is ambiguous. This episode is about the first thing. I'm Gotham Basso, this is Operational Velocity, and today we're going to wrench first into technology as a lever for operational value creation, where it moves the PL and where it doesn't.

SPEAKER_01And how you can tell the difference before you write the check. So let's set the table. Leverage-driven returns.

SPEAKER_01Also structurally harder because the median purchase multiples hit 11.8 times EPITA in 2025, the highest in years. And the median hold periods are now north of 5.8 years. That's the longest on record. And the exit market is still grinding. Which means what exactly? It means that if you're a GP or an operating partner or CEO of a PE backed company right now, Ibita margin expansion through genuine operational improvement is not a nice to have.

SPEAKER_01It's the primary remaining lever. I think many of the industry and consultancies all agree. So where does technology fit in that picture? Here's the tension. Every serious operating partner I know treats technology investment the same way they treat any other capital allocation decision. What constraint does this remove?

SPEAKER_01What metric improves? What's the payback period? And that's the conversation in the room when adults are running the show. But there's also a parallel conversation happening, often in the same room, sometimes in the same person, where technology is a signaling device. It signals modernity and it signals that you have a plan. It signals to the LPs that you're not sitting on a 2019 investment doing 2019 things.

SPEAKER_01And that signaling function is real. And I understand why it exists, but it's absolutely lethal when it drives deployment decisions. And here's what I mean by lethal. ERP implementation failure rates, depending on your source, run somewhere between 50 to 70 percent. Think about that, 50 to 70 percent. So, in other words, if you flip a coin before starting to make a major enterprise software implementation, your odds are about as good as just going with the coin.

SPEAKER_01So most ERP projects exceed their initial budgets by three to four times, and most timeline extensions run 30% or more beyond the original schedule. And the number one cause of these failures, not the software, not the vendor, the number one cause is a lack of clear value creation thesis going on. They didn't know what problem they were solving. They knew they needed a system, they just didn't know why.

SPEAKER_01Now contrast that with a business that approaches the same investment differently. Among organizations that conducted a proper return on an investment analysis before implementation and had been live for over a year, 83% reported meeting or exceeding their ROI expectations. 83%. So that delta between 50% failure and 83% success is not technology.

SPEAKER_01It's not even vendor selection. It's problem clarity. You have to know what you're fixing. So before any technology conversation in any portfolio company or acquisition target, I want to run what I call the operational leverage test. And there are four questions, basically simple questions, and they're quite devastating in their simplicity.

SPEAKER_01So question one what is the constraint? Not the problem, not the pain point, not the area where things could be better, the constraint. The one thing, if removed, unlocks capacity, margin, or throughput in a measurable way. Ellie Goldrat, the author of the goal, called it the bottleneck. In supply chain, we call it the constraint.

SPEAKER_01Whatever you call it, you need to name it specifically. Not our inventory management is inefficient. Specifically, we are carrying 43 days of inventory on our top 50 SKUs against an industry benchmark of 28 days. And that excess working capital costs us approximately 800,000 euros annually in carrying cost and obsolescence write-offs. Now that, folks, is a constraint.

SPEAKER_01That's a target, and now you can build a case for the technology. Question number two is what's the metric? If you cannot name the metric before you deploy the technology, you cannot evaluate the technology after you deploy it, full stop. The metric needs to be specific, measurable, time bound, and causally connected to a PL line. Not we'll be more efficient, but really specific.

SPEAKER_01Things like picks per hour improves from 42 to 75 within 90 days of deployment. Not we'll build better inventory visibility, but more specifically, inventory carrying days drop from 43 to 30 within six months, releasing approximately 400,000 in working capital. The metric is your contract with the technology. Without it, the conversation after deployment is entirely political.

SPEAKER_01But with it, it's factual. The third main question is what is the payback period? And this is where the adults separate from the enthusiasts. You see, anyone can get excited about what a technology does in a demo. The question is, at what point does the cost of acquiring, implementing, and running this technology become less than the value it generates?

SPEAKER_01For example, in warehouse automation, well-deployed autonomous mobile robots are delivering high payback in under 24 months in most commercial deployments. And some high-value e-commerce operations are seeing payback inside 12 months. That's a real investment case. But those numbers depend entirely on the baseline. What's your current cost per order?

SPEAKER_01And what's your current pick rate? What's your labor turnover rate? Because if you're running 36% annual turnover in your warehouse workforce, which is the industry average, by the way, the training cost alone is a variable that dramatically changes your automation economics. The payback period forces you to be honest about your baseline. And most businesses are much hazier about their baseline than they should be, which is itself a technology problem, usually a data visibility problem.

SPEAKER_01But let's not get circular. The fourth main question is who is accountable? Not who is sponsoring the project, not who signed the contract, who is accountable for delivering the metric by the date we agreed. This is the question that clears the room fastest. Because in a lot of technology implementations, accountability is diffuse. The IT team is accountable for the implementation, the operations team is accountable for the adoption, the vendor is accountable for, well, something.

SPEAKER_01Finance is watching, and when the metric is missed, which it frequently is, everyone has a very compelling story about why it was someone else's fault. So one owner, one metric, one deadline, that's the operational discipline. If you can answer all four of those questions: constraint, metric, payback, accountable owner before you deploy, then you're in the minority.

SPEAKER_01And you are dramatically more likely to be in the 83% who hit their ROI targets than the 50% who flame out on implementation. So let's get into the meat of it. Three categories where technology is genuinely, demonstratably moving the PL in industrial and distribution businesses right now. Not theoretically, not a pilot that will scale next year, but now.

SPEAKER_01So I'm going to start here because the data is extraordinary and the failure modes are instructive. The warehouse automation market, robotics, AMRs, automated storage and retrieval, goods-to-person system hit roughly$31 billion globally in 2025 and is growing at nearly 17% annually. Over 450,000 logistical robots were sold worldwide in 2025.

SPEAKER_01And in 2019, that number was 75,000. That is a 600% increase in six years. And this is not a nascent trend. This is adoption at scale. What are the operational outcomes? Properly deployed automation and fulfillment operations delivers a 21 to 35% increase in productivity. PIC accuracy moves towards 99%, which matters because returns cost you money, rework costs you time, and customer dissatisfaction costs you both.

SPEAKER_01Labor cost per order drops meaningfully. Safety instance, and this is the one that surprises people, drops by about 25%, which has a real insurance and liability implication. Let me give you some concrete examples. Staples, Canada, a hundred and forty thousand square foot fulfillment center in Vancouver, 29-year-old building, three-mile-long conveyor system that was, by their own admission, old, difficult to maintain, and very costly.

SPEAKER_01They replaced it with autonomous mobile robots. And within weeks, not months, weeks, productivity went from 42 units per hour to 82 units per hour. Cycle time dropped 70%, and because the robots reduce overtime demand, the workforce finish their ships on time. And that last point is not soft. That's a labor cost line. Now here's the important nuance.

SPEAKER_01Staples Canada did this inside an existing building. They didn't tear out the structure. The robots actually navigated the same aisles and workstations the employees already used. That is the deployment model that works at the mid-market level. You are not building a greenfield automated warehouse, and that's a$150 million capital project that requires a very specific scale and volume assumption to underwrite.

SPEAKER_01And it's been documented at least one major consumer goods company that got that math wrong, specifically. You're deploying flexible automation against a specific throughput constraint inside an existing operation. The other development worth flagging here is robotics as a service, or RAS. Instead of a large capital purchase, you subscribe. The robots are an operating expense, not a capital expense.

SPEAKER_01And 72% of logistics firms are either already using or planning to adopt subscription-based robotics contracts. And for mid-market businesses where capital allocation is tight and PE sponsors are watching the balance sheet, this changes the investment calculus significantly. And there's another case around inventory visibility and working capital. And this one is quieter than robots, but it is probably the single highest return technology investment available to most industrial and distribution businesses.

SPEAKER_01Here's the brutal fact about inventory in most mid-market businesses. They don't actually know what they have, they know what the system says they have. Those are often different numbers, and the difference lives in the gap between physical counts, system updates, and the various workarounds that accumulate over years of manual processes. What does it cost? A B2B distributor with a revenue of 50 million euros and a 40-day inventory position, which is pretty typical, has maybe 7 or 8 million euros tied up in stock.

SPEAKER_01If better inventory management, better forecasting, better replenishment logic, and better visibility lets them reduce that to 30 days, they've released 3 to 4 million in working capital. That is not margin improvement. That is cash immediate, real cash that reduces revolver utilization, improves free cash flow, and an leverage buyout structure directly affects your debt service capacity.

SPEAKER_01Boston Consulting Group data supports this. Enhanced supply planning can cut inventory levels by 5 to 20%, improving margins by an additional 25 to 50 basis points on top of the working capital release. The technology here is not exotic. It's basically a WMS or warehouse management systems as we know them. And they are now near universal at scale, with over 90% of larger operations running them.

SPEAKER_01But in the mid-market, particularly in owner-operated business coming into PE ownership, you frequently find businesses still running inventory on spreadsheets or on legacy systems that don't talk to each other. Or in tribal knowledge of warehouse manager who has been there since 2003 and knows where everything is, which is great until he retires, of course. The technology investment here is about data integrity first.

SPEAKER_01Before you optimize anything, you need to trust the data. And that's usually the unsexy, underestimated first step that kills implementation when it's skipped. Case number three is around predictive maintenance and asset utilization. This third category, it's less glamorous than warehouse robots, more impactful than people expect. In any asset-intensive business, whether it's manufacturing, processing, heavy distribution, unplanned downtime is one of the most expensive line items that doesn't appear as a line item.

SPEAKER_01It appears as production shortfalls, emergency maintenance, customer penalties, and the kind of operational chaos that wrecks your workforce scheduling for three days after a single equipment failure. IoT enabled predictive maintenance, sensors on critical equipment feeding real time data to a monitoring system that flags anomalies before they become failures, is now a genuinely accessible technologies at the mid market level.

SPEAKER_01The documented outcome in one well signed Case study, a facility using AI-driven censored monitoring, reduces unplanned downtime by 60% within 90 days. Think about that, 60% in 90 days. But also think about what that means for a business running two or three shifts on a production line where unplanned downtime costs you conservatively 5,000 to 10,000 euros per hour. If your average unplanned incident costs you 20 hours of production per month, and you can cut that by 60%, you've recovered eight hours.

SPEAKER_01That's 40,000 to 80,000 euros per month in recovered production capacity. At your Ibita margin, that falls straight to the bottom. The constraint being addressed here is not equipment failure per se. It's the information asymmetry between what your equipment is about to do and what your maintenance team knows about. Technology closes that gap. Predictive replaces reactive.

SPEAKER_01The wrench analogy holds. You're not buying a robot, you're buying earlier warning. And that's the lever. All right, let's talk about failure. Because this is where the real education lives. I said at the top of the episode that somewhere between 50 and 70% of ERP implementations fail. That number is so consistently cited across so many sources that I've just accepted it as a structural feature. Like how some percentage of every flight will be delayed, or how every home renovation will cost more than estimated.

SPEAKER_01It's almost like a law of physics at this point. But the interesting question is why? And the answer is almost never technology. I think the first failure mode is buying a solution before diagnosing the problem. This is the most common, and it usually starts with a vendor. A software company sends a very capable salesperson to visit your company. The salesperson shows a beautiful demo. The demo shows things the business doesn't currently have, such as real-time dashboards, integrated data, automated reports.

SPEAKER_01And the management team gets excited. The excitement is real, it's human, it's understandable. What the business is seeing in the demo is relief from the pain they experience every day. The problem is that they've jumped from this looks like it solves my main pain directly to purchase, without the intermediate step of defining what specifically the pain costs and what specifically the solution needs to deliver. So they buy the system, they implement a system, and then they discover that the system solves a slightly different problem than the one they had.

SPEAKER_01Or that the problem they thought they had was actually a symptom of a deeper process failure that software cannot fix. It's been documented that one consumer goods company spent more than$150 million to build a single, fully automated warehouse designed to serve both retail and e-commerce. The forecasts for the balance between those channels were completely wrong, and the facility ended up primarily handling wholesale fulfillment, leaving the expensive automation for case and part picking sitting underutilized.

SPEAKER_01The technology actually worked perfectly. The problem definition was wrong. The second failure mode is change management as an afterthought. We know that technology doesn't run a business. People run businesses using technology. This distinction is obvious when stated, but it's consistently ignored in practice. The Eurostat data on this is striking. While 73% of large EU enterprises provide ICT training to their staff, only 21% of SMEs do the same.

SPEAKER_01Just 21%. And in the mid-market and lower middle market, the business that private equities most frequently acquire, fewer than one in four companies is actively building the internal capability to use the technology. What that produces in practice is a warehouse manager who has been with the business for 15 to 20 years knows the old system intimately and deeply resents the new system. Not because the new system is bad, but because nobody asks his opinion, nobody explained why it's happening, and when he raises problems in the first month of GoLive, the implementation team tells him it's a change management issue and moves on.

SPEAKER_01Three months later, his team had developed workarounds that partially break the logic the system relies on. The system's data's quality degrades and the dashboards stop being trusted, and the investment case quietly unravels. Successful implementations require internal champions, people the vendor consultants called super users, who are invested in making the system work and are empowered to drive adoption. That's not a technology cost, that's a people cost, and it is consistently under resources.

SPEAKER_01The third major failure mode is what I call the integration fantasy. Because every technology vendor will tell you that their system integrates with everything. We have an open API. We're fully compatible with your existing stack. The integration is straightforward. While these statements may be technically true and practically misleading at roughly the same rate, integration is where technology projects go to die quietly and expensively. Here's the actual dynamic.

SPEAKER_01Your business has accumulated technology over the years, sometimes decades. And you have a legacy ARP that was implemented in 2009. You have a WMS that was added in 2015, and you have a CRM that sales insisted on in 2018. And you have a transportation management system that was bolted on during COVID. None of these were designed to talk to each other. And some of them are on premise. Some of our cloud, some are running versions that haven't been updated since the Trump administration.

SPEAKER_01The new system has to connect to all of them. And the integration cost is always underestimated, almost always overruns, and almost always creates data quality problems at the seams between the systems. And this is not a technology problem. This is a systems architecture problem that technology reveals. And the cost of not solving it before implementation is paying to solve it after, at three times the price and half the patience.

SPEAKER_01So before any significant technology implementation, the first deliverable should be a technology inventory and an integration map. What do you have? What does it talk to? What are the gaps? And that document, honestly produce, will save you more money than the technology itself. And let me speak now directly to the operations leaders and the investors in a room for a moment. I know you're here. I can smell the carry.

SPEAKER_01There's a pattern I see in PE back technology conversations, and it concerns me because I think it's destroying real value at scale. And the pattern looks something like this. Year one of the whole, the technology agenda is driven by what the sponsor needs to believe about the business, not by what the business actually needs. The narrative requirement, we have a tech-enabled value creation plan precedes the diagnostic. And once you've set that narrative in motion, the sunk cost of it creates enormous pressure to continue even when the data says stop.

SPEAKER_01The countermodel, the one that actually works, starts with what I'd call an operational technology diagnostic. Before you buy anything, you spend 60 to 90 days understanding three things. What are the actual operational constraints? What is the current technology landscape, including gaps and integration risk, and what is the internal capability to adopt and sustain new technology? That last one is the one most people skip: technical capability, change management capacity, digital literacy in the workforce.

SPEAKER_01And these are not soft factors. These are basically hard constraints on what the technology can actually deliver. The businesses that outperform on technology ROI share three characteristics. Number one, they define the problem before they choose a solution. Number two, they match the complexity of the technology, the capability of the organization to absorb it. And number three, they tied a portion of the management incentives to the successful delivery of the technology's ROI.

SPEAKER_01The last one has a remarkable clarifying effect on everyone's priorities. And there's a couple of data points that state that companies that embed technology ROI into management KPIs and conduct quarterly tracking against those KPIs are dramatically more likely to hit their targets than those that don't. Not slightly more likely, dramatically more likely. The holding period is long now, 5.8 years median.

SPEAKER_01And that means you have time to do this right, and you also have time to do it catastrophically wrong. The choice of which of those you do is made in the first 90 days. And I want to make one more point before we land this episode, and it's slightly philosophical, so please bear with me. There's a reason I insist on framing technology as an operating leverage rather than technology as strategy. And it's not semantic, it's about where authority lives.

SPEAKER_01When technology is framed as a strategy, it tends to migrate upwards. It becomes a board conversation, it becomes a GP priority. It becomes a C-suite initiative with a name and a budget and a steering committee. All of that is a very expensive process infrastructure around a question that should be answered at the shop floor, the warehouse floor, the plant floor. So where is the constraint? Ask the plant manager. Where does the process break?

SPEAKER_01Ask the shift supervisor. Are we losing time, losing inventory, losing throughput? Ask the people doing the work. Technology deployed from top down because the board wants to see a digital agenda almost universally underperforms relative to technology deployed from constraint upward. Because the operations team identified a specific friction and the organization chose to address it. And this is why I call it a wrench, not a vision. A wrench is a tool for a specific job.

SPEAKER_01You pick it up because you have a specific bolt to turn. You don't pick up a wrench and then wander around looking for things it might be useful on. Although I'll be honest, I have absolutely done that in a hardware store, but that's a personal feeling, not a business model. The business that use technology best treat it the way a good operations leader treats any other resource. Ruthlessly, instrumentally. It either moves the PL or it doesn't.

SPEAKER_01If it does, you deploy it, you measure it, you scale it. If it doesn't, you cut it. There's no romance, there's no journey, there's just a number. So let me close with the takeaways and I'll make this genuinely actionable because I have very little patience for podcast episodes that tell you interesting things and they leave you with, think about this. I think we're past that. If you're deploying technology in a company right now or about to, remember four things.

SPEAKER_01First, run the operational leverage test. Constraint, metric, payback, accountable owner. If you cannot answer all four before the contract is signed, do not sign the contract. Not yet. Go back and do the diagnostic work. Second, produce a technology inventory integration map before any major implementation. Know what you have, what it talks to, and what happens at the seams.

SPEAKER_01Third, budget for change management as a first class cost, not a residual. 21% of mid-market businesses provide adequate technology training to their people. The other 79% are funding failure. Change management is not a soft cost, it is the hard infrastructure of technological adoption. Fourth, tie management incentives to the ROI of the technology, not to the implementation of the technology.

SPEAKER_01There is a difference. Going live is not delivering value. Delivering the metric is delivering value. Why are the incentives to the metric? The businesses that do these four things are in the minority. They are the 83% who hit their ROI targets. The rest are in the majority. They have beautiful dashboards, incentive documentation, and a complicated story about why it's taking longer than expected to see the benefits.

SPEAKER_01Technology is a wrench. Pick the right bolt, tighten it properly, measure the result, move to the next bolt. That's operational velocity. I'm Gotham Bassoo. Thank you for being here. If this was useful, share it with someone who's about to approve a technology budget. They'll thank you or resent you. Either way, you've done your part. See you on the next episode.

SPEAKER_00Great returns aren't luck. They're built on the floor. Operators and investors always pushing for more. From the deal sheet signed to the systems in place. Speed without precision is just running a race. Operational velocity where execution sets the pace.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Ep 24. Alligo: Selling What Runs Out, Nordic Serial Acquirer

    Nov 17, 202643 minAudio

    Every other company in the Bergman & Beving family bets on the entrepreneur operator. Alligo bet on the platform. It was formed by the 2020 merger of Swedol and Tools. It now runs one ERP, one logistics network and one...

    Credit the people on this episode

  2. Ep 23. Lagercrantz: From Solely Distributing to Owning the Product, Nordic Serial Acquirer

    Nov 10, 202642 minAudio

    In March 2005, Lagercrantz earned an operating margin of 0.3%. Today it owns around 85 niche industrial companies, earns about 18%, and has set a new earnings-per-share record every year for more than fifteen years....

    Credit the people on this episode

  3. Ep 22. Addtech: The Daughter Serial Acquirer who Outgrew it's Parent

    Nov 3, 202655 minAudio

    In 2001, Bergman & Beving split itself in three. One of its daughters, Addtech, listed eight days before 9/11 with fifty subsidiaries, a nine-person head office and a telecom crash already under way. Twenty-five years...

    Credit the people on this episode

  4. Ep 21: Bergman & Beving: Grandfather of Nordic Serial Acquirers

    Oct 27, 20261 hr 8 minAudio

    Meet the grandfather of Nordic serial acquirers, Bergman and Beving. Before Addtech, Lagercrantz, AddLife and Momentum Group, there was one Swedish technical trading house, founded in Norrköping in 1906 by two...

    Credit the people on this episode

  5. Ep 20. Brad Jacobs: XPO, Logistics Roll-Up, Build It, Run It, Break It Up

    Oct 20, 202648 minAudio

    In 2011, Brad Jacobs bought control of a $158 million Michigan-based logistics company at approx. $7 a share. Fifteen years later, that one share has become three NYSE companies: XPO, GXO and RXO. This episode tells the...

    Credit the people on this episode