Insights & updates from our experts
As the number of customers using Xurrent continues to grow, more experts are needed to support Xurrent’s partner community. Today we are proud to announce that Fred Kouwenberg has decided to make the switch to Xurrent.

Xurrent makes enterprise service management so much easier. This does not only dramatically reduce the total cost of ownership of an organization’s service management solution, it also frees up a significant amount of time. Time that an organization can use to automate routine tasks, get a better handle on its external providers, and transition to a more dynamic sourcing approach to help speed up its digital transformation initiatives.
Fred Kouwenberg – Service Management Architect at Xurrent
After working with Peregrine, and then HP Service Manager, Fred started to introduce Europe to SaaS-based ITSM with ServiceNow in 2006. He did that together with Eelco Berghuis and he also worked with Frank Bakker, both of who already joined Xurrent earlier. Over the past few years in his role as CTO, Fred has also been working on the design of enterprise applications.
Fred joins Xurrent as Service Management Architect. Based in the Netherlands, he will work internationally supporting Xurrent partners on large enterprise engagements. All members of the Xurrent team, and especially Eelco and Frank, are excited to have such an acclaimed thought leader in their midst.

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)














