Record the workflow once
The person who does the job clicks through it as usual.
The platform
Record & run.
Show the work once. The platform runs it across every system you own.
Answer the agent's questions
Edge cases get settled in plain language, not in a ticket.
Run it on every case after
Deterministic code, run on schedule or on trigger, fully logged.
How it works
From one recording to a workflow that runs itself.
Record the workflow
Start the recorder and do the job. Binomio captures every click, field, file and system boundary, including browser tabs, desktop apps, spreadsheets and the internal tool with no API, as an ordered list of steps rather than a video.
- Open unpaid queue in billing portal
- Filter status = exception, age > 7 days
- Copy invoice id and vendor reference
- Look up purchase order in the ERP
- Match totals, then release or flag
Captured
2 systems14 fields1 decision point0 integrationsAnswer the agent's questions
One recording shows the normal path. The agent reads it, finds the gaps, and asks about them in plain language: what to do when a field is empty, which approval threshold applies, and when a human should take over. Each answer becomes a branch in the code.
Question 2 of 5
The purchase order is missing from the ERP. What do you do?
Written in the operator's words, not a rules engine.Becomes
if (!po) {
queue("ap_exceptions", {
invoice_id, vendor_ref
});
return halt("missing_po");
}Reviewable, versioned, and the same on run 1 and run 10,000.
Run the automation
The workflow runs on a schedule, on a trigger, or on demand. Every run writes a trace: inputs, each step, each decision, the branch taken. Anything outside the answers you gave stops and routes to the right human queue with the full trace attached.
| Run | Workflow | Steps | Duration | State |
|---|---|---|---|---|
| r-48210 | Invoice exception handling | 42 | 3.4s | Closed |
| r-48211 | Invoice exception handling | 42 | 3.1s | Closed |
| r-48212 | Invoice exception handling: missing PO | 17 | 1.2s | Escalated |
| r-48213 | Invoice exception handling | 42 | 3.6s | Closed |
Execution model
AI writes the code. Code does the work.
A model is the right tool for turning a recording into a program. It is the wrong tool for running that program eleven thousand times a day. So Binomio uses the model once, at build time, and ships code to production.
Same workflow, same 42 steps, same data: once as generated code, once executed step-by-step by a token-priced agent loop. Cost measured per 1,000 runs, wall-clock measured end to end. Method and raw numbers available on request.
Generation, not execution
The model reads the recording and your answers, then writes and tests the automation. At runtime it is not in the loop.
Same input, same output, every time
Code is deterministic. A run you approved in testing behaves identically in production, with no re-planning, no drift between runs and no prompt to babysit.
No per-token cost at runtime
Inference is a one-time build cost, not a line item on every case. That is where the cost gap comes from, and why the gap widens as volume grows.
Auditable as source
You can read the automation, diff a version, and point at the line that made a decision.
SOP generation
The recording writes the SOP.
Every recording produces a written procedure: numbered steps, the systems touched, the fields used, the decisions and their conditions. It reads like the document your team was supposed to keep and never had time to write.
Export it anywhere
Markdown, PDF, or structured JSON. Put it in your wiki, your LMS, your onboarding pack, or your auditor's evidence folder.
Stay in sync
When the automation changes, the SOP changes with it, versioned side by side. The document and the behaviour cannot drift apart.
Run it on another platform
The JSON export is a complete, machine-readable procedure. Hand it to another AI platform or your own agents. Nothing about the recording is locked in here.
Invoice exception handling
- Open the unpaid queue and filter to exceptions older than seven days.
- For each invoice, record the invoice id and vendor reference.
- Locate the purchase order in the ERP by vendor reference.
- If the totals match within tolerance, release the invoice for payment.
- If no purchase order exists, flag to the AP queue with the vendor reference.
SOP to automation
The person who does the job is the person who automates it.
An approved SOP promotes straight into a running automation. There is no handoff to a developer, no backlog and no translation layer where the detail gets lost. The operator who knows the exceptions is the one who approves them.
What you actually did
Captured once, by the operator, in the tools they already use.
What should happen
Reviewed and approved in plain language by the team that owns the work.
How it runs
Written from the approved SOP, tested against past cases, versioned.
Who owns it
The operator edits the SOP; the automation follows on the next version.
Workflow library
One place to see every automation and what it depends on.
Manager view across all workflows
Owner, volume, hours saved, escalation rate and last change, per workflow and per team.
Dependency graph
See which systems and which upstream workflows a change will touch before you approve it.
SOP export
Export one procedure or the whole library, with version history attached.
Full automation library
Everything the company has recorded is searchable, so the second team to hit a process reuses the first team's work.
Dependencies: accounts payable
Illustrative library view. Supply real screenshot.
billing portalInvoice exception handlingv4 · owner: AP ops
ERPVendor onboarding checksv2 · depends on ERP
vendor mailMonth-end reconciliationv7 · depends on 2 workflows
| Workflow | Runs / wk | Hrs saved |
|---|---|---|
| Invoice exception handling | 1,420 | 96 |
| Vendor onboarding checks | 180 | 24 |
| Month-end reconciliation | 40 | 61 |
Agent deployment
Our team deploys the first ones with you.
Self-serve recording works from day one. For the first wave and for processes that touch systems without APIs, a Binomio deployment team works alongside your operators until the workflows run unattended.
Workflow discovery workshop
Pick the processes where hours saved are largest and the rules are clearest.
Recording sessions with the team
Sit with the operators while they record, so the first capture is the right one.
Agent build and QA
Generated code reviewed and replayed against historical cases before it goes live.
Policy and guardrail setup
Approval thresholds, halt conditions and the human queues escalations land in.
Integration work
Systems with no API are included. The recording is the interface.
Monitoring and on-call for runs
Failed and escalated runs watched with your team during ramp-up.
Quarterly savings review
Hours saved reconciled against the baseline measured at recording time.
Training internal champions
By the second wave your own operators record and ship without us.
Pricing
Priced on results. You pay per hour saved.
No seat licences, no per-run fee, no bill for a workflow that never shipped. If a workflow gives back nothing, it costs nothing.
The recording is the baseline
Recording the workflow captures how long the work takes a person, step by step. That time is the measured baseline, not an estimate.
Every run counts once
Each completed run banks that baseline time. A thousand runs of a six-minute task is a hundred hours of work returned to the team.
You pay on hours saved
One rate per hour saved, reconciled every quarter against the run log. Escalated runs are not counted as saved.
Contact us
Bring one process. We will record it with you and show the hours it gives back.