A solo Master-Architect practice. Twelve years on platform, thirteen ServiceNow certifications, no juniors learning on your instance. Built fast, shipped clean, designed to last.
Most engagements start with one of these. Each routes to the engagement that fits.
New to ServiceNow and we want to do this properly the first time. Set the foundations, draw the lines.
Architecture & Advisory →Took over an instance built by someone else. We need to know what's worth keeping and what to redraw.
Architecture review & remediation →In flight on a multi-stream programme. We need senior architecture overlaying it before scope drifts.
Programme Architecture →The work doesn't match a Now product. We need a custom app built properly on the platform, not bolted on.
Custom Application Development →Most ServiceNow estates aren't undone by bad architecture. They're undone by trying to design every detail upfront, missing the moment when shipping would have taught more than another workshop.
Senior architecture is knowing which decisions need to be perfect and which need to be made and moved on from. CSDM, integration patterns, governance: these are the few lines that should not move. Almost everything else benefits from being shipped, used, and revised in the open.
That's why direct engagement matters. One Master Architect with twelve years of pattern recognition can tell when a decision needs another hour and when it needs to ship. That call is the work.
Indecision is expensive. So is shipping work that compromises on rigour. The job is to do both: get something working to a senior standard, get it in front of real users early, and iterate on what they actually do with it. Architecture that never reaches production is theory. Production work without architecture is debt.
ServiceNow's catalogue is wide, but it isn't infinite, and the licensing maths doesn't work for every workflow. Forcing an awkward OOTB module into work it wasn't designed for creates more debt than a well-scoped custom app on the same platform. Sometimes you need to build for yourself to make it worthwhile.
Thirteen ServiceNow certifications give you a solid foundation, and they're a credible signal to clients. They are not the same as expertise. Expertise is the experience and pattern recognition you only get from a decade of seeing what works and what doesn't on real estates with real users.
Used as an accelerator on live build, AI is genuinely transformative. Used as a marketing label, it's just noise. Agentic workflows, Now Assist and tools like Claude Code can deliver real outcomes faster, but only when you know what you're doing and treat the AI like a capable junior, not an oracle.
A pure-play ServiceNow practice. Each engagement is led, designed and delivered personally, with no juniors, no handoffs, no escalation chain.
Platform strategy, CSDM design, integration patterns, governance models, and architectural reviews of in-flight or inherited estates.
Agentic workflows, Now Assist enablement, and AI tooling, Claude Code, MCP, agent orchestration, applied to live build as method, not marketing.
Master-Architect-level oversight on multi-module, multi-stream ServiceNow programmes, holding the whole, so the parts cohere.
Where the standard estate's modules don't fit, a well-scoped custom Now Platform app usually beats another point solution, with lower five-year TCO.
Anonymised by convention. Available on request, where a non-disclosure permits.
Tell me about the platform. I'll respond personally.
