Building client engineering capability

When I started working with Danske Spil, they relied on external engineering resources for the solutions we were building and did not yet have their own developers capable of taking ownership of those systems.

My responsibility extended beyond delivering the technology. I helped plan the engineering resources needed to deliver within the client's budget and deadlines, while also helping Danske Spil build the internal capability to eventually own the work themselves.

There were two goals that had to work together.

We needed to continue delivering projects successfully using engineers from our team, while helping Danske Spil reduce their long-term dependency on external specialists.

That meant thinking beyond the immediate project and asking: how do we deliver today while preparing the client's own engineers to take ownership tomorrow?

I worked with the client around budgets, deadlines and upcoming work to determine what engineering resources we needed from our side and how those resources should be allocated.

At the same time, as Danske Spil began bringing developers in-house, I personally trained and mentored them across the technologies, platforms and development practices we were using.

My goal wasn't simply knowledge transfer. It was capability building — helping their engineers develop enough technical understanding, confidence and ownership to make decisions independently.

In that sense, my role increasingly became one of enablement: removing knowledge dependencies rather than creating them. As their confidence grew, ownership could increasingly move from our team to theirs.

Over time, Danske Spil developed its own internal engineering capability and became increasingly able to develop and operate the systems independently.

That was a successful outcome even though it reduced their dependency on us as an external partner.

For me, that's an important part of technical consulting and leadership: success isn't creating dependency on your expertise. It's leaving people and teams more capable than when you arrived.

The project combined technical leadership with mentoring, resource planning, budget awareness and long-term knowledge transfer — with the goal of building capability, not just delivering software.