Insights & updates from our experts

At a time when our business is growing faster than ever, Xurrent is thrilled to welcome Paul Lubik who joins the team as Service Management Architect. He is based in Melbourne, Australia and is already assisting partners and customers to achieve positive outcomes during and post implementation of their Xurrent environments.
Paul is an experienced IT professional with demonstrated performance in service delivery, project management and process improvement. He is known for his ability to create positive, high-performance workplace cultures and has extensive experience in building relationships with cross-functional teams, vendors and most importantly end users and customers.
With his experience, both as an end user and ITSM customer, he has a thorough understanding of what organizations need from their service management toolset, which will be a real asset to Xurrent and our customers. In past engagements, Paul has worked with tools like ManageEngine, HEAT, and ServiceNow, which will benefit customers as they plan their migration to Xurrent.
I’m excited to join Xurrent at this time of growth and am looking forward to leverage my service management experience in a company committed to positive customer service outcomes and product experience. I am convinced that Xurrent’s innovative and user-friendly solution for better service management is exactly what organizations are looking for these days, to eliminate unnecessary complexity. My ambition is to help the Xurrent team grow the Australia Pacific region in terms of product uptake and customer success.
Paul Lubik – Service Management Architect
Although Paul will initially be working mostly with this Australian colleagues Stefan Hulls and Laurens Pit, the entire Xurrent organizations is delighted to have another service management superstar on board. Welcome to the team Paul!

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

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)












