Blog

It is 03:11 on a Tuesday and a payroll controller in Vienna is on the bridge call. Net pay for a thousand employees did not post. The ServiceNow major incident is open, severity 1, and the integration team is already pulling logs from three different systems. The ServiceNow ticket says SAP HR returned a 500. The SAP basis team says the iDoc never arrived. The SuccessFactors admin says the delta export ran clean at midnight. Forty minutes in, somebody finally notices that the integration user account on the ServiceNow side rotated its credential at 02:00 and nobody updated the Concur and SAP mid-server connections. Resolution time, end to end, is over four hours. The actual fix took eleven minutes. That is the gap between mean time to detect and mean time to resolve, and it is almost never a tooling problem. It is an integration design problem. Most mid-market ServiceNow customers I work with already have a respectable ITSM practice. They have priority matrices, they have a CAB, they have a problem management process that someone actually runs. What they do not have is integration architecture that helps the on-call engineer figure out what broke in less than half an hour. Their…

A head of IT operations at a European retailer called me on a Saturday night last quarter. Their checkout flow had been intermittent for ninety minutes, the store was three days from a public earnings update, and the war-room bridge had eighteen people on it. Six of them were vendors. Two were lawyers. Nobody was running the call. The incident commander had been pulled into a separate executive bridge to brief the CFO and had not returned. The bridge had drifted into a roundtable of vendors describing what their own monitoring did and did not show. The retailer’s ServiceNow major incident management process had a beautiful page in the runbook describing the bridge etiquette. None of it was happening. This is the part of ServiceNow major incident management that nobody puts in the demo. The platform handles the workflow plumbing well. It opens the major incident record, it pages the commander, it sets the comms cadence, it logs the timeline. What it cannot do, and what nine in ten implementations get wrong, is the operating model around the workflow. The war room is a human process running on top of a technical record. If the human process is not designed, the technical record…

A procurement lead at a German logistics company forwarded me three SOWs last week and asked which one to sign. The scopes were almost identical. ITSM, a light HRSD wave, around 800 employees, two integrations. The timelines were five months, seven months, and eleven months. The pricing roughly tracked the timeline, which is what made him nervous. He wanted to know whether the five-month vendor was a hero or a liar, and he wanted to know it before he committed his name to the contract. The honest answer is that you cannot tell from the SOW. You can only tell by pressure-testing the plan the vendor will not put on the slide. There are five questions that separate a vendor who has actually delivered a ServiceNow implementation timeline in your size segment from one who is selling you a number that exists only in a sales spreadsheet. None of them are about the platform. All of them are about the parts of the project the vendor would prefer you did not look at too closely. Every mid-market ServiceNow proposal arrives with a Gantt chart. The Gantt chart shows phases stacked on top of each other in a tidy waterfall. Discovery, design, build, test, deploy, hypercare. The phases have…

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.

A CIO at a European insurer called me last month with a problem that is becoming familiar. They had switched on Now Assist for ITSM eight months earlier, paid for the SKU, sat through the keynote demos, and asked their service desk leads to “use the AI.” The dashboard told them adoption was high. The MTTR numbers had barely moved. Customer satisfaction was flat. Two of the agents were quietly turning the summarisation feature off because it kept hallucinating the wrong impacted CIs into resolution notes. The CIO did not want a vendor pitch. He wanted to know which Now Assist features actually pay for themselves on a real instance, and which ones the platform team should leave alone until the next release. That conversation is the post. Most ServiceNow customers I work with treat Now Assist the way they treated Predictive Intelligence in 2019. They flip the toggles, run a demo for the steering committee, and assume that because the model produces output, the output is valuable. It is the same mistake people made with chatbots in 2017. The output looks confident. The screenshots are great. Whether anyone is actually faster or more accurate is a separate question, and almost nobody…

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…

Last quarter I sat in a budget review with a CIO and his CFO at a mid-market industrial group. The CIO had built a thirty-slide ServiceNow business case. Process automation, self-service portal, AI triage, modern UX, vendor consolidation. The CFO listened for about four minutes, then put down his pen. “Tell me which of these numbers gets smaller next year and by how much.” The CIO did not have an answer. He had benefits. He did not have a number the finance function could put into a forecast and defend at audit. The deal stalled for six months. When it eventually got signed it was for a third of the original scope. That CFO is not unusual. He is the modal CFO in mid-market Europe right now, and he is the person who actually decides whether ServiceNow gets bought.

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…

