Insights & updates from our experts

A product is only as good as the people who create and maintain it. That’s why Xurrent is excited to announce that Dennis Blommesteijn has joined Xurrent’s development team as Senior Software Engineer.

Dennis brings a wealth of knowledge and experience to our organization. As a software engineer and system architect, he has worked on a wide variety of systems and technologies for several service organizations. One of his strengths is bridging the gap between business development and software development.
Dennis is someone who constantly looks for new methods and technologies to improve processes and is always willing to transfer his knowledge to the other engineers in his team. These are personality traits that are much appreciated in the Xurrent organization.
What impressed me the most, when I learned about Xurrent, is how well the organization is structured. The quality of their code-base and automated tests is impressive. It explains why they are still able to deliver multiple new features every week, even though the solution is already so mature. This makes for an exciting environment to work, because it allows me to build new capabilities that customers will actually use shortly thereafter.
Dennis Blommesteijn – Senior Software Engineer
Working from the Netherlands, Dennis will feel right at home in the development team that already includes several other Dutchmen like Mathijs Sterk, Robbert Brak, Robin Roestenburg and Fried Hoeben. All his colleagues are eager to support him as he starts to work on the first enhancement that he will add to the Xurrent service.

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)














