How a worry about an ageing parent led to EU MDR Class IIb conformity, and shaped the way we ship software for organisations that can’t afford to fail.
In early 2025, Johan Spännare’s father was diagnosed with dementia. The same question kept coming back: had his father taken his pills that morning?
It was a small problem against the diagnosis itself, but a solvable one. Johan has been writing software for twenty-five years, so he built a tool. A connected pill dispenser he could check from his phone, with logs he could audit later.
The build process was different. Johan let autonomous agents do most of the implementation work, including writing code and running tests, while he kept architecture, review, and the calls a person has to own.
Six months and dozens of releases later, the dispenser had reached EU MDR Class IIb conformity, with the technical documentation and traceability the classification requires. One engineer led the work. Most of the build was done by agents, inside a process Johan had put around them.
AI agents could already write code, but the process around them didn’t exist yet: intake, testing, compliance evidence as a by-product, and a person accountable for the judgment calls.
Johan brought Burhan in as a sounding board. They’d both spent years bringing continuous delivery into regulated Swedish enterprise, and Burhan kept using one word: factory. A codified line where autonomous workers produce the same quality of work every shift. Johan called the line Agentic Delivery and started building it for organisations where every release has to hold up to audit.
The accountability.
Burhan has built his career inside regulated Swedish insurance, where you can’t move fast without an audit trail. He works on how delivery is organised, and whether the capability stays in-house after an engagement ends. He can usually tell whether a delivery problem is in the tooling or in the team.
“AI can write code. Someone still has to own what ships.”
The craft.
Johan has spent his career shipping .NET into regulated Swedish enterprise. An Extreme Programming and Software Craftsmanship practitioner from well before either was fashionable, with a network engineer’s feel for where production fails. The person you want in the incident channel when nobody knows what broke.
“Most outages are obvious once you read the right log line.”
The network and the patience.
Thomas has built his career inside insurance technology. He started as an engineer on core insurance systems, then co-founded and ran a Nordic insurance-tech consultancy. He works at executive level, still reads source code, and these days writes it with autonomous agents.
“Patient capital. Operator network. A developer who still reads the code.”
If you’re running delivery into something regulated and high-stakes, we should talk.
info@agenticdelivery.se