We Brought Atlassian to Lagos. Twice.

Hosting, not selling. onpoint with our Atlassian colleagues and guests in Lagos — the people who build the product, in the same room as the people who have to run it.

There is a version of being a technology partner that involves reselling licences and answering support tickets. It is a perfectly respectable business. It is not the business we are in.

Over the past two years, onpoint has hosted members of the Atlassian team here in Lagos — Lesley Masibi and Stanley — not for a sales tour, but for something we think matters considerably more: putting the people who build the product in the same room as the people who have to run it, in this market, under these conditions.

We are an Atlassian Gold Partner. What that badge means to us in practice is an obligation. Our job is to consolidate the ideas, the innovation and the knowledge flowing through the global Atlassian ecosystem, and deliver the accumulated value of all of it to our clients here. Not a diluted version. The whole thing.

01 — The room

The boardroom at Black Diamond Hotel

The first time we hosted Atlassian, we convened an ITSM boardroom session at Black Diamond Hotel, Lagos — a deliberately small room filled with ITSM leaders and CIOs from across Nigerian industry.

We didn't run a product demo. We ran a conversation about unified service experience, and the questions underneath it that every organisation in that room was already wrestling with:

How do you actually maximise revenue when your service processes are fragmented across five systems that don't speak?

Where is the real cost hiding — and how much of it is being spent on manual reconciliation, repeat incidents, and work that falls between teams?

And how do you deliver a genuinely great experience to both audiences at once: the customers you serve, and the staff you expect to serve them?

That last one generated the most honest discussion of the day. Most organisations have invested seriously in customer experience while quietly tolerating an internal experience that frustrates their best people. Unifying service across the enterprise — IT, HR, facilities, finance, legal — is how that gap closes. It is also, not coincidentally, where the cost savings and the revenue protection live.

What made the session valuable wasn't the agenda. It was the candour. When CIOs are in a room with peers facing the same constraints, the conversation stops being aspirational and gets specific very quickly.

And it kept getting specific about one thing in particular.

“We went in to talk about unified service experience.We came out talking about data.”

The finding nobody put on the agenda

02 — The finding

The theme nobody scheduled: analytics

It surfaced early and it would not go away. Every CIO in that room, from a different industry with a different estate, circled back to the same frustration: they could not get the reports they needed out of the systems they already owned.

Not exotic reports. Fundamental ones.

1. Reporting that crosses team boundaries

Most organisations can tell you how one team performed. Very few can tell you how work moved between teams — where it queued, where it was handed off, where it silently died. That is precisely where the delay and the cost accumulate, and it was the view nobody had.

2. Cycle time for development teams

Engineering leaders were being asked to justify capacity, forecast delivery and defend investment largely on instinct. How long does work take from commit to production? Where does it stall? Without cycle time data, that conversation with the board is an argument, not an analysis.

3. Trustworthy data underneath both

This was the real anxiety. Several CIOs described spending more effort validating a number than acting on it. When leadership doesn't trust the report, the report doesn't get used — and the organisation reverts to deciding by seniority and memory.

What struck us is that almost none of this was a licensing gap. The capability was largely sitting in platforms these organisations had already bought. What was missing was the modelling, the configuration and the know-how to turn raw activity into a decision-grade view.

That is a solvable problem — and hearing the same version of it from CIO after CIO told us it was ours to solve.

Not a slide deck. Working sessions on live Atlassian capability — Confluence, Jira Service Management and Rovo — shown against the kind of connected project context most estates are still missing.

03 — The follow-through

Then we left the boardroom

An event is easy. Follow-through is the hard part, and it's the part we care about.

Across both visits, we took our Atlassian colleagues out to our clients — into their offices, in front of their teams, listening to their actual environments rather than a summarised version. Global product perspective, applied directly to a Nigerian organisation's real constraints, in the room, on the day.

We also ran a partner strategy session focused squarely on one question: what do our clients need from us that they aren't getting yet?

Analytics was one answer. The second came down to money.

On site, not on a call. Client visits across both trips — global product perspective applied directly to a Nigerian organisation's real estate and real constraints.

04 — The delivery

From conversation to capability

We moved analytics from a discussion topic into delivered work.

We ran training — bringing client teams up to the level where they could build, interpret and trust their own reporting, rather than depending on a partner every time the question changed. We would rather make a client self-sufficient than make them reliant on us. It's the more durable relationship, and it's the honest one.

And we went deeper with one of our leading enterprise clients, working alongside their teams to get real value out of their analytics: visibility across team boundaries, meaningful cycle time measurement for their development groups, and reporting their leadership could carry into a decision-making forum without a footnote of caveats.

The shift there wasn't really technical. It was cultural. When the data becomes reliable, the meetings change — debates about whose recollection is correct get replaced by conversations about what the numbers show and what to do next. Decisions get faster because the argument phase gets shorter.

That is what analytics is genuinely for. Not dashboards for their own sake. Better decisions, made sooner, with more confidence behind them.

05 — The commitment

Paying for licences in Naira

One of the clearest things we heard — from clients and prospects alike — was that foreign-currency licensing was a genuine barrier. Not a preference issue. A structural one, affecting budgeting, procurement cycles and forecasting for local firms.

So we changed it.

onpoint accepts Naira payments for Atlassian licences.

Procure, budget and plan in the currency you actually earn in.

Local organisations can now move without the FX friction that has quietly delayed or shrunk more than a few transformation programmes in this market.

We mention this not as a promotion but as evidence of how we work: our clients raised a constraint, we took it into a strategy session with our vendor partner, and we came back with a change to how we do business.

06 — The table

And yes — there was a lot of Nigerian food

We fed our guests properly. Repeatedly. It would have been rude not to.

We're only half joking about why that matters. Something happens over a shared table that does not happen across a video call. The conversations that shaped the Naira decision, and several of the client engagements that followed, started informally — after the formal agenda had closed and people were relaxed enough to say what they actually thought.

Partnership that only exists in a contract isn't partnership. Hospitality is not a soft detail here; it's how trust gets built in this market, and we're not going to apologise for being good at it.

07 — The standard

What this means if you're evaluating a partner

If your organisation is weighing up Atlassian — for ITSM, for enterprise service management, for delivery at scale — the question isn't really which partner can sell you the licence. Several can.

The question is which partner brings the global ecosystem to you, listens closely enough to hear what you actually need, and then does something about it:

• Builds the analytics capability you were missing — cross-team visibility and cycle time you can take to a board.

• Trains your people to own it — self-sufficiency over dependency.

• Changes its own commercial model when your constraints demand it.

That is the standard we hold ourselves to. Consolidate the ideas. Consolidate the innovation. Consolidate the knowledge. Deliver the cumulative value to the client — and stay accountable for the outcome.

We care about our clients' success. Hosting Atlassian in Lagos, twice, was one way of proving it. The analytics work and the Naira decision were the receipts. Ask the CIOs who were in that boardroom.

Want to be in the room for the next one?

Or you're simply tired of not being able to get a straight cross-team or cycle time report out of the tools you already pay for. Either way — let's have that conversation.