Choosing a ServiceNow Partner

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

Boutique ServiceNow Consulting: Five Tests Before You Sign the SOW

Boutique ServiceNow Consulting: Five Tests Before You Sign the SOW

A head of IT at a 600-person logistics company sent me a partner shortlist last month. Three names on it. One was a global SI everyone in his industry uses. The other two were positioned as boutique ServiceNow consulting firms, both around forty people, both with the standard set of badges on the website. He had asked all three for a scoping call and walked away from those calls more confused than when he started. Every firm said the same things. Every firm had the same case studies on rotation. Every firm claimed they would "act as a true partner, not a vendor." He wanted to know how to tell which one would actually deliver. This is the question that has replaced "do we need ServiceNow." Mid-market buyers have figured out that the Big 4 model breaks badly at their scale. They have read the LinkedIn posts about rotating consultants and offshore deflection. They are now looking for an alternative. The problem is that "boutique" has become a marketing label, not a structural reality. Plenty of small firms operate the Big 4 playbook in a smaller wrapper. Picking the wrong one costs you the same money and the same time.

ServiceNow Consulting Services for Mid-Sized Enterprises: What Actually Works at 300 to 2,000 Seats

ServiceNow Consulting Services for Mid-Sized Enterprises: What Actually Works at 300 to 2,000 Seats

The CIO of a 700-person logistics company in Antwerp called me on a Monday in March. She had a signed proposal from a Big 4 partner sitting on her desk, two years of work priced at €1.4 million, and a queasy feeling that something was off. Her IT director had pushed for it. The board wanted ServiceNow. The procurement team wanted a "safe" name on the contract. But the proposal had 64 pages, eight workstreams, twelve named roles, and not a single hour of work that was going to happen before month four. She wanted to know if she was about to make a mistake. She was. Not because the Big 4 firm was incompetent. Because the proposal was built for a company three times her size. That is the trap mid-sized enterprises walk into over and over when they go looking for ServiceNow consulting services for mid-sized enterprises and end up shopping at firms whose entire delivery model assumes a 5,000-seat customer with a global PMO. The mid-market sits in an awkward zone. You are big enough that the platform genuinely solves problems for you. Ticket volumes are real. HR cases are real. Asset sprawl is real. Audit pressure is real. You are not big enough to absorb a six-figure project...

How to Switch ServiceNow Partner Mid-Project Without Burning the Build

How to Switch ServiceNow Partner Mid-Project Without Burning the Build

A platform owner at a German logistics group called me on a Monday morning in March. Their ITSM go-live had slipped from January to April, then April to June. The Big 4 partner running the build had cycled through four lead consultants in seven months. The latest one had been on the platform for nine days. The steering committee had a board update on the Thursday and the CIO wanted to know whether they should walk. That conversation is more common than people admit. The decision to switch ServiceNow partner mid-project gets framed as nuclear, and most CIOs delay it for one or two quarters longer than they should. The cost of the delay is almost always larger than the cost of the switch. The trick is doing the switch without setting fire to the work that already exists, and without paying for the same scope twice. The pattern is consistent. A Big 4 or top-tier SI wins the bid on the strength of brand, references, and a named partner who shows up to the pitch. The build starts and the named partner disappears within four weeks. The actual delivery team is junior, often offshore, often rotating. The platform architect role is staffed at 0.3 FTE by someone covering three other...

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

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

A finance director at a 400-person manufacturer called me on a Thursday afternoon in February. They were eleven months into a ServiceNow ITSM and HRSD program with one of the Big 4. The original promise was nine months. The original budget was 1.4 million euros. They were now at 1.9 million, and the partner had just submitted a change request for another 380,000 to "stabilise the ITSM go-live." The actual platform? Half of HRSD was not built. The CMDB was a graveyard of duplicate CIs. Three of the original five named consultants had rotated off to a bigger account in Q4. The two who remained were a junior who had finished his ServiceNow Fundamentals two months earlier and a manager who came on calls but did not touch the platform. She was not angry. She was tired. She wanted to know if her board was going to look stupid for picking the safe name on the slipsheet. This is the conversation I have most often now. Not "should we use ServiceNow." That decision is usually two years old by the time we talk. The question that comes up again and again is whether a boutique ServiceNow consulting partner is genuinely a better fit for a mid-market company than one of the global integrators....