From Customer to Partner: Six Months of Growth, Learning, and New Perspectives
For five years, I built my ServiceNow career on the customer side. I knew the organization, the people, the processes, and the platform footprint inside and out. I had opportunities to solve complex problems and make a meaningful impact. It was a role I genuinely enjoyed.
When I decided to move to a ServiceNow partner last December, it wasn't because I was unhappy. Quite the opposite. I truly enjoyed my previous role and the team I worked with. I learned an incredible amount during those five years, worked alongside talented colleagues, and was supported throughout my career journey. This is not a story about leaving a bad situation. It's a story about finding a different kind of growth.
What drove me was curiosity. After five years in a single environment, I had a growing sense that there was a whole world of the platform I hadn't touched. Different industries, different use cases, different product suites. I wanted to know what I didn't know. That feeling, more than anything else, is what led me to make the leap.
Six months later, I can confidently say it has been one of the most rewarding professional decisions I've made. But it's not the right move for everyone, and I don't think it needs to be. Both paths have real, distinct value. What matters is knowing which one fits where you are in your career and what you're looking for right now.
Here are some of the biggest differences I've experienced, the good and the challenging.
My World Got Much Bigger
One of the realities of working for a customer is that your exposure to ServiceNow is naturally limited by your organization's needs. Even large organizations typically use only a fraction of what the platform can do. You become an expert in your company's implementation, but there are entire areas of the platform you may never touch.
Working for a partner changed that almost immediately. Instead of focusing on a single environment and roadmap, I'm now exposed to different industries, different use cases, different implementation approaches, and entirely different product suites. Every customer engagement brings something new to learn.
One experience that stands out happened just a couple of months after I joined my current organization. I was asked to demo Legal Service Delivery to a client. The catch? I had never worked with the product before.
Suddenly, I needed to learn the application well enough to confidently explain it, answer questions, and demonstrate its value. A few years ago, that prospect might have terrified me. Instead, it became one of the most rewarding learning experiences I've had. It pushed me outside my comfort zone and reminded me how much growth can happen when you're given the opportunity to stretch.
That said, I won't pretend that breadth comes without a tradeoff. On the customer side, there's something genuinely valuable about going deep. You build relationships over years, not weeks. You see the long-term impact of your work. You understand the organization well enough to anticipate problems before they happen. That kind of deep institutional knowledge is its own form of expertise, and it's one I sometimes miss.
Learning Became Part of the Job
One thing that surprised me was how much emphasis a partner places on continuous learning.
Of course, learning existed on the customer side too. In fact, I was consistently encouraged to pursue certifications and professional development. The challenge was never a lack of support. The challenge was finding the time.
Like many in-house platform teams, we were balancing projects, support work, operational responsibilities, and a seemingly endless list of priorities. Learning often became something I planned to do "when things slowed down." The problem was that things rarely slowed down.
At my current organization, time for learning is treated as an important part of the job rather than something that happens after the job is done. Since joining in December, I've earned two CIS certifications, something I had wanted to pursue for quite some time. More importantly, I've been encouraged to keep exploring new areas of the platform rather than staying within the boundaries of what I already know.
I do want to name something honestly here: the customer side's version of this challenge is real, but it's not unique to customers. Many partner organizations face the same pressure. What I've found at my specific organization may not reflect partner life universally. If continuous learning is important to you, it's worth asking about directly in any interview, on either side of the table.
My Coworkers Are an Incredible Resource
One of the biggest advantages of joining a boutique partner has been gaining access to an entire team of specialists. No matter how much experience you have, there will always be someone who knows more about a particular product, implementation approach, integration pattern, or business process. At a partner organization, those people are often just a few messages away.
I've found myself surrounded by architects, consultants, developers, and platform experts with deep experience across a wide range of ServiceNow products. The willingness of people to share knowledge and help each other succeed has been one of the most valuable parts of this transition. It's hard to overstate how much faster you can grow when you're learning from people who have already solved dozens of challenges you've never encountered before.
That said, strong teams exist on the customer side too. Some of the most talented people I've worked with in my career were colleagues at my previous organization. The difference isn't that one side has better people. It's that partner teams tend to have broader experience. Whether that's what you need depends on where you want to grow.
Learning to See Myself as the Expert
One adjustment I wasn't fully prepared for was the shift in perspective. As a customer, you're often collaborating with consultants and partners who are brought in because they're seen as the experts. As a partner, suddenly you're the one sitting in that seat. Customers are looking to you for guidance. They want recommendations, best practices, and confidence that they're moving in the right direction. At first, that felt intimidating.
If I'm being honest, I think many women will relate to this. We often spend so much time focusing on what we still need to learn that we overlook everything we already know. We wait until we feel completely ready before stepping into positions of greater visibility or authority. The reality is that complete readiness is often a myth.
“If I’m being honest, I think many women will relate to this. We often spend so much time focusing on what we still need to learn that we overlook everything we already know.”
This transition forced me to recognize that the experience I'd gained over five years on the customer side was genuinely valuable. It gave me insights that customers needed, perspectives that consultants who had never worked in-house might not have. Over time, I stopped asking myself whether I was qualified to be the expert and started focusing on how I could best help the people relying on my guidance.
That shift in mindset has been one of the most meaningful parts of this journey. But I also want to say: that shift can happen on the customer side too. Leading a platform team, owning a roadmap, driving enterprise-wide change, these are not small things. The opportunity to see yourself as an expert doesn't require changing jobs. Sometimes it just requires changing your perspective on the role you're already in.
The Boutique Partner Advantage
One of the most rewarding aspects of joining a boutique partner has been the opportunity to participate in the full lifecycle of a project. At many organizations, roles are highly specialized. A business analyst gathers requirements. A consultant designs the solution. A developer builds it. A project manager oversees delivery. There's nothing wrong with that model, and it works well for many teams. But it can also mean that your view of a project is limited to the piece you own.
At my current organization, I've had opportunities to engage directly with customers, gather requirements, refine backlogs, help shape solutions, and then build those solutions myself. In some cases, I've even begun leading projects from start to finish. That end-to-end experience has been incredibly rewarding. It's helped me develop skills that extend far beyond development and given me a much deeper understanding of how successful projects actually come together.
I also recognize that this opportunity reflects the kind of organization I joined. Being part of a boutique partner has created space for me to take on responsibilities that might be more segmented at a larger consulting firm.
The result is that I'm not just becoming a stronger developer. I'm becoming a stronger consultant, communicator, problem solver, and leader.
The Challenges Are Real, Too
No career move is perfect, and I'd be doing a disservice to anyone considering this path if I glossed over the harder parts.
The biggest adjustment for me has been the focus on billable hours. As a customer, I never had to think about utilization. I was focused on delivering value to my organization, not tracking how my time aligned to billable work. In consulting, utilization matters. It's part of the business model, and learning to think about work through that lens has been a genuine adjustment.
There's also a natural rhythm to consulting that took some getting used to. Some weeks are incredibly busy. You're juggling multiple priorities, customer meetings, deliverables, and deadlines. Other times, projects slow down or you're between engagements. Logically, you know these cycles are normal, but it can still feel unsettling when you've spent years in an environment where there was always another ticket, project, or backlog item waiting.
That stability is one of the things the customer side genuinely offers, and it's not a small thing. Knowing your organization, your stakeholders, your platform, and your roadmap provides a kind of grounding that consulting doesn't always replicate. If stability and long-term relationships are important to you, that's a real and legitimate reason to stay on the customer side. Not a safe choice. The right choice.
I've had to learn that professional value isn't measured solely by whether every hour is billable. That has been an important mindset shift.
Building on What Came Before
Looking back, I don't see my move as leaving one good opportunity for a better one. I see it as moving from one stage of my career to another.
My years on the customer side gave me the foundation I rely on every day. They taught me how organizations actually use the platform, what challenges administrators and developers face, and what success looks like from the customer's perspective. Those experiences have made me a stronger consultant.
Ironically, one of the things that customers seem to value most is that I've sat in their seat. I understand the competing priorities, resource constraints, internal politics, and day-to-day realities they face because I lived them myself. The lessons I learned in those five years didn't become less valuable when I joined a partner. If anything, they became even more valuable.
Why It Was the Right Move for Me
When I reflect on the past six months, the word that comes to mind is growth. I've broadened my technical knowledge, earned certifications, learned from experts, and gained exposure to new products, industries, and challenges. I've also developed more confidence in my own expertise, which might be the most meaningful change of all.
Most importantly, I've been able to do all of that while working for an organization that genuinely supports its people and invests in their success. That matters enormously, and I don't take it for granted.
But I want to end with something I mean genuinely, not just as a disclaimer. If you're on the customer side and you love what you do, that's not something to second-guess. Deep platform ownership, long-term stakeholder relationships, the satisfaction of watching something you built become part of how an organization works every day, those things have real value. A career built on that foundation is not a lesser path.
For anyone curious about making a similar transition, my advice isn't that you should make the leap. It's that you should be honest with yourself about what you're actually looking for. Especially for women, it can be easy to stay where we feel comfortable and proven. But it can be equally easy to chase change for its own sake. The question worth sitting with isn't "should I move to a partner?" It's "what kind of growth do I want right now, and where am I most likely to find it?"
“The question worth sitting with isn’t “should I move to a partner?” It’s “what kind of growth do I want right now, and where am I most likely to find it?””
We often underestimate the value of our experience because we're focused on what we have yet to learn. Sometimes it takes a new environment to show us just how much we already bring to the table. But sometimes it takes staying put and going deeper to discover the same thing.
Either way, figuring out which path is right for you is worth the reflection. If you're considering a change and want to think it through with someone who's been there recently, feel free to drop me a DM. I'm always happy to chat.
