When you run a consultancy, you think the job is about your expertise—the thing you’ve been hired to do. But very quickly, you realize the role demands a whole set of skills you never set out to master. They sneak in over time, and before you know it, you’ve become fluent in things you once thought you’d avoid. The funny part is, you don’t even notice you’re learning them until you look back and recognize how much your approach has shifted. These are the skills that never appear on your business card, yet they’re the ones that make the whole thing work. And here’s the tricky part: some of them serve you well no matter where you go, while others only really shine in the unique dynamic of consulting.
Take sales. Most consultants, myself included, would say, “I’m not a sales person.” It doesn’t feel like selling, and yet somehow the client roster grows, the referrals come in, and the proposals keep getting accepted. That’s because real sales in consulting isn’t about closing deals or polishing a pitch deck—it’s about listening. Truly listening. It’s about hearing what a client is trying to say even when the words don’t match the need, and offering them something that makes sense for their reality. HubSpot calls this consultative selling, but I think that label undersells what’s actually happening. You’re not selling in the conventional sense—you’re building trust. That skill translates beautifully into any environment. Even in a corporate role, the ability to listen, reframe, and align with stakeholders makes you invaluable. The nuance, though, is that in consulting you always get to close the loop—you either win the client or you don’t. In an employee role, you may find yourself listening just as carefully, but with less control over outcomes. The skill still matters, but the payoff looks different.
Expectation management is another hidden craft you pick up along the way. Early in my consulting career, I prided myself on delivering exactly what was asked, only to realize that’s rarely what was meant. A client might say, “make this faster,” but what they’re really struggling with is a workflow bottleneck or a misaligned process. You learn to translate vague requests into concrete outcomes and set expectations so there aren’t surprises at the end. This shift—from taking requests literally to shaping them thoughtfully—changes the dynamic. Harvard Business Review highlights the importance of clarity in managing complex projects, and consulting forces you into that discipline whether you want it or not. In corporate roles, expectation management is just as crucial, but the nuance lies in power dynamics. As a consultant, you get to renegotiate scope and reset deliverables with some leverage—you’re a hired expert. As an employee, saying “that’s not feasible with current resources” can be riskier, and it requires political navigation. The skill still applies, but it’s often softened by organizational culture.
And then there’s conflict and boundaries. Nobody warns you that running a consultancy is just as much about managing people as it is about managing projects. Clients will push, scope will creep, and sooner or later you find yourself in a conversation where you have to say no. And not a casual no, but a no that preserves the relationship, protects your time, and keeps the project viable. That’s not easy. In fact, it’s one of the hardest things to do well. I learned quickly that being “the fixer”—the one who stretches endlessly to make it all work—eventually burns you out and erodes trust. Setting boundaries became second nature. But here’s the nuance again: saying no to a client is often easier than saying no to a boss. With clients, the relationship is contractual—you can fall back on scope, agreements, or budgets. With a boss, especially in a large organization, boundaries are blurred by hierarchy and career considerations. That means one of the most valuable consulting skills doesn’t always transfer cleanly. You might find yourself more confident about boundaries than your peers, but also more frustrated when you can’t enforce them in the same way.
This tension—skills that both empower and frustrate—is what makes the consulting experience so unique. Running your own shop changes you. It makes you part sales, part translator, part diplomat. It forces you to become more adaptable, more aware, and more intentional about how you interact with people. And when you return to an employee role, those same skills don’t disappear. They just adapt. Some, like active listening and expectation management, are universal assets. Others, like the ability to draw hard boundaries, have to be tempered or reinterpreted in the context of organizational life. Neither is better or worse—it’s just different.
That’s the hidden curriculum of consulting. You sign up to do the technical work, but what you really walk away with is a set of invisible competencies that shape how you operate in any role. They’re what allow you to scale without burning out, to move from one-off gigs into long-term partnerships, and to see problems from a perspective most employees never get. They may not always transfer neatly back into corporate life, but they leave you changed nonetheless. And maybe that’s the point. Consulting doesn’t just sharpen your craft—it reshapes how you see work altogether.
Ready to take your Apple IT skills and consulting career to the next level?
I’m opening up free mentorship slots to help you navigate certifications, real-world challenges, and starting your own independent consulting business.
Let’s connect and grow together — Sign up here
AI Usage Transparency Report
AI Era · Written during widespread use of AI tools
AI Signal Composition
Score: 0.04 · Low AI Influence
Summary
When you run a consultancy, you think the job is about your expertise—the thing you’ve been hired to do. But very quickly, you realize the role demands a whole set of skills you never set out to master. They sneak in over time, and before you know it, you’ve become fluent in things you once thought you’d avoid. The funny part is, you don’t even notice you’re learning them until you look back and recognize how much your approach has shifted. These are the skills that never appear on your business card, yet they’re the ones that make the whole thing work. And here’s the tricky part: some of them serve you well no matter where you go, while others only really shine in the unique dynamic of consulting.
Related Posts
Setting up Ollama on macOS
Recently, after some bad experiences with OpenAI's ChatGPT and CODEX, I decided to look into and learn more about running local AI models. On its face it was intimidating, but I had seen a lot of people in the MacAdmins community posting examples of macOS setups, which really helped lower the bar for me both in terms of approachability and just making me more aware of the local AI community that exists out there today.
AI Agent Constraints and Security
I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.
ABM Warranty 0.4.1
The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.
Vibe Coding with Codex: From Fun to Frustration
So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...
The warranty dashboard Apple doesn’t provide… yet
Download ABM Warranty
Why Apple Fleet Risk Isn’t a Security Problem—Until It Is
Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.
ABM Warranty 0.3.1
The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.
ABM Warranty 0.2.0
ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.
Running a Beta Program: Lessons Learned
Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.
The Day I Unmanaged a Mac Into a Corner
There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.