Creatio, firsthand: a 2008 .NET app in no-code marketing clothes

I led the implementation of Creatio as a highly customized, widely integrated CRM at a wealth management firm as my parting project. Since Creatio is receiving mainstream press coverage, it's worth putting my firsthand experience on the record.

Creatio is a wrapper around a .NET application circa 2008. For anyone with development experience, that becomes obvious when the codebase peeks through. This is the platform being marketed as a modern, AI-powered, no-code solution.

The "no-code" promise is largely marketing:

🚩 Business users can configure UI and Business Processes... until their requirement hits a wall that only code can solve. That wall arrives surprisingly fast: date math, text manipulation

🚩 UI customization past that wall requires JavaScript. A bug doesn't just fail... it can freeze the page

🚩 Automation past that wall requires C# , a high bar for a business user, who will also need to understand package dependencies

🚩 Every time you save a Business Process or UI customization, the entire org recompiles. Every time.

🚩 Code lives inside Business Processes as unstructured scripts with no abstraction and no reusability, not as proper software

🚩 Developers who attempt to go beyond Business Process scripts quickly discover there is no documentation for Creatio's internal codebase, so writing anything meaningful requires reverse-engineering a black box and most give up

It is not enterprise-grade:

🚩 No bulk record processing, every record triggers its own Business Process individually

🚩 Business Processes have no built-in error handling. Non-technical users building automation are solely responsible for catching the errors junior developers typically make: null reference math, missing conditionals

🚩 Hanging processes — like those caused by a BP evaluating a null — stay hung until a user manually kills them

🚩 During data migration, BP errors produced 645,000 hanging processes and measurable server degradation

"Cloud platform" is misleading:

🚩 Each customer gets their own database, which has legitimate data isolation value in regulated industries, but shared cloud platforms have solved isolation more elegantly without the operational tradeoffs

🚩 The per-tenant database model creates real upgrade risk; what SaaS platforms resolve by rolling changes across shared infrastructure becomes a per-tenant deployment problem here

There are genuine strengths (just not outweighing the shortcomings above):

🔹 Some useful UI components I haven't seen in competing CRMs

🔹 Direct SQL access is genuinely powerful for enterprise implementations where developers are available, and goes beyond what most CRMs offer natively

Creatio markets themselves as enterprise-grade. They are not, and better options exist at every market segment they're targeting.