A conversation
A discussion with the consultants who would actually deliver the work. No sales team. No pitch deck.
Managed Services
Decide who runs it, before the project ends
The operating decision
Most organizations decide how a platform will be run by not deciding.
The project finishes, hypercare ends, the delivery team moves on, and whatever happens next becomes the operating model. Four different jobs get called managed services, and buying the wrong one can cost a year.
The problem
"We need support" can mean four different things
Ask four organizations what they want from support and you can get four different answers. One wants somebody accountable for the whole platform. One wants a small number of critical solutions to keep working. One has written governance rules and needs somebody to actually run them. One needs a senior person to decide between competing AI demands.
These are different accountabilities, and a contract that tries to cover all of them at once tends to cover none of them well.
The project ends with an open question.
Hypercare has a defined end. What happens after it often does not have an owner.
Recurring spend needs a reason.
A renewable line item has to show what changes, who is accountable and what the review looks like.
AI added a second operating problem.
The platform still has to work, and now AI needs both oversight and direction. Those are different jobs, and they rarely sit with the same person.
Lock-in is a fair worry.
The reasonable suspicion about any managed service is that it is designed to keep you dependent. A good one should be able to show how you would take it back.
The four jobs
Name the job, and the choice gets clearer
01
Run the platform.
Somebody is accountable for the whole ServiceNow platform staying coherent, healthy and worth its cost.
02
Keep named solutions working.
Somebody is accountable for an agreed set of solutions continuing to do what they were built for.
03
Operate the governance.
Somebody runs the reviews, prepares the decisions, tracks the exceptions and keeps the evidence, so the policy is applied rather than filed.
04
Lead the AI decisions.
Somebody senior is accountable for turning competing AI demands into clear business decisions, within a mandate you set.
You will usually need one or two of these, rather than all four. Some organizations need none of them yet, and we will tell you if that is you.
The services
Four ongoing services
Each has a focused scope.
01
Platform Governance
A named, accountable owner for your ServiceNow platform: its health, its incoming demand, its upgrades and its direction over time.
For organizations where the platform now matters to the business but nobody owns it end to end.
Learn about Platform Governance →02
Solution Support
Bounded support for an agreed set of solutions: fixing defects, deciding what is a defect and what is a change, releasing changes safely and owning recurring problems.
For organizations with a small number of business-critical solutions that must not quietly stop working.
Learn about Solution Support →03
Governance as a Service
The governance you have agreed, operated on an agreed cadence and primarily for AI: reviews, inventory, prepared decisions, exceptions and evidence.
For organizations that wrote the rules, or now face new ones, and found nobody had time to run them.
Learn about Governance as a Service →04
Fractional Chief AI Officer (CAIO)
Senior AI leadership on a part-time basis, within a written mandate you set.
For organizations that need accountable AI direction before creating a permanent executive role.
Learn about Fractional CAIO →If regulation is why you are here
New AI rules, including the EU AI Act, make it hard to operate without knowing which AI you run and how it is overseen. AI Control Tower is the ServiceNow capability for that visibility. We set it up as implementation work, and Governance as a Service can run the process around it.
See AI Control Tower →Which one do you need
Start from the problem you have
If this is your problemThe serviceWhat you getYour next step
Nobody decides across the platform as a wholePlatform GovernanceA named owner, prioritized demand, platform health and upgrades, within a mandate you setTalk about your platform's current state →
One or a few business-critical solutions are driftingSolution SupportDefect fixes, a clear call on what is a defect and what is a change, a safe release pathAgree which solutions need support →
The governance rules exist, or new ones apply, but nobody runs themGovernance as a ServiceReviews, prepared decisions, tracked exceptions and kept evidence, on an agreed cadenceReview your current governance →
AI demands compete and no senior person decidesFractional CAIOSenior AI direction within a written mandate, a portfolio view, a plan for handing over to a permanent roleDiscuss your AI leadership needs →
Regulation or your board wants proof of what AI you run and how it is controlledAI Control Tower, set up as implementation workThe ServiceNow capability for that visibilitySee AI Control Tower →
Go-live is coming and nobody has decided what happens nextDecided with you, before hypercare endsAn ongoing model chosen on purposeTalk about your ongoing model →
More than one of these applies, or you are not sureDecided with youA clear answer, including when you need none of theseTalk about your ongoing model →
Not sure which of these you need?
We will tell you, including when the answer is none.
After go-live
What happens when hypercare ends
Implementations tend to end the same way: go-live, a set period of intensive support, and then a gap. We contract hypercare as part of implementation work, with a fixed end date. The useful question is what you want in place when that date arrives, and the time to answer it is before go-live, not in the last week of hypercare.
01
Build
02
Go-live
03
Hypercare
04
Transition
Overlaps the final weeks of hypercare.
Decision
Ongoing model
Chosen on purpose, not by default.
How the handover into ongoing support runs, step by step, is on the Solution Support page.
What you choose, what you keep
Choose what we run, and keep everything else
Each service is scoped and contracted on its own, so you take only what closes a gap. Where two work well together, it is usually for one of these reasons.
Platform Governance+Solution Support
Example: when the platform needs an owner and two or three solutions need close attention.
Governance as a Serviceafteran AI Control Tower implementation
Example: when the visibility is in place but nobody runs the process around it.
Fractional CAIO+Governance as a Service
Example: when AI needs both senior direction and working controls.
If one is enough, start with one.
Whatever you choose, the business stays yours. This is where we draw the line.
AreaWho owns it
Business process, priorities and dataYou
Budget, investment and final approval of decisions, including risk acceptance and exceptionsYou. We prepare, record and escalate.
Legal and regulatory accountability, including as data controllerYou. We meet the obligations in our data processing and security terms.
User access approval, testing sign-off and approval of production releasesYou
Configuration and documentation created during the serviceYou
The ServiceNow subscription, licenses, platform availability and product defectsServiceNow, under your own agreement with them
ERP, marketing, HR and other connected systemsTheir own owners and vendors
The service you engaged us for, and coordination across these boundariesUs
We cannot promise availability for systems we do not run. What we commit to is this: when a problem crosses a boundary, we keep hold of it until the owning party has it, and you always know where it stands.
Why Pulse & Patterns
Senior practitioners running your service
The people who would run your service are the people who design and deliver the work. Our founders bring 18+ and 20+ years in platform operations, support and governance, and on a recurring service that matters more than on a project: you are buying who picks up the phone in month fourteen.
Senior, and close to the work.
No account layer, no handover to a team you have never met.
We separate the four jobs.
Most of this market sells capacity. We would rather tell you which accountability you are actually missing.
Independence is contractual, not a slogan.
Our client contracts oblige us to document the recommended system of record and integration boundary, including where an existing system or another supplier's product is the better answer. On a recurring service, that matters more than usual.
Platform health, assessed first-hand.
We review live instances and find capabilities installed, active and fully current with nothing published for them to govern. Being active is not the same as being effective, and knowing the difference is what an ongoing service is for.
When you do not need any of this
Sometimes the answer is no
Small and stable
If your platform is small and stable and one internal administrator is coping, you do not need an ongoing service. If that administrator is the only person who knows how it works, enablement is the cheaper fix.
An ownership question
If the real question is who inside your organization should own, govern and improve the platform, start with Operating Model Design.
Something new
If you need a new solution, module or integration, that is implementation work. Solution Support covers changes to the solutions you already have, not new ones.
Volume and catalogs
If you need ticket capacity at volume, or your procurement process requires a published catalog with fixed response times, a larger support provider will fit you better. We would rather tell you that now.
A business change
If the business itself needs to change, rather than have what exists run well, that is a transformation conversation.
Related: Operating Model Design, for deciding who should own and govern the platform inside your organization. Implementation and ServiceNow product pages, for how solutions get built. Transformation Partner, for changing how the business works. Enablement, for building your own team's capability. Discovery and Roadmapping, if the ongoing question is really a planning question.
Start the conversation
Make the operating decision on purpose.
Tell us where you are: mid-project, coming out of hypercare, or unhappy with an arrangement you inherited. We will tell you which of these services you need, and which you do not.