A finance director at a 600-person logistics company sent me three proposals last month and asked which one was the real number. The Big 4 firm had quoted €840,000 for an ITSM and HRSD build. A regional partner had quoted €420,000. A boutique had come in at €260,000. All three SOWs described, on paper, more or less the same scope. He wanted to know whether he was looking at three different qualities of work or three different ways of pricing the same work. The honest answer is that he was looking at one piece of work priced through three completely different commercial models. ServiceNow consulting costs are not opaque because the market is dishonest. They are opaque because nobody in the buying process is comparing like with like. Once you understand what each model is actually charging for, the right number for a mid-market implementation falls into a much narrower range than the proposals would suggest. This is the conversation finance directors deserve to have before they sign, not three months in when the change orders start arriving.

A finance director at a 600-person logistics company sent me three proposals last month and asked which one was the real number. The Big 4 firm had quoted €840,000 for an ITSM and HRSD build. A regional partner had quoted €420,000. A boutique had come in at €260,000. All three SOWs described, on paper, more or less the same scope. He wanted to know whether he was looking at three different qualities of work or three different ways of pricing the same work. The honest answer is that he was looking at one piece of work priced through three completely different commercial models. ServiceNow consulting costs are not opaque because the market is dishonest. They are opaque because nobody in the buying process is comparing like with like. Once you understand what each model is actually charging for, the right number for a mid-market implementation falls into a much narrower range than the proposals would suggest. This is the conversation finance directors deserve to have before they sign, not three months in when the change orders start arriving.

A CIO at a Hungarian energy company asked me last month how long a ServiceNow implementation actually takes. He had three proposals on his desk. One said four months. One said seven. One said “approximately twelve depending on scope.” All three were for what he described as “basic ITSM plus a bit of HR.” He wanted me to tell him which one was lying. The honest answer is that all three were lying, but in different directions, and the most useful thing I could do for him was explain the timeline none of them had put on paper. ServiceNow implementations are not late because the platform is hard. They are late because the proposal everyone signs is built around the part of the project that vendors know how to estimate, and the parts that actually consume the calendar are either missing from the SOW or buried inside a line called “client responsibility.” This is the conversation that needs to happen before a contract is signed, not at week sixteen when the program is already three months behind.

A CIO at a Hungarian energy company asked me last month how long a ServiceNow implementation actually takes. He had three proposals on his desk. One said four months. One said seven. One said “approximately twelve depending on scope.” All three were for what he described as “basic ITSM plus a bit of HR.” He wanted me to tell him which one was lying. The honest answer is that all three were lying, but in different directions, and the most useful thing I could do for him was explain the timeline none of them had put on paper. ServiceNow implementations are not late because the platform is hard. They are late because the proposal everyone signs is built around the part of the project that vendors know how to estimate, and the parts that actually consume the calendar are either missing from the SOW or buried inside a line called “client responsibility.” This is the conversation that needs to happen before a contract is signed, not at week sixteen when the program is already three months behind.

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….

A 600-bed teaching hospital in Central Europe loses email for forty minutes on a Tuesday morning. Nothing dramatic. A certificate expires on an internal relay, and inboxes go quiet across three floors. By the time the platform team rolls the fix, the damage is already done in places you would not…

The first ServiceNow implementation cost estimate a mid-size company receives almost never looks like the second one. The difference is not always quality. Often it is staffing model, scope shape, and what the partner has decided to bury in “configuration.” This is what mid-size buyers actually pay for, where the money disappears quietly, and how…

Ask three ServiceNow partners how long an implementation takes and you will get three different answers, all of them confident. The honest ServiceNow implementation timeline for a mid-size company is narrower than vendors admit and wider than buyers hope. This is what actually happens, week by week, and what makes the difference between a clean…

The wrong ServiceNow partner can cost you a full year and most of your budget before anyone admits the project is in trouble. The right one will have you in production within a quarter and leave a platform your own team can actually maintain. Finding the best ServiceNow consulting partner for a mid-size company is…

Introduction: The 2:47 AM Email Nobody Talks About It’s 2:47 AM on a Tuesday. A nurse on the overnight shift can’t log into the EHR because her access was never provisioned after a department transfer. The IT service desk has 94 unresolved tickets in the queue. A cardiology department head is emailing HR — again…

A practical playbook for IT leaders: how ServiceNow’s ITIL incident management, problem management, and HRSD for healthcare deliver real ITSM benefits. Actionable tips, a maturity model, and the platform-thinking shift that separates reactive teams from strategic ones.

ServiceNow HRSD gives healthcare HR teams the operational muscle to handle clinical onboarding, credentialing, confidential cases, and multi-entity complexity. Here’s the practitioner’s playbook.