How an Insurance Company Uses AI to Save 400 Hours a Month - Full Interview


The Applicable Bytes

Career & Growth, Technical leadership & AI for developers

A few minutes into my conversation with Anders Dræge, I realized something slightly embarrassing.

He has won awards for his AI work.

The last award I remember winning was for school electronics, somewhere around eighth grade.

And the difference between us isn’t the technology.

Anders leads AI development at Frende Insurance in Norway. His AI systems run in production, and together they save over 400 human hours a month.

When he talks about a project, he talks in numbers

When I talk about mine projects, I talk about what I built. How cool tech is, how happy we are. Then I finish it, and I start the next one. I’ve never been meticulous enough to take a project from start to finish and present it properly.

So I asked him the question I should have been asking myself: how do you actually measure an AI project?

His answer was almost disappointingly simple.

  • Ask the people who do the task today how long it takes, once. Minutes, sometimes seconds.
  • Count how many times the process runs.
  • Multiply.

That’s the whole method. He borrowed it from the company’s robotic process automation team (RPA: software robots that click through the steps a person would), who have counted saved hours that way since 2014.

Some tasks are tiny but happen thousands of times. Others are slow because a person has to dig through several systems to find one answer. Both add up, and both end as one number a leader understands: hours per month.

It took me straight back to a meeting from my consulting years.

We were building email classification for an insurance client, and we told leadership it would be hard to get the AI to 100%. We were aiming for around 90.

One of the senior people almost jumped out of his chair. “If you get it to 90%, ship it today. Our manual workflow is at about 65.”

I was thinking like an engineer, in binaries: code is either right or wrong.

He was thinking like the person who runs the operation.

The baseline was never 100%.

The baseline was his team, on a normal day.

I’ll admit I’ve been on the other side of this too. As a consultant, I’ve sat in the board meetings where AI was going to fix everything, tomorrow. Guilty.

Both mistakes come from the same place: we compare AI to a promise, when we should compare it to how the work gets done today.

Here’s the uncomfortable part: Anders’ closing advice wasn’t about AI at all.

Think value creation, he said, and then be able to communicate it. When leaders see that a system saved them a number of hours every single month, AI stops being an interesting experiment and becomes a priority.

That one landed, because communicating the value is exactly the step I skip.

If you can’t show the hours, even your best AI project looks like a hobby.

Hours are the easy part to count, though. The harder call is which initiatives deserve the hours in the first place. Anders also lets AI make some decisions entirely on its own, which goes against most of the advice you’ll read on LinkedIn, so I asked him why.

That’s where the full conversation goes next.

You can watch the full conversation here:

Postboks 60, Bergen, Vestlandet 5821
​Unsubscribe · Preferences​

Dalibor Jovic

I help lonely developers, technical and AI leaders with their career and with AI adoption. Once every few weeks I send an email about AI adoption, good coding practices and personal development.

Read more from Dalibor Jovic

The Applicable Bytes Career & Growth, Technical leadership & AI for developers You can have 100 projects of five years of experience in one company, and still not be senior. Because repetition is not the same as growth. That sounds obvious when you read it. It was not obvious when I lived it. After five years of programming, I looked strong, on paper: around 100 projects, a team lead title, and forum administrator credibility from the old PHP days. Those things helped me get my foot in the...

The Applicable Bytes Career & Growth, Technical leadership & AI for developers 20 years have passed since I got paid to code for the first time. Here are few things I’ve learned along the way. Most programmers think a career grows with time. Get a job. Complete projects. Stay long enough. Become senior. I did that. I worked on around 100 projects, became a team lead, moved to Norway, and arrived confident that my experience would open every door. Then I discovered I was a junior developer...

The Applicable Bytes Career & Growth, Technical leadership & AI for developers In this email I reflect on my recent interview with another fellow "Director of AI", Courtney Kingsbury, and we talk about common problems, fears and challenges that adoption of AI brings in two different companies. You might be the only person at your company who gets AI, then you already know the quiet weight that comes with it. Nobody above you understands what you actually do, nobody beside you can check your...