Choosing a ServiceNow Partner

Sep 29, 2026 Choosing a ServiceNow Partner

When to Switch Your ServiceNow Partner Mid-Project (and How to Do It Without Torching the Program)

A programme director at a European insurer rang me in July. Their ITSM rollout was eight months in, twelve weeks behind schedule, and the third change request had just landed on her desk. The partner was one of the big four. The engagement partner had rotated twice. The named architect on the SOW had never appeared on a working call. The offshore build team was three developers who all seemed to be learning ServiceNow on her budget. She asked me one question. "Is it too late to switch?" It was not. It rarely is. But the answer to the second question, the one nobody at her firm was asking yet, mattered more. How do you switch a ServiceNow partner mid-project without losing the eight months of work you already paid for?

Sep 19, 2026 Choosing a ServiceNow Partner

ServiceNow Consulting Services for Mid-Sized Enterprises: What Actually Works Between 200 and 2,000 Employees

A COO at an 800-person specialty chemicals company rang me last month. Her IT director had spent six weeks on a Big 4 scoping exercise and come back with a €1.4M number, a nineteen-month plan, and an org chart showing four consultants on the account she had never met. She wanted to know if that was the price of entry for ServiceNow, or whether she was being priced like a Fortune 500. She was being priced like a Fortune 500. This is the pattern I see almost every week. Mid-market companies, roughly 200 to 2,000 employees, get quoted implementation programs designed for organisations five or ten times their size. The methodology is the same. The team structure is the same. The overhead is the same. What the client actually needs is different, and nobody bothers to redesign the delivery model around that fact. Then the CFO gets sticker shock, the project gets shelved, and the mid-market keeps running on a mix of Jira Service Management, spreadsheets, and shared inboxes for another eighteen months.

Sep 1, 2026 Choosing a ServiceNow Partner

ServiceNow Consulting Services for Mid-Sized Enterprises Is Not the Enterprise Build Shrunk Down

An IT director at a 650-person industrial equipment maker sent me a scoping document last month. Forty-two pages. Written by a Big 4 partner she was evaluating. It proposed an eight-month ITSM implementation with a fifteen-person delivery team, a three-tier governance model with a steering committee that met fortnightly, a full CMDB build using Common Service Data Model 5, a Service Portfolio Management module she had never asked for, and a change advisory board structure copied verbatim from the same firm's engagement with a European bank. She asked me one question. "Does this look right for a company our size?" It did not. The document was a Fortune 500 implementation plan with the client name changed. Every mid-market company that has bought servicenow consulting services for mid-sized enterprises from a large SI has seen a version of this document. The plan is not wrong because it is bad. It is wrong because it is not built for a mid-sized enterprise. It is built for a large one, scaled down badly, and priced to keep a fifteen-person team busy.

Aug 31, 2026 Choosing a ServiceNow Partner

Why Boutique ServiceNow Consulting Beats a Big 4 on Mid-Market Work

A finance director at a 900-person specialty chemicals company rang me on a Wednesday afternoon last month. He had just signed a Statement of Work with a tier-one global SI for what should have been a straightforward ITSM plus HRSD build. The number on the SoW was €1.4 million for a fifteen-month program. He wasn't calling to celebrate. He was calling because he had spent the previous evening reading through the resource plan and noticed that of the eleven people billed against the project, only two had ServiceNow certifications, and none of them were the two people who had presented in the sales cycle. He wanted a second opinion before the kickoff meeting the following Monday. I've had a version of that call maybe fifteen times in the last three years. The pattern is so consistent it has stopped being surprising. A mid-market company (say 300 to 2,500 employees, one instance, no offshore captive, budget of €300k to €1.5m for the initial build) buys ServiceNow. They put the implementation out to tender. The Big 4 or a tier-one global SI wins because their name is on the shortlist and the procurement team feels safer signing with someone they've heard of. Six to nine months in,...

Aug 27, 2026 Choosing a ServiceNow Partner

How to Switch ServiceNow Partner Without Breaking the Instance You Already Paid For

An IT director at a mid-cap logistics group called me on a Monday. His board had already signed off on ending the managed-services contract with a Big 4 firm. The rate card was eye-watering, the tickets were closed with three-word resolution notes, and the last upgrade had left three custom applications sitting in a broken half-migrated state. His question was not "should we switch". That was decided. His question was the one every buyer at this point in the story asks: "how do we do this without the wheels coming off the platform for six months". That is the real problem when you switch ServiceNow partner. Everyone talks about the commercial exit, the notice period, the transition clause. Almost nobody talks about the two things that actually determine whether the change goes well or turns into an eighteen-month regret. Those two things are the state of the instance you are inheriting from yourself, and the handover the outgoing partner is contractually obliged to do but rarely does properly.

Aug 16, 2026 Choosing a ServiceNow Partner

The Three Moments a Mid-Sized Enterprise Should Call for ServiceNow Consulting Services (and the One Moment They Usually Do)

