Projects / Business Process Compiler
Maptelo watches you do a task in the browser and builds a process model with a guide from it. Then a robot works through the spreadsheet row by row and checks every result with an independent read of the system, not the screen.
Narrated in Polish · English subtitles
Film chapters2:47
01
An office robot clicks “Save”, sees a green message and reports success — and a week later it turns out nothing was saved. Maptelo rests on one rule: the screen can lie, so the system itself decides the result.
You do the process as usual, in Edge or Chrome. Maptelo records the steps, the screens and which spreadsheet column each typed value came from. Passwords never reach the disk.
A few demonstrations become a process model: steps, inputs, rules and a way to check the result — plus a guide, a BPMN diagram and a report. Where the demonstrations differ, the program asks.
The robot works through the sheet row by row in the browser. Only a row confirmed by a read of the system is VERIFIED. It never types again what is already there.
In shadow mode the robot goes through the rows without saving, people do their work, and an independent read compares the two and shows every difference.
02
After every run Maptelo asks the system itself — through an API or the database, never the screen the robot clicked on. On the left is the run from the film: an AI agent asked for a price change, and Maptelo returned the result with its proof.
| Outcome | What it means | What next |
|---|---|---|
| VERIFIED | Done and confirmed by an independent read. The only success. | Finished. |
| HALTED_SAFE | Stopped before saving, nothing changed — for example a dry run. | Can run again once explained. |
| BUSINESS_EXCEPTION | A known business exception — for example, the product does not exist. | Goes into the report. |
| NEEDS_RECONCILIATION | An uncertain save: the screen says “OK”, but the read does not confirm it. | A person checks. The robot does not retry. |
| SYSTEM_FAILURE | A technical error before saving. | Safe to run again. |
| REJECTED | Bad inputs. The run never started. | Fix the inputs. |
| COMPLETED_UNVERIFIED | The steps passed, but the process has no way to check the result. Not a success. | Add a check. |
03
Robots usually break after an application update. I ran a process built on Odoo 17 after the upgrade to Odoo 18: screen addresses, column names and the very way of adding a price had changed. A table row had become a dialog window.
Maptelo found the moved screens and fields by itself: by the screens’ landmarks, and in harder places with help from a language model.
Where the way of saving itself had changed, it stopped without saving instead of guessing.
A repair reaches a new version of the model only after a VERIFIED run and a person’s approval.
0false VERIFIED
0bad writes
04
Studio is a page available only on the computer where Maptelo runs. It shows every process, its steps and its data, and a run on a sheet can be watched row by row, with a screenshot behind every result.
You record a demonstration and build a model from it with one button.
You answer the program’s questions where demonstrations differ.
You run the process on a sheet, and the results go back to its copy: a status and a note next to every row.
05
Maptelo is a program for the computer of the person who does the process, not a cloud service. Process data stays inside the company.
Recording, the model, the robot and the proof all run locally. You use it through Studio in the browser or through commands in a terminal.
in progressan app window of its own and a Windows installer
The robot works in Edge or Chrome, in a separate profile that remembers the company sign-in. You sign in yourself, once, in an ordinary browser window.
Recordings, models, results and screenshots are files on your disk. Private mode covers data in screenshots, and the model keeps no example values.
After screens change, Maptelo can ask a language model to help with a repair. Without it, runs are fully repeatable — and a read of the system always decides the result.
You can offer an approved process to an AI agent such as Claude, through MCP. The agent sees only the tool and a result with proof — never a password or a session.
Only for this page and for downloading the program. A team version, if there is one, will run on a server inside the company.
06
Tested on two versions of a real ERP, Odoo 17 and 18, and on a test application of my own — with test data only.
Automation is ready only when it can prove that it worked.
Next: a Windows installer and a pilot on a process at work — only with the IT department’s approval and a data-protection review. Why I built it, and what testing on a real system taught me: A robot that has to prove it worked.