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.

ServiceNow Consulting Costs: Fixed-Fee vs Time-and-Materials, and Which One Actually Protects Your Budget

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

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

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

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.