One of the organisations we work with is a national NFP that came to us because they wanted to understand how to use AI to modernise their operations — but they had a lean IT team with limited AI experience and no one internally who'd navigated this before. We started with the governance foundations, then connected their CIO with a former peer who had delivered AI programs in a similar environment. That peer ended up presenting directly to their executive team. The reason they chose us over their existing global research provider — even though we were slightly more expensive — was that we could enable their whole team, not just the most senior person. Sometimes that's the difference that matters.

The CIO at one of Australia's major life insurers described his situation to me clearly: he knew where his organisation sat on data maturity and cloud readiness, but it was all instinct. He had no local data to back it up in board and executive conversations. He was partway through a major cloud migration and kept being asked: how do you know this was the right decision? He needed evidence that was specific to Australian organisations — not benchmarks built from companies in the US and Europe. We provided the A/NZ peer data he needed. He used it directly in board presentations, and it changed the quality of those conversations. He also used the membership to put three of his GMs on a development pathway — which is often as valuable as the benchmarks themselves.

A technology leader at a national law firm came to us with a familiar problem: her team had done significant transformation work over the past year, but there was no way to demonstrate it to non-technical business leaders. We benchmarked the function at the start of their transformation journey, then re-ran the same benchmarks twelve months later. The results showed clear, measurable progress across data maturity, modernisation, and AI readiness. When she presented the results to a newly appointed Chief AI Officer and the wider leadership team, the IT team received public recognition for work that had been invisible until that point. Her feedback: it wasn't just about justifying the spend. It genuinely lifted team morale. We also supported her on the AI governance questions her internal legal team was raising — turning what had been a blocking conversation into a productive one.

A government technology leader was asked to build a modern technology strategy for his organisation. He knew what he wanted to achieve — something genuinely forward-thinking, not constrained by the legacy thinking that often limits government IT. The challenge was knowing how to structure the approach and where to start. We matched him with an advisor who had specifically built and implemented strategies in regulated, resource-constrained environments — someone who understood the reality of limited budget and heavy governance, not just the theory of good strategy. One advisory session gave him a clear structure and enough direction to get started. The most valuable thing we did was find the right person for the problem — not the most senior advisor, but the most relevant one.

A CIO at a not-for-profit organisation came to us after a global research firm told their board they were overspending on IT and security. The board took it seriously and started questioning the investment. The problem was that the global benchmarks didn't reflect the organisation's actual risk profile or peer group. They work with highly vulnerable populations and hold sensitive data that a breach could genuinely endanger. We ran custom benchmarks against their specific peer sectors — Australian NFP and healthcare organisations — and the data told a different story. Their investment was appropriate for their risk context. The board approved a two-year program to reduce risk exposure. Local data made the difference. Global averages hadn't.

One of our healthcare clients uses five seats on their membership — and each of those five people is getting completely different support. One is working on AI governance and market direction with a data expert. One had lost her middle management layer and needed team coaching to bridge the gap. The Chief Medical Officer had built AI tools for clinical scheduling and came to us to check the governance. In that conversation, we identified that one of the tools was hosting patient data with a US company in a way that conflicted with Australian healthcare data legislation — an issue that would have been very costly to discover later. The Executive Director's instruction at the start was simple: "The best way you can support me is to support my team." That's the mandate we work to — and it's why the multi-seat model matters. One CIO with one licence doesn't build an organisation. Five leaders with five types of support does.

A technology leader at a major building company was about to take a new strategy to the board. Before submitting it, they wanted someone to review it — not to validate the direction, but to identify what could go wrong. We matched them with an advisor who had been CIO at one of Australia's largest property and construction companies. She reviewed the full strategy and identified several risk areas, including a significant change resistance issue related to long-tenured staff that would have derailed the implementation. They addressed those issues before the board saw the strategy. The version that went to the board was materially stronger — and the questions they got were about execution, not about whether the direction was right. Finding problems before you're committed to them is almost always cheaper than finding them during delivery.

One of the objections we hear most often is: "Our organisation is too unique for an advisory firm to really help us." I understand the instinct. But in my experience, what's unique is the context — the problems underneath are usually recognisable. The organisation I think of when I hear that is one of our government clients that manages a genuinely one-of-a-kind national infrastructure program. There is no direct comparator anywhere. But the challenges — managing large-scale change, communicating strategy to a complex stakeholder environment, building a team capable of executing something that's never been done — those exist everywhere. We matched each of their leaders with the closest relevant experience we had, even when that meant finding someone who had managed a 40,000-person merger and applying those lessons to a different context entirely. Their senior leader's feedback: "I feel like you guys really listen to us. You're not going, 'Here's what you need to do.' It's, 'Let's see how we can help you.'" That's the difference between a service that prescribes and one that adapts.

A large organisation rolling out Microsoft Copilot came to us with a common problem: the licences existed, but senior business leaders weren't using them, and the people meant to drive adoption internally didn't have the credibility or communication skills to make it stick. We helped in two ways. First, we ran a workshop with thirty of their internal digital champions — focused not on technology upskilling, but on personal brand, communication, and how to position themselves as credible subject matter experts within the organisation. In the weeks that followed, those thirty people visibly changed how they showed up and communicated. Second, we brought in one of our research analysts to deliver a live keynote on-site to launch a reverse mentoring program — pairing junior digital-savvy staff with senior leaders. The goal was to make sure everyone started from a shared baseline of understanding about AI before the mentoring began. When AI adoption stalls, it's usually not a technology problem. It's a communication and credibility problem.