Almost every organisation has them: process descriptions. Created during a project in which consultants spent weeks on interviews and workshops, neatly drawn in Visio or a process tool, carefully recorded in a handbook.
And then day-to-day practice changed. One step turned out to be unnecessary, a department started doing things slightly differently, a new system was added. Nobody updated the drawing, because the drawing didn't do anything anyway. Two years later the handbook is a historical document and everyone is back to doing things their own way.
That is the fundamental problem with traditional process management: the description and the execution are two different things. As long as that is the case, the description will always lag behind.
Creatio comes from a different tradition. The platform started life as a BPM system (for years it was called bpm'online), and its starting point is that the process you draw is the same process that runs. Change the drawing and the execution changes with it. That sounds like a detail, but it is the most important difference there is.
Business Process Management is not software but a way of working: you record how the work is done, you carry it out according to that agreement, you measure what happens, and you improve based on what you see. A BPM system is the tool for doing that.
The distinction that matters in practice is the one between two types of work.
These run in a similar way every time: a quote request, a credit approval, an onboarding programme, a purchase request. You know the steps, the order and the decision rules. You capture them in a process model that the system executes.
This has a goal but no fixed path: a complex customer query, a claims file, a tender, a complaint. You know which steps are possible and which stage you are in, but the order depends on the situation.
Many systems can only handle the first kind. That is where it starts to chafe, because half your work doesn't fit in a straight line.
A few types of process where a BPM platform clearly delivers more than workflows in a CRM:
Our approval process ran through email and Excel. In Creatio it is now fixed, with a clear owner for each step and a lead time we can finally measure.
What makes this topic confusing is that four different things look alike. The distinction:
| What for | Works on | |
|---|---|---|
| Workflows in your CRM or ERP | Automation within a single application | That system's data |
| Creatio BPM | Processes across departments and systems, with decision points and approvals | The process as a whole |
| RPA | Actions in systems without a usable API | The screen |
| AI agents | Steps that require interpretation or judgement | Meaning and context |
These four don't compete, they complement each other. A well-designed process in Creatio can call an API integration for one step, an RPA bot for a system without an API, and an AI agent to assess an incoming document.
What Creatio is explicitly not: an ERP. General ledger, stock valuation, VAT returns and annual accounts belong in your financial system. Creatio orchestrates the process and makes sure the right data ends up in the right place. Being honest about that saves disappointment later.
Not because of the software. Because of five things we see again and again in practice.
The process description in the handbook is rarely the real process. Automate the theory and you build something nobody uses.
The organisation's primary process is the most tempting and the worst place to start. Begin with something well-defined, with a clear pain point and a visible result.
A process with eighty steps is not a process but a manual. Model at the level you manage at, and leave craftsmanship to the craftspeople.
In professional services the exception is often thirty percent of cases. A process that only knows the main route forces people to work around it.
A process without an owner who is allowed and able to change it grinds to a halt within a year. Then you have your old problem back, only more expensive.
With the people who carry it out. This is often where it turns out that some of the steps no longer serve a purpose. You can also book a separate process mapping workshop with us for this, with no obligation to implement anything afterwards.
That determines whether you design a BPMN process or a case, and getting that choice wrong costs you the whole project.
Not at the level of individual actions.
Before we start on the next one.
Lead time, exception routes, where files get stuck.
Your team needs to be able to change processes themselves: that is the whole reason for choosing no-code.
The value of process management does not lie in the moment you capture the process. It lies in the months and years after that, in which reality changes and your process model either moves with it or doesn't.
That is why the platform matters. A process description in a document is out of date from day one. An executable process in Creatio that your team can change themselves stays accurate, because changing it is easier than working around it.
Workflows in a CRM automate actions within that one system: creating a task, sending an email, updating a field. BPM is about the process as a whole, across departments and systems, with decision points, approvals, parallel paths, exceptions and lead time monitoring. If your automation stays within one application, workflows are enough. If your processes pass through several departments and systems, you need a process engine.
BPMN 2.0 is the international standard for notating business processes. It matters for two reasons: your models can be read by anyone who knows the notation, including auditors and new employees, and you can exchange diagrams with other BPM systems instead of being stuck with a proprietary format. In Creatio these models are also executable: the diagram is the working logic, not a drawing that someone then has to rebuild.
Case management is meant for work that has a goal but no fixed path: claims files, complex customer queries, tenders, objection procedures. You define stages and the steps that can occur within them, and the system suggests the logical next step without enforcing it. You need it as soon as your staff must keep professional freedom while the organisation still wants to know where a file stands.
Yourselves, and that is the whole idea. The process designer is no-code and intended for people from the business. We set things up, train your people and hand over. For complex integrations or a major redesign you bring us back in, but day-to-day adjustments to a step, a rule or an approval should sit with your own team. Otherwise no-code loses its main advantage.
No. Creatio is a CRM and process platform built on no-code and AI, not an accounting system. General ledger, stock valuation, VAT returns and annual accounts stay in your ERP or accounting package. Creatio orchestrates the process across your systems and makes sure data ends up in the right place. In organisations where the complexity lies mainly in commercial and service processes rather than logistics, Creatio can become the operational heart, with a lighter financial package alongside it.
With one well-defined process that has a clear pain point and a visible result, not with your primary process. Good candidates are quote approval, customer acceptance, onboarding new customers, purchase requests or complaint handling. First map that process as it really runs, including the exceptions nobody has written down.
For a well-defined process with a limited number of integrations, a few weeks is realistic, most of which goes into analysis and design. A full process architecture with several processes, integrations and its own data model is built up in phases over months. The fact that you can then adjust things yourself also makes the first version less nerve-racking: it doesn't have to be perfect.
By deciding in advance what you will measure. Lead time from request to completion, the percentage of files completed without intervention, the number of steps in the process, and how often the exception route is chosen. Creatio logs every process run, so those figures are available from day one. That turns process improvement from an exchange of opinions into a conversation about facts.
Mobile XL is a Creatio partner and always starts with your processes, not with the software.
