For much of the past decade, building a successful ServiceNow practice, in many respects, followed a familiar formula. Recruit consultants, build implementation capability, collect certifications, and gradually expand into neighbouring workflow areas.
But recent years have seen ServiceNow transform itself from a workflow automation platform into a much broader enterprise technology company. Organic product development has been accompanied by acquisitions including Moveworks, Armis, and Veza, while new capabilities such as AI Control Tower, Otto, and Autonomous Workforce have expanded its ambitions far beyond IT service management.
For customers, there is an opportunity to consolidate more business processes on a single platform. For partners and ServiceNow professionals, however, it presents a different challenge.
How do you build and maintain expertise across a platform that continues to grow in both breadth and complexity? Or, to put another way, has ServiceNow become too big for any one partner to master?
A Platform That’s Outgrown The Traditional Partner Model
Having spent years working across the ServiceNow ecosystem before founding ServiceNow talent marketplace Billfly, Scott Jacocks has watched the platform evolve from a specialist IT workflow tool into something much broader.
“The reality is that no single partner is master of the entirety of the platform,” he said.
“The platform has expanded beyond what any one person – or in many cases any one organization – can realistically hold in their head,” he said. “Five years ago, if you understood ITSM, ITOM, HRSD and CSM, you could credibly say you understood most of ServiceNow. That’s no longer true.”
Today’s platform demands expertise across AI, CRM, security, governance, industry solutions, data, enterprise architecture and an increasingly sophisticated ecosystem of adjacent technologies.
“Specialization is inevitable if you are not a GSI,” said Jacocks, who also argues that even the largest global systems integrators aren’t immune.
“They may have every specialist somewhere in the organization, but they can’t guarantee every specialist is available when a customer needs them.”
Instead, partners are increasingly being forced to make strategic decisions about where they differentiate. Some will become leaders in AI. Others will focus on security, customer workflows or industry expertise. Trying to excel at everything, Jacocks believes, is becoming increasingly unrealistic.
Rather than trying to become experts across the entire platform, consultants should aim for deep expertise in one or two disciplines while maintaining a broader understanding of adjacent technologies.
That challenge is being amplified by AI. Professionals now need to understand not only how AI is embedded within ServiceNow itself through AI Agents and agentic workflows, but also how customers are deploying AI across the wider enterprise.
The result is a much more demanding skills profile than existed a few years ago.
Rethinking What It Means To Be A ServiceNow Partner
While Jacocks believes no single partner can realistically master the entire platform, others argue that doesn’t mean the era of the full-service partner is over.
Prabjoth Saimbhi, global head of alliances, practices and innovation at Cognizant’s ServiceNow Business Group, agrees that the traditional ServiceNow generalist is disappearing.
“When I first started working with ServiceNow, it was just ITSM with a few adjacencies,” he said.
“It has now expanded to include AI, security, CRM, industry solutions and autonomous workflows. This means it’s impossible for a single architect to have a genuine full understanding of the whole platform in their head.”
The answer, however, isn’t to fragment delivery across multiple suppliers. Instead, Saimbhi believes partners need to rethink how expertise is organized.
“The skill isn’t knowing everything anymore. It’s knowing how to assemble the right depth, fast.”
That has led the company to move towards a domain-led operating model, building specialist teams around customer outcomes rather than individual ServiceNow products.
Instead of expecting one consultant or even one practice to understand every capability, Cognizant assembles expertise from across AI, security, data, business transformation and platform engineering according to the requirements of each engagement.
“The generalist individual… is over. But breadth of coverage and depth of expertise are different claims,” said Saimbhi.
Customers, he argues, still want a single organization accountable for delivery.
“Customers still want one accountable partner. They don’t want to manage a dozen vendors and carry the integration risk themselves.
“The delivery behind that accountability is increasingly a network. No large partner is the best in the world at every niche, and pretending otherwise doesn’t serve the customer.
“Our job is to be that orchestrator, and to be secure enough in our own value that we’re not threatened by pulling in someone who’s better at one thing than we are.”
The challenge is not necessarily that partners have become too small. Rather, they need to become much better at assembling specialist expertise while maintaining accountability for customer outcomes.
ServiceNow ‘Looks Different’ Today
ServiceNow itself acknowledges that its own evolution is forcing partners to think differently about how they organize their businesses.
According to Adam Spearing, enterprise advisory lead at ServiceNow UKI, many partners are still structured around a traditional ServiceNow Centre of Excellence – an approach that made sense when the platform was largely focused on IT workflows such as ITSM, HR Service Delivery and IT Operations Management.
The problem, he argues, is that today’s ServiceNow looks very different. Capabilities such as AI Control Tower, Otto, Moveworks, Armis, and Veza don’t naturally fit within that traditional organizational model. They introduce new buying centres, new stakeholders and entirely different conversations around AI governance, enterprise security, identity management, and business transformation.
Rather than adding more consultants to an existing ServiceNow practice, Spearing believes partners need to think much more broadly about where these capabilities belong.
An AI specialist working on AI Control Tower, for example, may sit more naturally within an enterprise AI consulting practice than a traditional ServiceNow team. Likewise, expertise around identity governance or cyber resilience may be better aligned with wider security practices than platform implementation teams.
In essence, ServiceNow’s own expansion is changing not only what partners deliver, but how they organize themselves.
“What made those partners successful doing implementations is going to change,” he said.
That doesn’t mean implementation becomes irrelevant. Rather, Spearing believes AI will increasingly compress the effort required for routine platform delivery, allowing partners to concentrate on higher-value work.
Instead of differentiating themselves through the speed or scale of implementation, partners will increasingly create value through architecture, governance, operating model design, AI readiness, and helping organizations redesign how work itself is performed.
Final Thoughts
The ServiceNow platform has evolved faster than the traditional ServiceNow partner model. But that doesn’t mean the traditional partner is disappearing.
However, it does mean the assumptions are being challenged. As the platform continues to expand through AI, security and autonomous workflows, competitive advantage is likely to depend less on trying to know everything and more on knowing how to combine the right expertise at the right time.
As Saimbhi put it: “The skill isn’t knowing everything anymore. It’s knowing how to assemble the right depth, fast.”