Choosing a ServiceNow Partner

Boutique vs Big 4, partner selection, switching from a Big 4 partner.

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

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.

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

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.

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

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.

How to Build the Business Case to Switch Your ServiceNow Partner Before the Audit Committee

How to Build the Business Case to Switch Your ServiceNow Partner Before the Audit Committee

A CIO at a listed European retailer sent me a two-line email last month. "We know we need to switch ServiceNow partner. The CFO wants a business case. Can you help me build one that survives the audit committee?" That is the question I get most often now. Not "should we switch" but "how do we defend the switch in a boardroom where the incumbent has a fifteen-year relationship with the CEO and the audit chair remembers signing the master services agreement in 2019." The technical case for switching is usually the easy part. Any competent platform owner can list the defects, the slippage and the OOTB literacy gaps. What breaks in the boardroom is the financial narrative. When the current partner is a globally recognised name, the CFO's default position is that a switch introduces risk, not that staying does. Reversing that intuition requires numbers, not adjectives. This piece is the framework I use with clients who need to build the case for a switch that will hold up under adversarial scrutiny from a procurement director, a group auditor and a non-executive with a long memory.

ServiceNow Consulting Services for Mid-Sized Enterprises: The Evaluation Criteria That Actually Matter

ServiceNow Consulting Services for Mid-Sized Enterprises: The Evaluation Criteria That Actually Matter

A CIO of a 1,200-person insurance broker sent me his RFP last week. Twenty-eight pages. Seventeen scoring dimensions. A weighted matrix that would not have looked out of place at a defence procurement office. He wanted an outside opinion before he sent it out to five shortlisted partners. I read it on the train home from Vienna and called him the next morning. I told him the RFP was excellent, thorough, and would almost certainly help him pick the wrong partner. He was quiet for a moment and then asked what I meant. What I meant is that the RFP was optimised for the wrong buyer. It was a scale-down of the RFP a Fortune 100 uses to buy from a Big 4. It scored partners on things that matter when you are running a hundred-million-euro programme with three parallel workstreams and a dedicated PMO. It scored almost none of the things that determine whether a mid-market ServiceNow implementation actually ships on time and gets adopted after go-live. If you sit in the 300 to 3,000 employee band and you are about to send a ServiceNow RFP into the market, the evaluation criteria you use to sort responses will decide the next two years of your platform's life. This is not the same...

When Boutique ServiceNow Consulting Beats a Big 4, and When It Doesn't

When Boutique ServiceNow Consulting Beats a Big 4, and When It Doesn’t

A CIO at a €300M industrial firm rang me last month. He'd just finished a bake-off between two Deloitte practices and one boutique shop, and he wanted a sanity check before signing. The Deloitte proposal came in at €1.4M for a phase-one ITSM and CMDB rollout across three regions. The boutique quote was €480k for the same scope, with fewer bodies but named senior architects on every workstream. His board was pushing him toward Deloitte. His gut said the boutique. He asked me to help him think it through honestly. I don't sell against the Big 4 by default. I've watched boutique shops blow deadlines just as badly as Accenture, and I've watched Deloitte crews save a floundering programme that a specialist SI had already botched. The question "should I hire a big four firm or a specialist SI" doesn't have a universal answer. It has a set of conditions, and the sensible thing is to walk through them before signing anything. There are scenarios where a Big 4 practice is genuinely the right call, and pretending otherwise is dishonest.

How to Switch ServiceNow Partner Mid-Project Without Blowing Up the Roadmap

How to Switch ServiceNow Partner Mid-Project Without Blowing Up the Roadmap

