Insights & updates from our experts
The annual Xurrent Customer Advisory Board meeting took place last week at Hartwell House, nestled in the beautiful English countryside. For three days the Xurrent team was joined by 12 of our customers and partners to discuss service management best practices, the challenges facing modern enterprises, and Xurrent’s development priorities for the coming year.

It was fantastic to hear how customers gained ever-increasing value from Xurrent, fueled by our weekly releases. Equally, it was gratifying to hear a recurring theme from customers, both old and new, that what sets Xurrent apart is not only great technology helping solve problems other solutions struggle with, but also, the sense of a true Partnership (note the capital P) based on aligned goals and shared values.

As in previous years, attendees enjoyed interesting lodgings and fine food. To promote open discussions, the sessions were mixed up with activities that got the CAB members to compete in some fun traditional English games.

As the event drew to a close, the customers reviewed priorities and reached consensus to on the development focus for 2019. Some enhancements, like the Xurrent mobile app, dashboards and project portfolio management were already anticipated. But there were also some innovative ideas that got pushed to the top of the list. As these enhancements are introduced over the next 12 months, they will take the enterprise service management industry into exciting new territory.
Once more we close the annual CAB meeting having celebrated our collective successes and with a clear eye to the future!

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)














