Blog

  • The ServiceNow ITSM Benefits That Only Show Up at Renewal
    A VP of operations at a mid-market logistics company put a question in front of me on a Tuesday afternoon last month. His three-year ServiceNow agreement was coming up for renewal in February. Procurement had sent him a number. The number was larger than the first contract by a non-trivial margin, with the usual arithmetic of list-price increases, module expansions his teams had quietly adopted, and a managed services line that had grown each year. He had to defend the renewal to a finance committee that remembered the original business case and wanted to know whether the platform had delivered what it was supposed to. He asked me a direct question. If he stripped out the vendor marketing and the original slide deck, what were the real ServiceNow ITSM benefits he should put in front of his committee? Not the pitch. Not the twelve-point ROI table that nobody in the room believed. The actual case for renewing at a higher number. We spent the better part of two hours working through it. What came out of that conversation is, in my experience, the more useful way to think about the advantages of ServiceNow. The benefits that justify the second contract are not the ones that…
  • ServiceNow CSM for B2B: The SLA Gap That Quietly Costs You Enterprise Renewals
    A VP of customer success at a European SaaS vendor called me on a Monday morning about a renewal she had just lost. Three million a year, one of her top ten accounts, gone. The exit interview told her the customer felt “underserved” over the last eighteen months. Her head of support pulled the data to prove them wrong. SLA attainment on that account was 94%, well above the contracted 90%. Agent satisfaction scores were fine. Not a single case was formally escalated. On paper, the service had been exemplary. On the customer’s side, the story was different. Their head of IT had a spreadsheet of thirty-seven tickets that had technically met SLA but had taken three or four touches to resolve. Eight of them had been reopened. Four cases had been closed with workarounds that never got fixed. The customer did not care that the first response was logged at hour 3 of a 4-hour target. They cared that nothing was ever actually done. This is the shape of most ServiceNow CSM problems I see in mid-market B2B. The platform is not broken. The configuration measures a service model that satisfies the contract while quietly losing the account.
  • The Boutique ServiceNow Consulting Trade-Off: What You Give Up, What You Gain
    A CIO at a mid-sized European insurer asked me a fair question on a call last month. He was leaning toward hiring me to lead his ITSM rebuild, but his board had pushed back on the single-partner risk. “What happens if you get hit by a bus?” he said. “What happens if you decide to take a sabbatical in month three? I lose the whole program.” It is the honest objection to boutique ServiceNow consulting, and the one that most boutique practitioners paper over with reassurances about continuity plans and backup associates. The reassurances usually ring hollow because the buyer can hear that the firm has four people total, and if one of them walks, you are in a different firm. I want to make a different argument. The single-partner concern is real. It is not the main risk on your project. The main risk on your project is that the people doing the work in month four are not the people who promised you the work in month zero. A Big 4 engagement eliminates the bus problem by replacing it with a larger problem that is harder to see. Boutique ServiceNow consulting makes a specific, bounded trade. Understanding exactly what that trade is, in both directions, is what buyers at your stage…
  • When Big 4 Managed Services Stop Answering: The Case to Switch Your ServiceNow Partner After Go-Live
    A head of IT at a 900-person pharma distributor called me on a Monday morning this October. His ServiceNow ITSM instance had gone live eighteen months earlier with one of the Big 4. The build itself was fine. Not elegant, but functional. The problem was what had happened since. He had an SLA with the same firm for managed services, Gold tier, priced at the gold-tier number. Response times were the kind of thing that only looks good in a quarterly review deck. When his service desk raised a ticket about a flow that had stopped firing after a platform upgrade, the response came back six working days later, from an engineer three time zones away, asking him to export system logs the engineer could have pulled himself. The flow had been broken that whole time. His incident queue, his change advisory board, his auditor-facing reports were all tied to that flow. He didn’t ask me whether he could switch partners. He asked me how fast. That conversation is the one I keep having this year. Not the mid-build rescue. The post-go-live one. The build was fine. The relationship after isn’t. If you’re running a ServiceNow instance that a Big 4 partner stood up for you and you’re now paying…
  • HRSD Shared Services: What Actually Breaks Six Months After Go-Live
    An HR shared services lead at a 3,200-person industrial group in the Ruhr called me in the first week of October. They had gone live on ServiceNow HRSD in mid-March. The project had been clean. Two tiers of case management, Employee Center up, Lifecycle Events wired for onboarding and offboarding, SuccessFactors sitting underneath as the system of record. The go-live metrics were the kind you put in a steering slide. Case volume handled per FTE up eighteen percent. First response time down forty-two percent. Portal adoption at seventy-six percent in the first month. Six months later the numbers had flattened and the complaints had rotated. The HR business partners were saying the tool felt heavier than the inbox it replaced. The works council was asking pointed questions about who could read what case data. Two of the regional HR managers had started routing sensitive cases back through email because they did not trust the security model. The shared services lead sent me the Employee Center feedback form export and asked a simple question. Why does HRSD get worse at month six.
  • ServiceNow Field Service Management: Where Dispatch Logic Breaks and What Fixes It
    A regional operations director at a lift maintenance company outside Milan called me in late September. They run around four hundred service engineers across northern Italy, Austria, and Slovenia, every one of them driving a van and carrying a laptop with the ServiceNow mobile agent on it. The platform had been live for fourteen months. Dispatch was broken. The specific complaint was that the automated scheduling engine was producing routes that engineers refused to run. Jobs that should have gone to the nearest qualified technician were landing with someone two hours further out. Priority tickets were being queued behind preventive maintenance visits. Customers were calling the service desk directly, bypassing the portal, because the portal said “scheduled for tomorrow” when the engineer was actually three days out. The operations director showed me a Monday dispatch screen with sixty-three jobs assigned to the automated solver and forty-one manually overridden. The dispatcher had become a human reconciliation layer between what the system said and what the engineers actually did.
  • ServiceNow Consulting Costs: The Change Request Arithmetic That Doubles Your Budget After Signature
    A procurement lead at a €1.2 billion industrial group in Lyon forwarded me a spreadsheet in October. The ServiceNow ITSM programme was ninety percent complete. The signed statement of work was €280,000 fixed-fee with a declared T&M buffer of ten percent. The current invoiced total was €442,000. Nothing in the implementation itself had failed. The platform worked. The business was happy with the configuration. The budget had not been eaten by a crisis. It had been eaten by twenty-three change requests across eight months, each one approved individually, each one defensible on its own terms, each one at a day rate thirty percent higher than the rate baked into the fixed-fee bid. Twenty-three line items. One hundred and sixty-two overrun days. A procurement team that could not point to a single conversation where someone said “no.” She asked me the only question that mattered. “How does a fixed-fee contract turn into a sixty percent overrun?”
  • ServiceNow Consulting Services for Mid-Sized Enterprises: What You Actually Need
    A HR director at a 480-person industrial software company called me two weeks ago. She had three proposals on her desk from Big 4 partners. One quoted fourteen months and €1.6M for an HRSD plus ITSM rollout. Another quoted seventeen months with a dedicated program manager line item that cost more than her entire L&D budget. The third quoted “to be scoped after a six-week discovery phase,” and the discovery phase alone was €240k. She asked me a reasonable question. “Are we really this complicated, or is somebody padding?” She is not that complicated. The 400-to-900-person band is where ServiceNow sellers and partner delivery teams quietly misread the room. The methodology is built around Fortune 500 clients with ten business units and six legal entities. When that methodology is pointed at a mid-market company with one HR team, one shared service centre, and a single ServiceDesk Monday-to-Friday, you get a program that costs three times what it should and takes two times as long. The platform is the same. The company is not. ServiceNow consulting services for mid-sized enterprises should look nothing like a global enterprise rollout, and most of what is marketed to the mid-market…
  • Why Your Enterprise ServiceNow Implementation Timeline Doesn’t Scale Linearly With Scope
    A CIO at a 7,000-person industrial group called me last month, two weeks before Phase 2 kickoff. The business had decided, after Phase 1 went live for IT and HR in two countries, that Phase 2 would add Logistics and Finance Shared Services across five more countries. The implementation partner had quoted an extra ten weeks. The CIO wanted a second opinion before he signed the change order. I ran the numbers with him over a ninety-minute call. Ten weeks was not wrong by a little. It was wrong by a factor of two and a half. The real additional time was between twenty-four and twenty-eight weeks, assuming nothing else changed. He signed nothing that week. This is the problem I keep running into on enterprise work. The sales math assumes a ServiceNow implementation timeline is additive. One more department, so a bit more time. One more country, so a bit more effort. In reality, enterprise ServiceNow implementation time scales nonlinearly, and the nonlinearity shows up in exactly the places that no one measures until it is too late.
  • The ServiceNow ITSM Benefits a CFO Actually Buys, Two Years After Sign-Off
    A CFO at a 500-person industrial services company sent me a note last month. He had been part of the decision to buy ServiceNow about two and a half years before, had signed the implementation statement of work, and had just finished a quiet internal review of what the platform had actually delivered. He wanted my view on something that was bothering him. The business case he had approved in 2023 was wrong on almost every line. The savings he had been pitched never materialised in the way the slides said they would. And he was still, two years later, enthusiastic about the investment. He asked me whether that was normal. I told him it was more normal than most people in the industry want to admit, and that if he looked carefully at what the platform had actually delivered, he would find a different and better set of ServiceNow ITSM benefits than the ones he had been sold on. We spent an hour on the call working out what those were. I want to write up what we discussed, because it is a much more honest conversation about why ServiceNow is worth the money than most of the pre-sale material I see pitched into mid-market CFOs.
  • What Boutique ServiceNow Consulting Settles in a Two-Hour Scoping Call That Takes a Big 4 Six Weeks
    A head of IT at a 600-person logistics firm sent me a scoping document last month. Forty-one pages. It had been produced by one of the Big 4 after what they called a “discovery and assessment engagement.” Six weeks, three onsite workshops, nineteen stakeholder interviews, a kickoff deck, an interim readout, a final readout, and a signed statement of work for the next phase. The invoice for the discovery was €84,000. He asked me to look at it before he signed the implementation SOW. I read the whole thing on a Sunday afternoon. The actual content, once you stripped out the appendices, the methodology slides, the “future state vision,” the governance structure diagrams, and the eleven-page stakeholder RACI, fit on about two pages of substance. His current ITSM instance was over-customized. He needed a rebuild of incident, problem, and change on a cleaner data model, with a reasonable integration to his monitoring tool and a sane service catalog for his internal users. That was it. I called him back on the Monday. We spent two hours on the phone. By the end of that call I had a scoped build plan, a sequencing recommendation, a rough cost band, and a shortlist of the three technical…
  • ServiceNow Flow Designer in Production: Patterns I Trust and Patterns I Don’t
    A client called me a few weeks ago because their new HR onboarding flow had been failing silently for eleven days. Nobody had noticed. The error handler on the parent flow caught the exception, logged a one-line message to a custom table, and quietly moved on. Twelve new hires started that fortnight without laptop requests, access provisioning, or payroll setup. The flow was green in Flow Designer. The dashboards were green. HR found out when the first employee emailed asking why she had no laptop on day three. That is the problem with ServiceNow Flow Designer in production. It makes building the happy path trivial, so teams build the happy path and move on. The error paths, the retries, the idempotency, the observability, the subflow boundaries, the integrationhub rate limits, none of those get the same attention. Six months later the instance is covered in flows that work until they don’t, and when they don’t, nobody can tell. I spend a lot of my consulting time on ServiceNow Flow Designer, both greenfield builds and rescue work on flows other people wrote. The patterns below are what I have learned to trust, and the ones I have learned to rip out when I inherit them.
  • When to Switch Your ServiceNow Partner Mid-Project (And How to Do It Without Blowing Up the Timeline)
    A programme director at a mid-market insurer called me on a Wednesday last autumn. Her ITSM rollout was eight months in with one of the Big 4. The CMDB was still empty of anything useful. The incident form had thirty-two custom fields nobody could explain. The named architect on the SOW had been rotated to another account twice already, and the delivery lead was a 24-year-old running Scrum ceremonies from a slide template. She wasn’t angry. She was past that. She wanted to know if it was too late to switch. That call isn’t unusual. It’s roughly one in four of the inbound conversations I have, and the pattern repeats so often it has a shape. The engagement didn’t fail at month eight. It failed at month two, when the senior architect who sold the deal handed the keyboard to a bench team. The next six months were the client slowly figuring that out. If you’re reading this with a similar knot in your stomach, the question isn’t whether you can switch your ServiceNow partner mid-build. You can. People do it. The question is whether you understand what breaks when you do, what gets recovered, and what the next three months actually look like.
  • What a ServiceNow Instance Health Audit Actually Finds in Ten Days
    A new CIO at a mid-market insurer inherited a ServiceNow instance last February. Three years of implementation under a Big 4 partner, two go-lives, one half-finished HRSD rollout, and a renewal invoice sitting on her desk for a licence tier she could not justify. She asked her ServiceNow account manager what state the platform was in. He said “healthy, you’re on Washington.” That was the answer. On a half-million-euro-a-year platform. She called us the following week. Ten business days later she had a 42-page report, a dashboard with 46 scored items across six dimensions, and a conversation to have with her account manager that was no longer symmetric. The instance was not broken. It also was not healthy. It was the normal condition of a ServiceNow instance that has had three years of change, two partner handovers, and nobody specifically paid to look after it.
  • ServiceNow Consulting Costs: Fixed-Fee vs Time-and-Materials, and Which One Actually Protects Your Budget
    A finance director at a logistics group in Rotterdam called me in February. Their ServiceNow ITSM rollout had been running for eleven months on a time-and-materials contract with one of the big consultancies. The original estimate was 420 billable days. They had just signed off invoice number thirty-four, and the running total was 710 days. Nothing was live yet. The project manager kept using the phrase “complexity emerged during discovery,” which is consultant Esperanto for “we didn’t scope it and now we’re charging you to fix our scoping.” She asked me one question. “Would a fixed-fee contract have stopped this?” The honest answer is that it would have stopped most of it, and the parts it would not have stopped would at least have been someone else’s problem. That is the whole argument for how ServiceNow consulting costs should be structured in a mid-market engagement. Not that fixed-fee is cheaper on paper, because sometimes it is not. The point is that fixed-fee shifts the scope risk off your P&L and onto the vendor’s, and that is the risk that actually blows budgets.
  • ServiceNow Consulting Services for Mid-Sized Enterprises: Where the Scope Trap Lives
    A COO at a 650-person logistics company calls on a Tuesday morning. They signed the SOW six months ago. The deck promised ITSM, CSM, HR, a bit of ITOM, “foundational governance”, and a roadmap to Now Assist by month ten. Their partner, a mid-tier regional SI, is burning through the budget at a rate that puts them at 140 percent by go-live, and they are now five weeks past the first phase milestone with no live incident module. The CFO wants to know whether to pause, replan, or fire the SI. The COO wants to know what went wrong. Nothing went wrong. The scope went wrong, six months ago, on a slide no one scrutinised. This is the single most common failure mode I see when mid-sized companies buy a platform built for the Fortune 500, and it is almost always baked in before the first developer logs into the instance. ServiceNow sells the same catalog to a 650-person logistics company and to a 65,000-person bank. The modules are identical. The licensing is identical. The sales motion is identical. What is not identical is the organisational capacity to absorb the platform.
  • The Two Weeks That Decide Your ServiceNow Implementation Timeline
    A head of IT at a 600-person industrial supplier called me after their partner’s third timeline slip. The signed statement of work said twenty-two weeks to live incident, request, change, and a thin CMDB. By week nineteen, the delivery lead was asking for an eight-week extension and quoting discovery findings as the reason. His board had already approved the extension when he phoned me, so he was not asking for help negotiating. He wanted to know what he could do differently on the next phase so it did not happen again. His question is the right one, and the honest answer is that almost every ServiceNow implementation timeline is decided before the official kickoff meeting. The two weeks before the project is announced to the business are where most of the slip is manufactured, and nobody budgets for them. I say this at the risk of annoying every account executive at every system integrator. They sell a start date. Clients buy a start date. Everybody wants the kickoff slide in the second week of the quarter. What actually drives whether a project lands on time has very little to do with the kickoff and almost everything to do with the preparation that either happened or did not…
  • ServiceNow ITIL Best Practices: The Problem Management Discipline Mid-Market Teams Skip
    A head of service at a 900-person industrial equipment firm in the Benelux region sent me her incident volumes last month. The weekly count had been climbing for eleven months straight, from roughly 180 to just over 320. The service desk was adding people. The CFO was unhappy. The CIO had just agreed a second-wave hiring plan for the service desk. Nobody on the leadership team could tell me what the top five recurring root causes were, because nobody had been counting. That gap is the whole post. The ServiceNow platform ships with a Problem module that is competent out of the box, free to turn on, and almost universally ignored in mid-market shops. Every one of those 320 weekly incidents had a cause. Perhaps forty distinct causes drove the full volume. The firm was paying full ticket cost for all 320 and had never identified the forty. This is the hole where ServiceNow ITIL best practices stop being an abstract reference library and start being a very concrete difference in run cost. I want to walk through what mid-market problem management discipline actually looks like on ServiceNow, where the common failure modes are, and what two or three moves get you most of the value in…
  • The Procurement Filter That Keeps Mid-Market Buyers from a Boutique ServiceNow Consulting Partner
    A head of IT at a 650-person logistics group in southern Germany called me in late September. He had just signed with one of the Big 4 for a two-year ServiceNow programme covering ITSM, HRSD and basic SPM. The number on the SOW was a shade under €2.3 million. He was not calling to celebrate. He was calling because, three weeks in, he had met four different people from the delivery team, none of whom had been in the sales meetings, and the solution architect who had sold him the design was now scheduled for one day a month on the engagement. I asked him why he had not seriously evaluated a smaller partner. His answer was the thing I want to write about today: his procurement team ran a standard RFP template they had used for ERP and the enterprise data warehouse. The template filtered out every firm with fewer than 500 employees globally in question 3. He never got to see a boutique ServiceNow consulting proposal because the gate stopped them before the technical scoring started. This is the mechanism. It is not that mid-market buyers prefer the Big 4. It is that mid-market procurement teams import filters built for different categories of spend and apply them to platform work…
  • The ServiceNow ITSM Benefits a CFO Actually Pays For
    A CFO at a 900-person engineering firm pulled me into a call last spring with one question. Not about the platform, not about workflows. “Give me the three lines I write on the slide to the board. Because right now I have ‘service management’ and the board is going to ask me what we got for 480 thousand euros.” That is the real question hiding inside every pitch deck on ServiceNow ITSM benefits. The sales conversation is about automation and single pane of glass. The invoice conversation is about where the money shows up again. Those are not the same conversation, and the gap between them is where most ServiceNow business cases quietly die after year two. I have spent fifteen years watching this. The patterns are consistent. The CFO buys three things, and only three. Everything else is interior decoration.