A CTO at a European insurance group called me in April. Their HRSD and ITSM programme with a Big 4 partner was seven months into an eleven-month plan. Two lifecycle events were live. The rest were slipping a sprint every sprint. The named architect had rotated out in February. The replacement had rotated out in March. The programme board had already extended twice. The CTO had made the internal decision to switch servicenow partner three weeks earlier, but nobody in his team knew how to actually do it without the platform going dark in the transition. That is where most of these conversations start. Not with the decision. With the mechanics. The warning signs are the easy part. Every mid-market leader I speak with can list them once they see the pattern. The hard part is the transition itself, because a partner change mid-project has moving parts that a fresh implementation does not. There is a half-finished data model. There is a live production instance carrying real user load. There is an update set graveyard nobody has documented. There is a managed service contract with an exit clause that reads like a hostage note. And there is a business sponsor who wants to know, on one...

Inside Boutique ServiceNow Consulting: The Senior-Only Delivery Model Mid-Market Buyers Are Actually Paying For

Inside Boutique ServiceNow Consulting: The Senior-Only Delivery Model Mid-Market Buyers Are Actually Paying For

A VP of Operations at a 350-person SaaS company asked me a question last week that nobody asks on the first call. He had read enough LinkedIn posts about the Big 4 pyramid to be cautious, and he was ready to choose a smaller firm. What he wanted to know was different. "If I sign with a boutique," he said, "what does day fourteen look like? What does day sixty look like? Tell me what is actually happening inside the engagement, not what the slide says." That is the right question, and it is the one almost nobody answers honestly during a pitch. The boutique versus Big 4 debate has been ground down to slogans. Specialist SI versus pyramid. Senior delivery versus offshore deflection. Fixed-fee versus time-and-materials. All of those things are real, but they are descriptions of the wrapper, not the actual mechanics inside the engagement. If you are a mid-market buyer trying to decide between a global integrator and a smaller specialist, what you want to understand is what happens on a Tuesday afternoon in week three. That is what this post is about.

What Mid-Sized Enterprises Actually Need From ServiceNow Consulting Services

What Mid-Sized Enterprises Actually Need From ServiceNow Consulting Services

An ops director at an 800-person logistics company called me last month. Their executive team had just signed a three-year ServiceNow contract. The implementation partner, a top-tier global SI, had pitched a twelve-month programme with a workstream lead, two architects, four developers, a business analyst, a PMO, and a part-time engagement director. The blended day rate was the kind of number you only say out loud in a small room. Halfway through month three the company had a tidy steering committee, a Jira board the size of a small city, two PowerPoints titled "Future State Vision", and exactly zero working catalog items in production. The director was not angry. He was tired. He said the same thing I hear from every mid-market buyer who has been burned once. "We are not a Fortune 500. We do not need a programme. We need somebody to build the thing." That gap, between what mid-sized enterprises actually need and what large SIs sell them, is the entire reason boutique ServiceNow consulting exists. If you sit in the 200 to 2,000 employee band, with revenue somewhere between fifty million and a billion, and you are looking at servicenow consulting services mid-sized enterprises...

When to Switch ServiceNow Partner: Eight Warning Signs Mid-Market CIOs Ignore Too Long

When to Switch ServiceNow Partner: Eight Warning Signs Mid-Market CIOs Ignore Too Long

A CIO at a 900-person specialty chemicals group rang me at the end of May. Their ITSM and HRSD rollout with a top-tier global SI had been live for fourteen months. The build was technically finished. The managed service contract that followed it was not finished, and it was not working. Tickets to the partner were taking eleven days to acknowledge. The named delivery lead they had been promised was sharing his time across nine accounts. Half the change requests came back with quotes higher than the original implementation rate card. The CIO knew something was wrong and could not put it on a slide for the audit committee. He wanted a calibration call. We spent forty minutes on it. By the end he had the eight signals he needed and a number he could defend. The decision to switch ServiceNow partner is almost never made on time. The signals show up months before the move happens, and most leadership teams sit on them because the alternative feels worse than the status quo. It is not. The cost of staying with a partner who is mis-delivering is larger than the cost of moving, and the gap widens every month. The question is not whether to switch. The question is whether you can see the...