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.

ServiceNow Consulting Costs: What You Actually Pay For, and Why the Number on the Statement of Work Is Almost Never the Final Bill
Aug 21, 2026 Implementation Strategy

ServiceNow Consulting Costs: What You Actually Pay For, and Why the Number on the Statement of Work Is Almost Never the Final Bill

A CIO at a mid-market insurer emailed me on a Tuesday morning last month. Subject line: "second opinion." She had a signed SOW from one of the Big 4 for a Now Assist rollout across ITSM and CSM. The headline number was €780,000 over nine months. Reasonable, on paper. Six months in, the run rate was tracking to €1.4 million and the go-live date had slipped twice. She wanted to know two things. Was she being taken for a ride, and what would a boutique shop have quoted for the same scope. I get some version of that email about every three weeks now. The gap between what buyers think they are signing up for and what they end up paying is the biggest source of pain in ServiceNow programmes right now, and it is almost entirely avoidable if you know where to look before you sign. Every ServiceNow implementation has three cost lines. The one on the SOW. The one that hits your budget. And the one your finance director will actually approve when the change request lands on their desk in month five.

The Real ServiceNow Implementation Timeline: What Vendors Won't Print in the SOW
Aug 20, 2026 Implementation Strategy

The Real ServiceNow Implementation Timeline: What Vendors Won’t Print in the SOW

A CIO at a European industrial group forwarded me a slide last week. Big four brand on the cover, twelve neat swimlanes, "Go-Live: Q1 2027" in bold across the bottom. Nine months, ITSM plus HRSD plus a CMDB refresh, three geographies, forty-two integrations, twelve thousand employees. He asked me one question: is this real. I told him what I tell everyone who shows me a plan like that. The dates are real. The scope is not. Something in that triangle is going to slip, and if nobody names which side before the kickoff, the project will name it for them at month seven. This is the conversation nobody wants to have during a pitch. Vendors sell aggressive dates because aggressive dates win RFPs. Buyers accept aggressive dates because they need a business case that clears the CFO. Nine months sounds decisive. Fourteen months sounds like the vendor is padding. So everybody signs, and then everybody spends the second half of the project renegotiating what "live" actually means. The honest number for a full mid-to-large ServiceNow implementation is not nine months. It's twelve to eighteen, and the shape of those months matters more than the total.

Change Management on ServiceNow Fails at the CAB, Not at the Form
Aug 18, 2026 Change Management

Change Management on ServiceNow Fails at the CAB, Not at the Form

An infrastructure lead at a European insurer called me last month with what he thought was a workflow problem. His team's change request form on ServiceNow had grown to sixty-two fields. The approval routing had eleven conditional branches. Emergency changes were sitting in the queue for two days waiting for a rubber-stamp signature. His CIO had asked him to fix the form. The form was not the problem. The form was the last place anyone looked for a problem that started in the change advisory board eighteen months earlier. This is the pattern I see in most mid-market change management ServiceNow deployments. The platform is doing exactly what it was configured to do. The configuration reflects a set of decisions the CAB made, or failed to make, over years of drift. And by the time someone escalates, the diagnosis has already been misdirected at the tool.

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