I am a direct buyer looking to acquire and operate one established essential services business for the long term. Managed IT services — the MSP model — is one of the sectors I am focused on. I am not a competitor looking to consolidate, not a broker, not a private equity group with a fixed exit timeline, and not an overseas roll-up platform. I am based in Sydney and looking across Australia.
The goal is continuity: keep your engineers doing the work they are good at, your managed services clients well served under their existing contracts, and the business operating properly under an owner who understands how to run a contracted, people-heavy service operation.
A well-run managed IT services business has qualities that are hard to replicate. Monthly recurring revenue is the core of the model — businesses pay a predictable per-seat or per-device fee every month for the IT function they cannot run in-house, and that revenue renews as long as the service keeps the phones answered and the tickets closed. Switching MSPs is genuinely painful: new tenants to re-document, credentials to reset, RMM agents to redeploy, SaaS stacks to re-onboard. Clients stay for years because the cost of changing is measured in months of disruption, not just dollars. Cyber exposure and compliance expectations are pushing more SMBs into the managed model every year, not fewer. These are the structural reasons a well-run MSP is such a stable, cash-generative business.
Before starting ALX, I founded and ran a commercial cleaning business. I managed a distributed service team, chased invoices from slow-paying clients, dealt with the early-morning call when someone did not show up, and learned what makes a contracted B2B service work: reliable people, consistent delivery, and the discipline to meet service commitments every day without drop-off. A managed IT services business runs on the same fundamentals — contracted monthly revenue, a team who are the real asset, clients who stay because the service stays reliable, and an owner who is ultimately accountable for whether the ticket queue moves. The specialist technical depth of running an MSP sits with your engineers and that is exactly what I would be preserving, not replacing. The commercial and operational side of running a recurring-service business is ground I have walked.
In most MSPs with a capable engineering team, the technical delivery keeps running while I would typically take over the commercial and ownership side: client relationships and renewals, vendor and distributor partnerships, financial management, quoting, business development, and long-term planning. Technical escalation stays with the senior engineers who know the client environments. I bring commercial leadership, not a second laptop.
I am not buying the business to rip out the stack or consolidate the team. The PSA, the RMM, the Microsoft partner arrangements, the distributor relationships — the plan is to keep what works. The value is in the team, the MRR book, and the reputation you have built. Change for its own sake destroys that value, not creates it.
The handover happens at your pace. Most transitions include a period where you introduce top clients, walk me through the MRR book and vendor partner relationships, and make sure there is a clean transfer of commercial knowledge. Some owners want a clean break; others want to stay involved for a few months to ensure a smooth transition. Both work.
Good tier 2 and tier 3 engineers are hard to find and harder to replace. Stability is the first priority. The plan is to keep the team, their conditions, and their working arrangements in place from day one. A new owner who disrupts a working engineering team destroys the value of what he just bought. I plan to be visible and accessible early, earning trust rather than demanding it.
It stays. Whether it is Autotask, ConnectWise, HaloPSA, N-able, Kaseya, Datto, or something else — if it is working, there is no reason to change it. Migrating a PSA or RMM mid-transition is a straight loss: months of disruption, data quality risk, and unnecessary churn in a team that just changed ownership. Same principle for Microsoft partner status, distributor relationships, and cyber tooling.
That is the pattern I see most often — the founder wearing several hats that do not naturally belong together. The commercial and account-management side is the role I would step into: client relationships, renewals, quoting, vendor management, financial oversight. Technical escalation needs to live with a senior engineer or technical lead, and we would want that capability clearly in place (or built during the handover) before settlement. If it is one of the roles you want to keep doing for a while, that is fine too.
In managed services, the day-to-day relationship is with the service desk and the engineer who answers the Friday afternoon ticket, not the owner. What keeps a client renewing is reliable service and a stable team. If the engineers stay and the response quality stays, the contracts are far more likely to continue. Joint introductions from you to key client contacts during the handover reinforce that continuity.
These are addressed in diligence and transition planning. Some sit with the business entity and transfer with it; some require re-registration or novation on change of ownership; cyber insurance is typically re-underwritten at transaction. I would not proceed unless these are in good order, and where there is work to do, it is planned for during the transition rather than left as a surprise after settlement.
Yes. Nothing happens without your say-so. Before any business information is shared, we sign a mutual confidentiality agreement. Your staff, your clients, your vendor partners, and your competitors will not know we are talking unless you choose to tell them.
That is completely fine. Many owners I speak with are thinking about it but not ready to act. I am happy to have a conversation now, answer any questions, and stay in touch. There is no pressure and no timeline on my side.
Even if you are not ready to sell today, I am happy to talk. No pressure, no obligation.