Insights & updates from our experts
The location of this year’s customer advisory board meeting was Barberstown Castle in Ireland. In this rustic setting, the achievements of 2016 were reviewed with Xurrent’s largest enterprise customers. These customers also shared some of the more interesting ways in which they are using Xurrent to benefit their business.

The development team was given a session to demonstrate the knowledge management functionality that will be released later this year. In addition, they provided an architectural overview of the all new infrastructure that is currently being prepared. Between the many sessions there were short fun activities to make sure that everyone was able to stay fresh and focussed.

Like at previous CAB meetings, the days were long. In the end, though, the customers concluded this meeting by setting a clear direction for 2017. The focus is going to be on productivity improvements. There are lots of clever ideas that we will be working on to make the service even more intuitive and effective, and to ensure that the specific needs of large multinationals are met. Apart from efficiency optimization, the other theme for 2017 will be portfolio & project management.

As these improvements are delivered, they will be announced right here at the Xurrent Blog. We are already looking forward to next year, when we shall scroll through the blog posts again to show you the new ways in which Xurrent delivers value to its enterprise customers.

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)














