Why we rebuilt it
For a long time, we ran our internal CRM and ERP on the Microsoft stack. Not because it was perfect, but because it met our requirements well enough for a long time. We filled the gaps with customizations and workarounds.
You either buy a standard solution and adapt your processes to it, or invest in custom development that consumes considerable time and budget.
That trade-off has fundamentally changed.
Agentic coding — AI-assisted software development in which AI actively contributes to development — makes it possible to build custom solutions much faster and more efficiently. Work that used to take months and require large development teams can now be delivered by small, focused teams.
We took advantage of that.
What we built
Together with our nearshore partner, we migrated our existing Power Apps solution to a custom-built application. Our focus was not only on speed, but also on quality, security and clear architecture governance.
We rebuilt our CRM and ERP interfaces and tailored them consistently to the way we work. The user interfaces are custom-designed, and the business logic follows our processes rather than the requirements of a standard platform.
We did not replace everything: our workflows still run through Power Automate, and identity management remains based on Microsoft Entra ID. Where existing platforms play to their strengths, we continue to use them deliberately.
Our data remains secure and GDPR-compliant. We have not changed that.
The result is a solution that feels as though it was made for us. Because it was.
What this means for our clients
This is not an internal experiment, but established practice. We are doing exactly what we recommend to our clients: regularly questioning technology decisions and consistently evaluating new possibilities.
Agentic coding fundamentally changes the economics of custom software development. Solutions that would have been too complex or expensive just a few years ago are now realistic options for many companies.
This does not mean the end of standard software. But the question “Build or buy?” needs to be asked again today.
We have made a start. And we are curious to see where this journey takes us next.