What happened to Magium?

New start, new name.



Back in 2007 I started being self-employed providing services related to Microsoft Dynamics NAV (the predecessor of Business Central). Throughout the years I worked for partners, ISV’s and end-users in varying roles: from process analysis to programming, and from business consultancy to end-user support. I haven’t been bored for a single moment: there was always something to do. If there wasn’t a customer request, then there was always something new to explore. Especially the past few years.

change is chance


Then, why change?

The Microsoft Dynamics 365 ecosystem has been very busy catching up with many changes in recent years. Microsoft re-branded their Dynamics products a few years ago, for example: NAV changed to Business Central. The product has changed a lot too, both the user interface and underlying technology. The C/AL programming language changed to AL, and with that new development tools were introduced to the BC ecosystem, like: VSCode, Docker, GIT, DevOps, Powershell.

Also, the ecosystem changed. Microsoft made the base application open source. Their development team opened-up and listens much better to the feedback of the community, and often they react fast. What a difference compared to the ivory tower that Microsoft sometimes seemed to be 10-15 years ago! A lot of people that worked with Great Plains, switched to BC and have enriched the BC community. And not to forget appsource: Microsoft’s marketplace where users can download apps has changed the way that ERP software is sold and implemented. This gave me the opportunity to (finally) start building an app. An app with functionality to manage subscriptions, similar to solutions I have created for several end-users in previous years.

My work is still about creating solutions with BC, but how I do that has completely changed, since I got to know the ATDD (Acceptance Test Driven Development) methodology. @link to AT. To me this was a kind of game changer, something I should have done much earlier. In short: it provides a structure to develop software and improves the quality.

With all these changes going on, I found it time to update my company too. The name change reflects this refresh. That is why I changed to company name from Magium to Intelligo.

intellegere intelligo understand learn realize


So, why Intelligo?

With a company name I want something that symbolize what I do: analyzing, understanding, and connecting. And something that reflects my values: Quality, Integrity, Progress, Grinta* and Fun. For me, Intelligo just fits that.

Intelligo comes from the latin verb intellegere which comes from legere, ‘bring together, pick out, catch with the eye, read’, and inter-, ‘between, within’. Intelligo is the present active of intellegere and can be translated to: I understand, learn, realize.

My ambition is to have you understand your Business Central, to learn how to get the most out of it, and to realize how to empower your organization with Business Central.

It is often not about the answer at all, but about asking the right question.

Curious about what Intelligo can do for you?

* Grinta – Italian cycling term for guts, courage, determined, perseverance, character, and just that little extra.

Posted in

Meest recente nieuwsberichten

Test Automation and ATDD

What happened to Magium?