For years, the way I ran IT for clients lived entirely in my head. Every process, every checklist, every connection between systems. CX365 is the story of how I turned that into a platform — and why it changed everything.
For a long time, the operating system for running a managed IT business existed entirely inside my head.
I knew which client was due for a review. I knew which domains were expiring in the next 90 days. I knew which businesses had cyber insurance policies coming up for renewal, which ones were running on phone systems that needed replacing, which internet connections were approaching their contract end. I knew who had compliance obligations and which ones were being met.
I held all of it — the whole picture of every client, every system, every obligation — in mental models that had been built up over years of doing the work.
This is fine when you are a small operation and you are personally across every engagement. It is not fine when you are trying to scale, when you are trusting others to carry parts of the picture, or when the complexity of the client base grows beyond what any one person can reliably hold in their head.
CX365 is what happened when I decided to stop relying on my memory and start building something that could hold the picture properly.
The Problem I Was Solving
Let me describe what managing a client’s technology actually involves — not the technical work, but the operational coordination.
There are the users and devices: who has access to what, which machines are assigned to which people, who has left the business and whether their accounts have been properly offboarded. There are the groups and permissions: what each person should be able to see and do, and whether those permissions are current and correctly set.
There is the domain infrastructure: when domains expire, whether DNS records are correctly configured, whether the domain is registered in the right entity’s name and accessible to the right people when something needs to change.
There is the internet and connectivity layer: which provider, what contract terms, what service level, when the contract renews. There are the phone systems: the same questions, plus the user configuration, the call routing, the mobile app deployment, the billing.
There is the website: hosting, SSL certificates, CMS platform, whether the business is exposed because something has not been renewed or because the platform has not been updated.
There is cyber security: what tooling is in place, whether it is current, what the policy posture is, what the insurance coverage looks like, whether the coverage actually matches the real exposure.
There are the policies themselves: acceptable use, data handling, password requirements, incident response. Whether they exist, whether they are current, whether staff have been trained on them.
There is ticketing and support: the history of what has been done, what is pending, what has been recurring, what the patterns tell you about underlying problems.
There is planning: what the technology roadmap looks like, what needs to be replaced or upgraded in the next 12 to 24 months, what the budget implications are.
And there are expenses: what the client is spending across all of their technology, whether they are getting value from everything they are paying for, whether there are redundant subscriptions or vendor relationships that have been duplicated.
That is the complete picture of a managed IT engagement. Every single one of those elements, for every single client, in a way that allows you to be proactive rather than reactive — to catch the domain expiry before it causes an outage, to flag the insurance gap before something happens that makes it relevant, to plan the hardware replacement before the old machine fails at the worst possible time.
For years, I was managing all of that out of a combination of memory, spreadsheets, and scattered tools. It worked — barely — but it was fragile, it did not scale, and it depended entirely on me staying across everything personally.
The Moment I Decided to Build Something
There was not a single dramatic incident that prompted it. It was more the accumulation of near-misses and the growing sense that the informal system was going to fail in a way that mattered.
A domain renewal that almost slipped through because the reminder went to an old email address. A cyber insurance policy that a client renewed without consulting us, into a product that did not actually cover their real exposure because the insurer had changed the terms. A hardware audit that revealed a server warranty had expired eighteen months earlier — something I would have caught if I had been tracking it properly, something that had slipped because it was stored in a spreadsheet I had not looked at in four months.
Each of these was recoverable. None of them caused a serious outcome. But together they told me that the informal system was operating close to its limits.
I also kept watching other MSPs — the ones I had worked for, the ones I competed with, the ones I compared notes with in the industry — and seeing the same fragmentation everywhere. Different tools for ticketing, for documentation, for monitoring, for billing, for security. Information siloed across platforms that did not talk to each other. Engineers who had to look in four different places to get the full picture of a client’s environment.
The technology for running technology businesses was, in many cases, worse than the technology those businesses were running for their clients. That struck me as an unsatisfactory irony.
Building the Operating System
The concept behind CX365 was to take everything that existed in my head — every process, every checklist, every connection between the elements of a managed IT engagement — and externalise it into a structured platform.
Not a collection of tools. Not a better set of spreadsheets. An operating system for managing technology relationships, where every element was connected to every other element, where information entered once was visible everywhere it was relevant, and where the platform would surface what needed attention rather than requiring someone to remember to look.
Users and devices connected to groups and permissions. Groups connected to policies. Policies connected to compliance requirements. Compliance requirements connected to cyber insurance. Cyber insurance connected to the technology stack. The technology stack connected to planning and budget. Planning connected to support tickets and patterns. Support patterns connected back to the technology decisions that created them.
The whole picture, in one place, accessible to everyone on the team who needed it.
Building this was not a small project. It involved mapping the full operational logic of how we run client engagements, translating that into platform architecture, and then building the discipline to actually use it — to enter the information, to keep it current, to run the work through the system rather than around it.
That discipline is the hard part. Tools are easy. Habits are hard. Getting a team to operate through a new system, rather than falling back to the informal patterns they are comfortable with, requires sustained management attention.
What CX365 Actually Contains
Today, CX365 covers the full picture of a managed technology engagement:
Users and devices — every person, every machine, every software licence, all connected. When someone joins a business, we provision from a template. When someone leaves, offboarding runs a checklist that covers every system they had access to. Nothing falls through the gap because the gap is visible.
Groups and permissions — access control documented and reviewable. The question “who currently has access to the finance shared drive?” has an answer, immediately, without involving an engineer.
Domains and DNS — every domain, every registrar, every expiry date, every DNS record. Alerts go out well in advance of renewals. Changes are documented. Nothing expires because someone forgot.
Internet and phone — contracts, providers, terms, renewal dates. We are reviewing these ahead of the renewal rather than discovering the automatic rollover after it has happened.
Web and hosting — certificates, platforms, hosting arrangements. SSL expiry alerts. CMS update status. The things that cause embarrassing outages when they are missed.
Cyber security — tooling status, policy documentation, training records, insurance policy details. All in the same place, all connected to the same client record.
Policies — IT policies that are current, versioned, and linked to the users who have been trained on them.
Tickets and support — the full history of what has been done, what is pending, and what the patterns indicate about underlying issues.
Planning — the technology roadmap, hardware replacement schedules, upgrade planning, budget projections.
Expenses — what the client is spending across every technology line item, mapped and reviewable. The question “are we getting value from all of this?” has an answer.
What It Changed
The most significant change was not operational efficiency, though that improved substantially.
It was the quality of the client conversation.
When you have the full picture of a client’s technology environment in a structured, current system, the quarterly review conversation is completely different. You are not giving them a status update. You are giving them a strategic view — here is where you are, here is what has changed, here is what is coming, here is what we recommend and why.
Clients who are given that view understand their technology investment in a way that clients who receive only reactive support never do. They make better decisions. They act on recommendations. They understand the value of what they are paying for because they can see it, structured and explained, rather than trusting that something invisible is being done on their behalf.
That visibility, I have come to believe, is the core of a good managed IT relationship. Not just the technical work — the understanding.
CX365 is how we produce that understanding at scale, consistently, across every client, without depending on everything living in one person’s memory.
I spent years carrying this in my head. Getting it out onto a platform was one of the best decisions I have made in building this business.
