Boutique ServiceNow Consultancy

Senior ServiceNow Consulting. No Juniors On Your Instance.

CMDB, ITSM and automation for enterprise teams who can't afford to do it twice. Budapest-based; we work EU and US hours.

50+

Enterprise Clients

60%

Faster MTTR

10yr

Platform Experience

Instance Health Monitor Live
CMDB Accuracy
0
+12.3% this quarter
Auto-Resolved
0
+28% vs last month
Avg. Resolution
0
-60% from baseline
CI Validated
2,847 assets
Flow Triggered
auto-remediation

ServiceNow work delivered for teams at

European Commission OECD Swiss Army Audi OMV Tetra Pak

The Work, Specifically

No "digital transformation." Six things — and for each one, what it actually means when we do it.

🗃

CMDB Implementation

Data model, Discovery, Service Mapping, reconciliation rules, and a health dashboard someone will actually look at. We'll also tell you which CI classes you're populating for no reason.

Explore
🔧

ITSM Optimization

Incident, Problem, Change, Request — configured for how your team works, not how the demo did. Most of the slowness we find is assignment rules and approval chains, not the platform.

Explore

Flow Designer

Flow Designer, IntegrationHub spokes, scripted actions. We won't reach for a script when a flow does it, or a flow when a UI policy does it — automation you keep, not automation you rebuild.

Explore
🔗

Integrations & APIs

REST, SOAP, MID Server, IntegrationHub — ServiceNow talking to Azure, AWS, Jira, SAP, Teams. With retry logic and a credential that won't silently expire, because that's the half that usually gets skipped.

Explore
📈

Reporting & Analytics

Performance Analytics, scorecards, SLA tracking. The hard part isn't the dashboard — it's choosing the handful of numbers your CIO will actually act on. We help with that part too.

Explore
🛡

Managed Services

Upgrades, patching, day-to-day admin, and the small fixes that pile up. On-demand or a light retainer — no minimums designed to bill you for doing nothing.

Explore

Boutique, On Purpose

Small shop, senior people, your time zone. We agree what "done" looks like in numbers before anyone touches the instance — and we hand the keys back, because re-hiring us should be a choice, not a dependency.

01

Certified — And Scarred

CSA, CIS-ITSM, CAD and CIS-Discovery certified — and we've cleaned up enough other people's instances to know what doesn't last.

02

Numbers Before Config

MTTR, CMDB accuracy, automation rate — we agree the target before writing a line of config. If those numbers don't move, we're not finished.

03

EU & US Hours

Budapest base, EU and US working hours. You're not waiting overnight for an answer to a blocker.

04

No Lock-In By Design

Every build ships with the docs and a walkthrough so your team can maintain it without us. We'll also tell you when something's a bad idea — including when it's our idea.

Four Phases. Nothing Goes Live Untested.

Weekly demos, no big-bang surprises, and a check against the numbers we agreed up front.

1

Discover

Read-only look at the instance as it is, plus straight talks with the people who live in it. Root causes, not symptoms.

2

Design

Data model, workflows and architecture on paper first — reviewed with you before anyone configures a thing.

3

Build

Short sprints, a working demo every week, testing as we go. Go-live is a non-event by the time we get there.

4

Hand Over

Post-launch tuning, the walkthrough so your team owns it, and the before/after on the metrics from phase one.

Don’t Take Our Word For It — Read Theirs

Verified reviews from Trustpilot

★★★★★

“Excellent ServiceNow Technical Consultant — As the Hiring Manager overseeing a number of contractors for the ServiceNow practice, Mladen and I interacted for contract arrangements, timesheets, invoicing and any general queries. Mladen was always reliable, prompt and communicative, very easy to work with and a pleasure to speak to! His feedback from his …”

LJ
Lucia JelleyUnited Kingdom · Verified review · Trustpilot · Jan 2023
★★★★★

“Mladen is a very experienced developer and is very kind, always in for a good personal chat but he got the right attitude, respect and know-how. We created a double Interface between ITSM toolings which caused some issues here and there, Mladen was one of the most experienced developers which fixed and corrected a lot for my process and tooling.”

RN
Rogier NasNetherlands · Verified review · Trustpilot · Jan 2023
★★★★★

“Friendly, knowledgable and professional — I have worked alongside Mladen as a fellow Senior Consultant on a long-term post-implementation support and additional development project where he has been pivotal its success. Mladen, is friendly, knowledgable and professional in carrying out his development activities and goes above and beyond to ensure clients …”

CH
Cameron HSUnited Kingdom · Verified review · Trustpilot · Jan 2023
★★★★★

“Mladen acted as a senior ServiceNow developer and showed experience, knowledge and has been a valuable member of the team. Delivered everything as expected. Great positive person, great addition to the team.”

SM
Stefan MilkicSerbia · Verified review · Trustpilot · Mar 2026

From Our Blog

ServiceNow guides, ITSM best practices, and automation patterns from our team.

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

The Eight Line Items That Inflate ServiceNow Consulting Costs by 40 Percent

The Eight Line Items That Inflate ServiceNow Consulting Costs by 40 Percent

The CIO of a mid-sized European insurer pulled me into a call last quarter with a problem most buyers only notice when it is too late. Her ServiceNow ITSM build had been signed at €620,000 and she was now staring at change requests that put the final number closer to €960,000. The work itself was not bad. The platform was being built competently. What she wanted to know was whether the overrun was normal or whether she had been set up. I read the SOW and the seven change orders. The answer was not flattering to her partner, but it was also not unusual. The original price was honest about the visible scope and silent about the predictable cost drivers that every experienced ServiceNow practitioner knows will surface inside the first six months. Those drivers were not surprises. They were a pricing strategy. And once you know what they look like, you can take 30 to 40 percent off most mid-market proposals before the kickoff meeting. This post walks through the eight specific line items that quietly inflate ServiceNow consulting costs, what each one really should cost, and how to write them into the SOW so you are not negotiating from a position of weakness later.

ITSM Integrations for Reducing Mean Time to Resolution: A Field Guide for SAP, SuccessFactors and Workday Shops
Jun 18, 2026 Integrations

ITSM Integrations for Reducing Mean Time to Resolution: A Field Guide for SAP, SuccessFactors and Workday Shops

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

Want the Truth About Your ServiceNow?

Book a free 30-minute call — or go straight for the full picture: the 10-Day Instance Health Report scores every part of your instance 0–100, with a prioritized action plan.