When Kathryn Nguyen joined Apex Wholesale Distribution as chief operating officer in early 2023, she inherited a business running on a patchwork of systems that had accumulated over two decades: a locally hosted ERP that required a dedicated server room, a separate invoicing platform that didn't talk to it, and a customer portal built in 2016 that had never been updated. Her operations team spent roughly 15 hours a week manually reconciling data between the three. "We were essentially doing digital transformation in reverse," she says. "Every new tool we added made the problem worse."
Within eighteen months, working with Melbourne-based managed service provider Clearline Technology Group, Apex had consolidated onto a cloud-native stack, automated its reconciliation processes, and cut its order-to-invoice cycle from four days to six hours. Revenue didn't change. Margin did — up 3.8 percentage points, almost entirely from labour reallocation.
Apex's experience is increasingly common, but it is also more instructive than most digital transformation case studies because of what it reveals about the role a managed service provider actually played. Clearline did not simply execute a migration brief. Their team spent six weeks mapping Apex's workflows before writing a single line of configuration. They identified two processes that Nguyen's team had assumed needed to be digitised but that, on analysis, were better candidates for elimination altogether.
When Strategy Precedes Technology
The canonical failure mode of digital transformation projects — and the research is consistent on this — is technology selection that precedes problem definition. A 2024 study by Deloitte Australia found that 61 percent of mid-market transformation projects that ran significantly over budget had made platform decisions before completing a current-state assessment. The projects that stayed on track almost universally involved an external partner who slowed the business down in the planning phase.
This is the shift in how the better managed service providers now position themselves. The transactional model — a business identifies a problem, an MSP prices a solution — is giving way to something closer to embedded advisory. Firms like Telstra Purple, DXC Technology's Australian arm, and a growing cohort of mid-tier specialists are deploying dedicated technology strategists alongside their engineers. These are people whose job is to understand a client's competitive position, not just their network topology.
For the client, the practical implication is that the MSP carries institutional knowledge across the organisation's technology history. They know why the legacy system exists, who depends on it, and what a migration will actually disrupt — not just in the IT department but on the loading dock or in the sales team.
The Change Management Gap
What surprises many executives who have been through a transformation is how much of the project budget — and how much of what determines its success — has nothing to do with technology.
Marcus Bellamy, a digital transformation director at consulting firm Nous Group who has worked on more than thirty Australian mid-market projects in the past five years, estimates that change management accounts for around 40 percent of project risk and, in most budgets, less than 10 percent of spend. "The technology almost always works," he says. "What fails is the human system around it. People don't use the new tool, or they use it wrong, or a middle manager quietly maintains the spreadsheet because they don't trust the new system yet."
Managed service providers who recognise this now build change management capability into their service offering — not as a separate consulting engagement but as part of the base delivery. That includes structured training programmes, adoption dashboards that track which features are actually being used, and feedback mechanisms that surface resistance before it hardens into workarounds.
Measuring What Matters
For businesses considering a transformation engagement, the due diligence question that cuts through the most marketing noise is simple: ask the MSP how they measure success at month twelve, not at go-live.
Go-live metrics — system uptime, data migration completeness, training completion rates — are necessary but not sufficient. The more revealing indicators are operational ones: has the process the technology was meant to improve actually improved, and by how much? Nguyen's 3.8-point margin improvement is the kind of number that answers that question. It also, she notes, made the board conversation about the project's cost considerably easier in retrospect.
The managed service providers building durable client relationships are the ones who commit to those downstream metrics from the outset, and who are willing to have their fees partially tied to them. That is still uncommon in Australia — but it is no longer rare.