The phrase "ongoing support retainer" covers a lot of ground in the ServiceNow world. Some of it is a block of hours you can use for incidents and small enhancements. Some of it is a named resource who is nominally available but usually busy on other clients. Almost none of it is what we mean when we say Platform Excellence Partnership.
Here is what ours actually involves.
The monthly health scan
Every month, your platform is assessed against ten domains and 50+ metrics. Configuration hygiene, CMDB integrity, upgrade readiness, integration health, and AI readiness are scored, trended, and reported.
- Anchor client platform health score
- 95/100
- Domains assessed every month
- 10
- Metrics assessed every month
- 50+
The score matters less than the trend. A platform at sixty-five and improving is in a better position than one at eighty-five and declining. What we are tracking is trajectory, and surfacing the things that will become problems before they become incidents.
The governance cadence
Each month there is a structured conversation with your platform owner. Not a status update but a decision meeting. We work through:
- The health scan findings and what to do about them
- The enhancement backlog and how to prioritise it
- Any architectural decisions that need to be made before they get made by accident
- What is coming in the next ServiceNow release and what it means for your configuration
This is the conversation most platforms never have. Without it, architectural decisions get made by whoever raises a ticket and whoever happens to pick it up. The platform drifts. Technical debt compounds quietly until it is expensive to fix.
What the architect actually does
The partnership includes a dedicated Certified Architect: the same person, consistently. Not a ticket queue staffed by whoever is available.
Your architect reviews every significant platform change before it goes to production. Not as a bureaucratic gate, but as a genuine architecture review that catches the problems that are much cheaper to fix before they are deployed than after.
Top tip
The most common thing we catch in architecture reviews is not bugs; it is configuration choices that work fine in isolation but create problems when the platform is upgraded or when another team makes a seemingly unrelated change. This is the kind of thing that only shows up if someone is holding the whole picture in their head.
Your architect is also available for design questions: the kind that come up in the middle of a project and need a quick answer from someone who understands the platform deeply, not a ticket that comes back in three business days.
Enhancement delivery
The partnership includes structured delivery of improvements within the retainer. Not a separate project, not separately scoped and separately billed for routine enhancement work. This is what makes the model work for clients: the friction between identifying an improvement and delivering it is low.
Significant new capability, such as a new module, a major integration, or a custom AI implementation, is scoped and delivered separately. But the ongoing work of making a platform better is included.
Why retainer beats project for platform work
A platform delivered as a one-time project and then handed to an operations team tends to drift. The operations team is skilled at keeping the lights on, not at architectural evolution. The SI who built it moves on to the next project.
What the platform needs is someone who is always current: always watching the trajectory, always seeing the next ServiceNow release coming before it arrives, always available when an architectural question needs answering.
That is the model. If it sounds like something your platform needs, start with a conversation.
- Platform Excellence
- Architecture
- Retainer
- ServiceNow
Jamie Douglas
Certified Master Architect, GlydePath. One of fewer than 700 CMAs worldwide, with 22 years in IT and 15 in ServiceNow.