A CIO at a 900-person specialty chemicals group phoned me on a Tuesday in June. His voice had that specific flatness you hear from people who have been in meetings since seven in the morning. The ServiceNow platform his team had been building for eleven months was going live in three weeks, and he had just been told by his own implementation partner that the CMDB was not going to be ready for wave two. Not "delayed by a sprint" not ready. Not populated, not governed, not integrated with the discovery tool they had already paid for. He wanted to know whether it was worth pausing the go-live or pushing through. I asked him when he had first suspected the CMDB was in trouble. He said month four. I asked why he had not called anyone in month four. He said he thought his internal team could handle it, and by the time he was sure they could not, it felt too late to bring anyone else in. That is the pattern. Mid-sized enterprises call for outside ServiceNow consulting services when they are already on fire, and the fire is usually something that started five months earlier as a small design decision nobody caught. If you are a CIO or a platform owner at a mid-market company running...

Aug 12, 2026 Choosing a ServiceNow Partner

Boutique ServiceNow Consulting: The Buyer’s Diligence Checklist That Separates the Real Shops From the Rebrands

An IT director at a Benelux logistics group phoned me last month with a question that has become uncomfortably common. She had shortlisted three small ServiceNow consultancies for a HRSD build after a bad experience with a Big 4 firm. Two of the three had polished decks, similar day rates, and near-identical LinkedIn profiles. She could not tell which of them would actually deliver, and which was two ex-Accenture managers with a Squarespace site and a subcontractor pool in Poland. She wanted a diligence framework she could run in a week that would give her a defensible answer. That question deserves a proper answer, because the market has quietly filled up with boutique ServiceNow consulting firms that look identical from the outside and diverge sharply the moment you scratch the surface. The good ones are the best value in the ecosystem. The bad ones are worse than the Big 4 they claim to replace, because they combine boutique pricing risk with none of the boutique operational depth. This post is the checklist I have watched work, refined over roughly forty introductory calls in the last year.

Aug 10, 2026 Choosing a ServiceNow Partner

The First Ninety Days After You Switch Your ServiceNow Partner Mid-Project

A programme director at a mid-cap European insurer called me at eight on a Sunday evening. Her Big 4 partner had just filed a fourth timeline slip on a fifteen-month HRSD and ITSM programme that was now approaching twenty-two months. The steering committee had voted on Friday to switch. Her question was not whether the decision was right. It was, "What do I actually do on Monday morning." That is the conversation nobody in the sales cycle prepares you for. Everyone tells you how to build the business case to switch ServiceNow partner. Almost nobody tells you what the first ninety days after the switch actually look like, or how you avoid trading one broken programme for another one. Firing the incumbent is the easy part. The next thirteen weeks decide whether the switch was worth the fight. This post is the playbook I hand to clients in the first two weeks after they make the call. It is not a marketing framework. It is what has to happen, in what order, so the platform is stable, the client team is back in control, and the new partner can actually deliver against a plan that survives contact with the instance.

Aug 2, 2026 Choosing a ServiceNow Partner

ServiceNow Consulting Services for Mid-Sized Enterprises: What Year One After Go-Live Actually Looks Like

A COO at a 900-person medtech firm called me in early July. Their ServiceNow ITSM rollout had gone live in February. The partner shook hands, delivered the last training webinar, and demobilised the team. By June the platform owner had two hundred open change requests in her personal backlog, an incident queue that nobody trusted, and a steering committee that had stopped meeting because there was nothing left to steer. On paper the implementation was a success. In practice she was six months into what she now recognised was the real project, and she had no partner in the room to help her run it. That gap is the single most damaging feature of how ServiceNow consulting services for mid-sized enterprises are usually sold and delivered. The industry contracts, prices, and pitches around the implementation. It leaves the twelve months after go-live to be figured out later. In the enterprise segment that gap is filled by a large managed services contract with the same firm that built the platform. In the mid-market it usually gets filled by silence, and the silence has a cost.

Jul 30, 2026 Choosing a ServiceNow Partner

Boutique ServiceNow Consulting: What a Big 4 Contract Structurally Can’t Give You

A CIO at a €900m distribution business called me two weeks ago, three months before her Big 4 managed services contract came up for renewal. She was not angry. She was tired. Her team had lived through eighteen months of a ServiceNow rollout under a top-tier firm and the platform worked. Tickets flowed. Reports ran. The board was mostly satisfied. What she wanted to understand was why every meaningful decision felt slower than it should, and why the people she saw at kickoff had all rotated off the account by month four. I have had a version of this conversation four times this year. The pattern is consistent enough that it stopped being a coincidence and became a structural observation about how large firms sell ServiceNow work, and what that structure prevents them from delivering. The point of this post is not to argue that a Big 4 firm can never do good ServiceNow work. Plenty of them do. It is to be honest about the trade-offs baked into the Big 4 delivery model on the ServiceNow platform, and about the specific situations where a boutique ServiceNow consulting partner is not just cheaper but structurally better.