Insights & updates from our experts

Another talented engineer has joined Xurrent’s Research & Development team. Based in the Netherlands, Bernard Vianen will work as DevOps Engineer and focus on keeping the Xurrent service available and performant on all infrastructures.

Bernard brings a wealth of knowledge and experience, having worked in software development and implementation for over 20 years. As an independent contractor, he worked for the infrastructure departments of small and large companies in various sectors, from finance to e-commerce. Like ABN AMRO Bank, ING, Equence, NN Group, A.S.R., Achmea, the Dutch tax office, and Blokker & Kramp. His main activities were workflow automation, the configuration of servers, installing web, J2ee, database, and messaging servers, and deploying software applications.
His specialty is releasing software from development to production environments (DTAP), and with his abstract and rational approach, he is well equipped to work in the most complex environments.
I look forward to exploring new ideas to keep improving the Xurrent enterprise service management platform. I am greatly impressed with its architecture and the people behind it. It will be inspiring to work together with Xurrent’s team of talented engineers to explore, create and implement even more innovative solutions for our customers and to increase productivity in the workplace.
Bernard Vianen – DevOps Engineer
The team looks forward to working together with Bernard to develop great things. Welcome, Bernard!

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.






.webp)





.webp)
.webp)














