Show
You start a screen recording and do the task once, the way you always do. No narration, no slowing down. The recording stays on your computer, and only the frames you review and approve are sent to Ada.
Module: Automations
Show Ada once how you do it. She takes it from there
You record your screen while doing your ordinary work: copying an order across systems, issuing a document, filling in data. Ada breaks the recording into steps, hands them back for your review, and runs the process from then on. She stops wherever the decision belongs to a person.
No scripting · no rebuilding your systems · learns from the work you already do
Three steps instead of an implementation project
There is no builder where you assemble a process from blocks. Your own work, recorded once, is the configuration.
Review
Ada returns the process as a list of steps in plain language. Each one shows where it came from and how confident she is. You rename fields, drop the steps you do not need, and mark the ones she must never run without asking.
Run
The process starts on your click, at a set time, or when a message arrives that triggers it. After every run you get a report: what was done, how long it took, and what needed a human decision.
Example: an order from the inbox into the sales system
Recorded once by an office administrator. From the second run onward, Ada does it.
Ada
An order came in from Kowalski Wholesale. I recognise this process, so I am creating the document in the sales panel.
Ada
I copied eight line items. On item four the product code does not match your price list, so I am leaving it for review rather than guessing.
Ada
Before I commit: order 2412/09, eight items, 4,380 PLN net, 14 day terms. Shall I confirm?
Administrator
Item four is code KL-220. Go ahead.
Ada
Saved. Document number 2412/09, confirmation sent to the customer. The whole run took two minutes.
messageline items copiedquestion on the unclear itemhuman approvalreport
Ada stopped twice: once on data she could not resolve, once before a write she could not undo. Everything else ran without asking.
How this differs from a click robot
Automation built on recorded clicks breaks the first time a screen layout changes. This works differently.
- It learns from a demonstration, not from a builder
- You do not assemble a scenario from blocks or describe it in a spreadsheet. You show it once and Ada does the rest of the work.
- The process is a readable list, not a black box
- Every step can be read, corrected and removed before the first run. You know exactly what Ada will do before she does anything.
- Official connections first, clicking second
- Where your system offers a programming interface, Ada uses it. That does not break when the vendor moves a button on screen.
- It stops instead of guessing
- A screen that looks different, a field that disappeared, data that does not add up: the run pauses and waits for a person, with a description of what it found.
Where Ada's independence ends
This is the part every finance team asks about, so we state it plainly.
- An irreversible step always waits for a click
- Sending, approving, deleting and paying require a person. Ada shows a card naming the operation and the exact amount, and it executes only after the click. No setting removes this.
- The catalogue of actions is closed
- Ada performs only the steps in your process. She does not execute code, does not open addresses read off someone else's page, and does not download files. Screen content is material for her, never an instruction.
- Credentials never pass through the model
- Ada works with the name of a field, not its value. Credentials to your systems are supplied by the execution layer and never reach the language model provider.
- Every run leaves a trail
- The report shows which steps ran, which were skipped and why, and who approved the operations that needed consent. Without that, no one can hand over work.
The recording stays with you
A screen recording of an office is the most sensitive material such a system can handle, so we built it not to hold that material at all.
The video file never reaches our servers
We cut the recording into individual frames inside your browser. You review them and decide which ones to send. The file itself stays on your disk.
Frames live as long as the analysis
Once the process has been broken into steps, the images are deleted. What remains is the list of steps, which is what you need, and nothing beyond it.
What is worth handing to Ada
It works for repetitive work that follows rules and happens on screen.
- Good fit
- Copying orders and invoices between systems, creating customer records, filling in data in a panel, issuing documents to a fixed template, pulling reports and circulating them to the team.
- Weaker fit
- Work where every other case looks different and calls for a conversation with the customer or a commercial judgement. Ada will do the mechanical part, but the decision still comes back to a person.
- Out of scope
- Online banking, payments, tax filings and social insurance systems. The cost of our mistake there is not comparable to any saving in time.
Questions that come up most often
How many recordings does Ada need to learn a process?
One pass is enough to produce a list of steps for review. For processes with several variants, you add a recording of each variant and Ada fills in the missing branches.
What happens when our vendor rebuilds the system?
A step that no longer matches pauses the run and comes back to you describing what Ada could not find. You fix that one step instead of recording the process again.
Do employees have to know their screen is being recorded?
Yes, and the module enforces it. Before we accept the first recording we ask you to state the legal basis and confirm that staff have been informed. Without that, the material cannot be uploaded.
Can Ada work in our accounting software installed on an office computer?
Yes. Processes in systems reachable through a browser run on our side, and those in software installed on a workstation are handled on that workstation.
Who is responsible if Ada enters something incorrectly?
That is why irreversible steps require human consent and why every run leaves a report. Responsibility stays where the decision is made, while Ada does the mechanical part and shows everything she did.
What does it cost?
Automations are an add-on to the Team plan. You pay up front for a package of runs and for recording analysis time. When the package runs out the process waits, or you buy another. Nothing is added to your invoice without your order.
Show us one process that eats your team's time
In the demo we take one of your tasks, record it together and show you what it looks like broken into steps. You leave with a concrete answer on how much of it Ada can take over.