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.

The Real ServiceNow Implementation Timeline: Why Six Months Rarely Means Six Months
Sep 21, 2026 Implementation Strategy

The Real ServiceNow Implementation Timeline: Why Six Months Rarely Means Six Months

A COO signs a Statement of Work in January. The SI has quoted a 24-week ServiceNow implementation timeline, ITSM Pro plus a light ITOM footprint, go-live in early July. She circulates the plan internally. Marketing pencils in a launch webinar. Finance builds the licence spend into the Q3 forecast. HR schedules the change-comms rollout. By late April the delivery lead sends the first quietly worded status note. Discovery took longer than planned because the CMDB source data was worse than anyone admitted. Two integrations were re-scoped when the SAP team said their middleware team is booked until September. Change requests are stacking up. The July date is now "at risk". By June it has slid to October. By October it is November with a phased approach. The webinar is cancelled. None of this is unusual. It is the average ServiceNow implementation timeline for a mid-market rollout done properly. The problem is that almost nobody quotes it that way at the sales stage, so every project starts with a plan that was already fiction on the day it was signed.

ServiceNow Consulting Services for Mid-Sized Enterprises: What Actually Works Between 200 and 2,000 Employees
Sep 19, 2026 Choosing a ServiceNow Partner

ServiceNow Consulting Services for Mid-Sized Enterprises: What Actually Works Between 200 and 2,000 Employees

A COO at an 800-person specialty chemicals company rang me last month. Her IT director had spent six weeks on a Big 4 scoping exercise and come back with a €1.4M number, a nineteen-month plan, and an org chart showing four consultants on the account she had never met. She wanted to know if that was the price of entry for ServiceNow, or whether she was being priced like a Fortune 500. She was being priced like a Fortune 500. This is the pattern I see almost every week. Mid-market companies, roughly 200 to 2,000 employees, get quoted implementation programs designed for organisations five or ten times their size. The methodology is the same. The team structure is the same. The overhead is the same. What the client actually needs is different, and nobody bothers to redesign the delivery model around that fact. Then the CFO gets sticker shock, the project gets shelved, and the mid-market keeps running on a mix of Jira Service Management, spreadsheets, and shared inboxes for another eighteen months.

Change Management on ServiceNow: Why Your CAB Discipline Is Quietly Wrecking Your Change Failure Rate
Sep 17, 2026 Change Management

Change Management on ServiceNow: Why Your CAB Discipline Is Quietly Wrecking Your Change Failure Rate

A platform lead at a European insurer asked me last month to look at their change process on ServiceNow. Their board had just been shown a slide with a 14 percent change failure rate and the CIO wanted to know whether it was a tooling problem or a people problem. He was hoping for tooling, because tooling is buyable. I spent two days pulling change records, listening in on a CAB, and sitting with the Change team. The tool was fine. The CAB was theatre. Every Wednesday at 15:00 a room of twelve people spent ninety minutes rubber-stamping fifty-plus normal changes, arguing about two of them, and running out of time before the standard change catalogue was even mentioned. Nobody was reading the change records before the meeting. The risk score was cargo-culted from the template. The implementation plans were three sentences long. The failure rate had nothing to do with the platform. It had everything to do with the fact that change management servicenow had become a compliance ritual instead of a control.

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