Five Modules. Six Months. One Bank That Stopped Guessing.

How onpoint rebuilt ITSM from the ground up for a leading Nigerian bank — and why the value is still compounding a year later

Every bank in West Africa runs on the same quiet contradiction. The business is real-time. The service management underneath it is not.

Incidents live in one system. Requests live in another. Change lives in a spreadsheet somebody owns and nobody trusts. Assets live in three places and agree in none. And when the board asks a simple question — how much did that outage actually cost us, and will it happen again? — the answer takes four days and three apologies to assemble.

That was the starting position for one of Nigeria's leading banks when they came to onpoint in February last year.

The real problem wasn't the tooling. It was the seams.

The bank didn't lack technology. It lacked connective tissue.

Their ITSM estate had grown the way most bank estates grow: process by process, department by department, each one solved locally and correctly, none of them solved together. The result was a set of well-run silos that could not see each other.

The symptoms were familiar to anyone who has run IT service delivery at scale:

Incident, request, problem, change and asset management operated as separate universes with no shared source of truth. There was no advanced CMDB linking configuration items to the services they supported, which meant no one could trace an incident back to the change that caused it, or forward to the customers it affected.

Data gaps meant analytics were assembled by hand rather than produced by the platform. Reporting was retrospective, fragmented and manual — a monthly archaeology exercise rather than a live instrument. And there was effectively no mobility: engineers, approvers and service owners were tethered to desks in a bank whose people had long since stopped working from only one place.

None of that is a tooling failure. It's an architecture failure. And architecture failures cannot be patched — they have to be designed out.

Why the bank chose onpoint

onpoint has spent years delivering ITSM and enterprise service management across Nigeria, Ghana and Malta, in exactly the environments where the margin for error is thinnest: regulated financial services, high transaction volumes, and audit regimes that don't accept "we think" as an answer.

The bank wasn't shopping for a licence reseller. They were looking for a partner who would argue with them in the discovery room and then be accountable for what got built.

"We had been sold platforms before. What we hadn't been sold was a design. onpoint came in and spent weeks refusing to build anything until we agreed on what the actual problem was." — Head of IT Service Delivery, the Bank

The Double Diamond: earning the right to build

onpoint ran intensive discovery using the Double Diamond framework — diverge to explore, converge to define, diverge again to ideate, converge again to deliver.

The first diamond was deliberately uncomfortable. onpoint's lead consultants sat with service desk agents, application owners, infrastructure teams, change managers, procurement, risk and business stakeholders — not to collect a wish list, but to separate the problems people said they had from the problems the evidence showed they had. Workshops mapped real ticket journeys end to end, exposed where work fell between teams, and traced the exact points where data stopped flowing.

What emerged was sharper — and smaller — than the original brief. A handful of root causes were generating the majority of the pain, and most of them converged on one thing: the absence of a service-aware CMDB.

The second diamond turned that definition into an architecture designed for scale — a target-state blueprint where a single, properly modelled CMDB sits at the centre and every process hangs off it. Incident knows what it broke. Change knows what it will touch. Problem knows what keeps recurring and why. Asset knows what the bank owns, where it sits and what it costs. Requests flow through defined catalogues with defined owners and defined SLAs.

Design first. Configuration second. That sequence is the entire difference between a platform that ages well and one that becomes next year's migration project.

Six months. Five modules. Live.

oughly six months after discovery began, the bank went live on five integrated modules, delivered in a phased rollout with the CMDB established as the backbone rather than an afterthought.

Not a pilot. Not a proof of concept. Production, in a Tier-1 banking environment, with the old silos retired.

"The go-live was the least dramatic day of the project. That's the compliment." — Engagement Lead, onpoint

What changed

Analytics stopped being a project. Reporting that once consumed days of manual consolidation is now produced by the platform itself. Leadership moved from reconstructing last month to steering this week.

Service management went mobile. Teams now raise, approve, action and close work from anywhere — branch, home, in transit. Approval bottlenecks that used to wait on someone being physically present simply dissolved.

Vendor and service agreement admin got automated. A set of mundane, repetitive processes around service vendor agreements — the kind of low-value work that quietly consumes senior people's calendars — was eliminated outright.

Problem management got teeth. Rich, well-structured problem records linked to configuration items and change history mean recurring failures are now diagnosed against evidence instead of memory. Fewer repeat incidents. Better root cause. Real institutional learning.

AI joined the resolution path. AI assistance in triage and ticket resolution has measurably improved response times, surfacing relevant knowledge and prior resolutions to agents at the moment of need rather than after the escalation.

ITSM became ESM. The platform expanded beyond IT — building on Jira Service Management to support cross-functional, collaborative service delivery across business units. The service management discipline IT spent years maturing is now available to the rest of the bank.

A year on, the curve is still going up

Here is the part that matters most to any bank evaluating a transformation partner.

Roughly a year after go-live, the bank is still extracting new value from the same investment. Not maintaining it. Growing it.

onpoint remains engaged — consulting, iterating, and implementing new capability, with a current focus on applying AI to compress service delivery speed further. Adoption widens. Automation deepens. The architecture holds because it was designed to.

Most ITSM programmes peak at go-live and decline from there. This one didn't, for one structural reason: the foundation was built to be extended, and the partnership didn't end at handover.

"We don't hand over a platform and disappear. We stay, we measure, and we keep implementing the best available answer as the technology moves." — Engagement Lead, onpoint

What other banks should take from this

If your ITSM estate feels familiar — processes that work individually and fail collectively, analytics assembled by hand, a CMDB that exists on paper, teams who can't work from anywhere, and an AI strategy with nowhere solid to stand — the lesson from this programme is straightforward.

You cannot automate your way out of a broken architecture. AI applied to fragmented data produces confident nonsense faster. The banks getting real returns from AI in service management are the ones who fixed the foundation first.

Discovery is not a delay. It is the deliverable. The weeks spent defining the right problem are what made six-month delivery possible at all.

The CMDB is not a module. It is the spine. Every downstream capability — problem, change, asset, analytics, AI — is only as good as the configuration model beneath it.

Choose a partner who stays. The value in this programme showed up in month six. It kept showing up in month eighteen because someone was still there designing for it.

Let's talk about your estate

onpoint delivers ITSM and enterprise service management transformation for financial institutions across Nigeria, Ghana and Malta — from discovery and architecture through implementation, adoption and continuous optimisation with AI.

If you're preparing for an ITSM transformation, replacing a platform that never delivered, or trying to work out where AI actually fits in your service delivery, we should have the discovery conversation.

Talk to onpoint. We work together, and we implement the best.