Blog

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.

The Rise of Budapest as a ServiceNow Delivery Center Over the past five years, Budapest has quietly become one of Europe’s most important cities for ServiceNow talent. What started as a cost-arbitrage play has evolved into something more significant: a genuine center of ServiceNow expertise with a depth of talent that rivals London, Amsterdam, and…

Why ServiceNow Upgrades Require Serious Planning ServiceNow releases two major versions per year, and staying current is not optional — it is a business requirement. Older versions lose support, miss critical security patches, and cannot access new features that your competitors are already using. But a poorly planned upgrade can break integrations, disable customizations, and…

Why This Comparison Matters When enterprise organizations evaluate ServiceNow partners, the shortlist typically includes one or two Big 4 firms (Deloitte, EY, PwC, KPMG) alongside global system integrators (Accenture, DXC, Infosys) and smaller boutique consultancies. The assumption is usually that bigger is safer. In our experience working alongside — and sometimes cleaning up after —…

The Confusion Between CMDB and Asset Management One of the most common questions we get from new clients is: “Do we need both a CMDB and asset management, or is one enough?” The confusion is understandable — both systems track IT items, both live in ServiceNow, and there is significant overlap in the data they…

What MTTR Actually Measures and Why It Matters Mean Time to Resolution (MTTR) is the average time from when an incident is reported to when it is fully resolved. It is not mean time to respond, not mean time to acknowledge — it is the total clock from “something is broken” to “everything works again.”…

Why Every ServiceNow Instance Needs a Health Check When we onboard a new client, the first thing we do is run a comprehensive health check on their ServiceNow instance. Not because we assume things are broken, but because every instance accumulates technical debt over time — skipped upgrades, abandoned customizations, orphaned scripts, and configurations that…

When to Use Flow Designer vs. Legacy Workflows ServiceNow Flow Designer is the future of automation on the platform, but that does not mean you should migrate everything overnight. After configuring Flow Designer across 50+ enterprise implementations, we have developed clear rules for when to use it and when legacy workflows still make sense. Use…

Why Your ServiceNow CMDB Data Quality Keeps Getting Worse Every ServiceNow implementation starts with clean data. Six months later, your CMDB has duplicate CIs, broken relationships, and teams that have stopped trusting it altogether. Sound familiar? After leading 50+ ServiceNow implementations for enterprises like Deloitte, Audi, and Tetra Pak, we see the same pattern: organizations…