Welcome to my blog
Join me on my journey as I share my insights and experiences on all things Apple, Business and Entrepreneurship!
Join me on my journey as I share my insights and experiences on all things Apple, Business and Entrepreneurship!
A major part of that transition is operational visibility. If teams are split across different systems, it is nearly impossible to create real shared support. That is why integrating core tools, especially something as central as a ticketing platform, becomes so important. Once everyone can see the same workload in one place, the business is in a much better position to distribute responsibility and reduce dependence on one person or one small group.
That is where many leaders feel the strain of growth. A bigger team naturally brings more moving parts, more people involved in decisions, and more situations where assumptions can create confusion. What once felt simple can start to feel chaotic, not because the business is broken, but because the work now depends on clearer alignment between more people. Without consistent communication, that kind of growth can quickly turn discomfort into unnecessary friction.
In my case, the decision to merge was not about chasing a one-time payout. The larger goal was to keep building toward something that would have been difficult to achieve alone: a broader, more capable Apple-focused managed service organization with the scale to grow well. After exploring other growth paths, including outside capital and slower independent expansion, the merger became the most practical way to keep moving toward that vision without taking on a level of risk that would have slowed the business down.
That creates a difficult adjustment for any founder who has spent years making the final call. Once the business is part of something larger, you may still have influence, but you are no longer the only person driving the direction. There will be moments when decisions are made that you would not have made yourself. That is one of the hardest realities of moving from business owner to part of a broader leadership team. You still care about the outcome, but you now have to work through a structure where...
That adjustment is rarely comfortable. Owners are often effective because they are decisive, independent, and deeply invested in how the business is run. Those same qualities can make the transition into a broader organization more difficult. The challenge is not just learning a new title or reporting structure. It is learning how to lead when you no longer control every part of the system.
One of the biggest adjustments after a sale is moving from owner-operator to team player. When you run your own business, you are used to setting the pace, defining the standards, and making the final call. Inside a larger organization, that independence narrows. Decisions now sit inside a broader structure, and even when the long-term strategy makes sense, the transition can still be uncomfortable. It takes time to stop thinking like the only decision-maker and start working inside a larger operating model.
That does not mean every business should promise unlimited after-hours support. Clear boundaries still matter. In our case, standard business hours remain the expectation, and serious after-hours issues can be escalated through broader support coverage when needed. Most off-hours requests are not major outages anyway. They tend to be quick questions, basic troubleshooting, password resets, or a request for reassurance about something suspicious. A lightweight communication channel works well for exactly those moments.
What makes the model work is not only the Apple integration. It is the combination of Apple Business Chat with a shared messaging platform that can route, store, and manage conversations across the team. In our case, that means using a platform that treats text and chat like a shared support inbox rather than a personal device feature. Multiple technicians can see the same thread, reply from the same business identity, and keep the conversation attached to the organization instead of one individual employee.
That is one of the first major pitfalls of team growth: the time cost of making someone useful. Unless a new team member is a near-perfect fit and fully ready on day one, the business has to absorb a period where capacity actually feels tighter, not better. The owner is still carrying delivery responsibility while also investing time in building someone else up to speed. For small teams, that tradeoff can be more expensive than it first appears.
That matters because most security failures do not begin with highly sophisticated attacks. They often start with routine decisions made in the wrong environment. A user joins an unfamiliar Wi-Fi network, works from a location they do not fully trust, or delays enabling a setting that would have reduced risk. In those moments, security is not only about what tools are installed. It is about whether the operating system can recognize a riskier situation and guide the user toward a safer response.
That is where many security strategies fall short. Most security tools are designed to encourage better habits, but they do not automatically create them. They can warn, prompt, restrict, and reduce risk, but they cannot fully replace judgment. If users do not take ownership of their role in keeping systems secure, even strong tooling can be undermined by routine behavior.
That is why security awareness training matters. The goal is not to make people paranoid. It is to help them recognize the patterns that attackers rely on most. Phishing emails, fake login prompts, impersonation attempts, and browser-based scams all depend on the same basic weakness: people are busy, distracted, and often rewarded for choosing convenience over caution. Attackers know that, and modern scams are designed to exploit it.
That mindset made sense in an earlier era, when remote support was far more limited than it is today. In many cases, helping someone remotely meant trying to walk them through each click over the phone while mentally mapping the entire operating system and hoping they followed along accurately. It was time-consuming, error-prone, and often frustrating for both sides.
One of the biggest lessons I learned during the merger process was that not every opportunity places value on the same thing. Some conversations were centered almost entirely on me as an operator. In that kind of situation, the business itself is secondary. The clients, systems, and long-term structure of the company carry less weight, and the offer starts looking more like an acquihire than a true business partnership.
That gap created the foundation for the business. Instead of trying to serve everyone, the early focus was on organizations with small in-house IT teams, especially nonprofits and design agencies that depended on Apple-heavy environments. These teams did not necessarily need a full outsourced department. What they needed was dependable backup, additional coverage, and a trusted partner who could step in without creating disruption.
That problem was one of the clearest business opportunities I ever saw because I had lived it firsthand. I spent time working in environments where taking time off was difficult not because the work was unimportant, but because there was no meaningful backup plan. The systems still needed support, the users still needed help, and the organization was often relying too heavily on one person to keep everything moving.
One of the hardest lessons in consulting is that scale does not automatically create efficiency. It often exposes the places where your systems are inconsistent. Different teams may serve clients well on their own, but if they bill differently, document differently, or rely on different tools, even a well-intentioned merger can create confusion faster than it creates leverage. The challenge is not just combining staff. The real work is standardizing the operational habits that shape the client experience every day.
The MacAdmins Foundation exists to support the people and programs that help this community thrive. It helps create access, build opportunities, and strengthen the broader ecosystem that so many Apple administrators rely on every day. For a field that depends heavily on shared knowledge, mentoring, and collaboration, that kind of support has real long-term value.
As I was building the business, one of the most valuable things I did was invest time in getting to know other business owners in the same space. That meant asking questions, learning from people who had been doing the work longer, and building trust without approaching every interaction like a competitive threat. In some cases, it even meant referring business elsewhere to make it clear that the goal was relationship building, not trying to undermine what someone else had spent years creating.
That is where self-reflection becomes one of the most important business skills a consultant can develop. Growth is not only about adding clients or increasing revenue. It is also about recognizing what you do well, what you do poorly, and what you no longer want to own. For some founders, that leads to hiring. For others, it leads to partnerships. In some cases, it leads to a larger realization that the business may benefit from a different structure than the one that got it off the ground.
That is where security conversations become difficult. The threats are real, and downplaying them does not help anyone. Businesses do face serious risk from weak controls, poor habits, and delayed decisions. But there is a difference between honestly communicating risk and relying on fear as the primary way to sell a solution. One approach builds trust. The other often creates pressure without creating commitment.
That tension becomes clear when a business tries to grow into a new service area. Hiring and training from scratch can work, but it takes time, money, and close oversight to reach the standard clients expect. A partnership can sometimes create a faster path. In our case, expanding into cybersecurity meant working with outside specialists who could bring skills we did not already have in-house. That allowed us to build a stronger service offering without pretending to have depth we had not yet developed internally.
That lesson became clear to me as I built a services business around Apple-focused consulting. The original idea behind the company was simple: support organizations that relied heavily on Apple devices but did not have a deep internal IT bench. I had worked in environments where one person carried most of the technical load, and I understood how difficult it was for those teams to find reliable backup. That gap in the market created the opportunity, but the first version of the brand was built faster than it should have...
Jon recalls attending a WWE even with the CCP crew, thanks to Joe’s sister.
Jon takes us through his path of leaving a 9-to-5 job and starting a consultancy to fill a visible void.
