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.

Book a Free Call → See Our Results

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
What We Do

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
Why Us

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.

How We Work

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.

What Clients Say

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
All reviews on Trustpilot →
Insights

From Our Blog

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

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

ServiceNow Major Incident Management: The War-Room Patterns That Actually Hold Under Pressure
Jun 16, 2026 Major Incident Management

ServiceNow Major Incident Management: The War-Room Patterns That Actually Hold Under Pressure

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

How to Pressure-Test a ServiceNow Implementation Timeline Before You Sign the SOW
Jun 15, 2026 Implementation Strategy

How to Pressure-Test a ServiceNow Implementation Timeline Before You Sign the SOW

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

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.

Book Free Call → The 10-Day Health Report