Work · 05 · Processes
Every step
visible to the business, not only to developers
Changes to a BPM system without the chaos
8steps from request to closing
5modules: contracts, counterparties, correspondence, powers of attorney, bonds
Not connectedtest environment
28.10.2026one limited change accepted on the copy
The path of a request.
- 1 · personRequest
- 2 · AI + operatorAnalysis: reads the live system, changes nothing
- 3 · personTwo decisions: “taken into work” and “specification fixed”
- 4 · AI agentDevelopment on a copy
- 5 · AI, then a personAcceptance on the copy: an independent AI runs the scenarios, a person once
- 6 · AITransfer to test
- 7Release to the live system
- 8 · personClosed after the customer confirms
What counts as acceptance.
- ✓ The whole affected business path is checked, not only the changed piece
- ✓ Real buttons are pressed
- ✓ After publishing, the result is read back again
- ✓ “The server answered 200”, “it compiled”, “the import finished” are not acceptance
What the tool does not do.
- It never writes to the live system: it only reads and compares
Not yet.
- The test environment is not connected yet
- No package has reached the live system yet
AI reviews every change request, development happens on a test environment, and the analyst and product owner accept the result before it reaches the live system.
Next piece of work: A check: is your ERP ready for AI?