Show it once. It’s handled for good.
Autofil is Retypd’s computer agent for enterprise operations. It learns a task from a single demonstration, writes it down as a plain-language Playbook your process owners sign, and runs it across any application — under policy set in Retypd Governance, with evidence for every action.
| Learns from | One demonstration |
|---|---|
| Operates | Browser, desktop, Citrix, 3270 |
| Runs in | Your cloud or on-premises |
| First workflow | Supervised production by week 6 |
A recording becomes a Playbook. A Playbook becomes evidence.
Sixty-three seconds of an accounts-payable clerk’s screen, the procedure the business signs, and the record each run leaves behind.
A Recorded once · 63 seconds
| 00:00:02 | OPEN | Outlook › Invoices inbox |
| 00:00:09 | READ | INV-48210.pdf |
| 00:00:15 | SWITCH | SAP GUI › MIRO |
| 00:00:21 | TYPE | Vendor 100442 |
| 00:00:31 | TYPE | Reference HF-2291-08 |
| 00:00:38 | TYPE | PO 4500018842 |
| 00:00:44 | CHECK | GR 5000913 · ok |
| 00:00:52 | TYPE | Amount 48,210.00 |
| 00:00:57 | SAY | “Over 50k goes to the controller.” |
| 00:01:03 | CLICK | Post |
B Playbook AP-12 · signed off · v3
- 01Read each new invoice and extract supplier, reference, PO and amount.
- 02Confirm supplier and bank details against the vendor master.VND-3
- 03Three-way match against PO and goods receipt.
- 04Key the invoice in MIRO; read every field back.
- 05Above $50,000: prepare everything, hold for the controller.AP-12
- 06Post, attach the source, seal the record.
C Governance evidence · run #A-20418
| Field | Value | Source | |
|---|---|---|---|
| Vendor | 100442 | Extract · INV-48210 p1 | ✓ |
| Reference | HF-2291-08 | Extract · INV-48210 p1 | ✓ |
| PO | 4500018842 | Extract · INV-48210 p1 | ✓ |
| Amount | 48,210.00 | Extract · INV-48210 p2 | ✓ |
| G/L | 6100 | Model · conf. 0.98 | ✓ |
| Policy | AP-12 | Under limit · auto-post | ✓ |
Sealed 07:42:57 · hash 9f3a…c21e · screen replay attached
Fig. 02.1 One accounts-payable task as recorded (A), as signed (B) and as evidenced in Retypd Governance on every run (C).
Show. Govern. Run. Improve.
No process maps, no scripts and no integration project. The people who know the work teach it — once.
- 01Show
Learn the job by watching it done.
A process owner does the task once — or a few times, with the awkward variants. Autofil captures the screens, keystrokes and spoken reasoning, then writes a plain-language Playbook.
- Desktop recorder and browser extension
- Narration turns tacit rules into explicit ones
- Sensitive fields masked at capture
- 02Govern
Wrap it in the policy you already have.
Thresholds, approval rules, data boundaries and an autonomy level are set for every workflow in Retypd Governance — as policy, outside the model. Risk and compliance write the guardrails; Autofil cannot step outside them.
- Approvals in Teams, Slack or email
- Monetary, volume and time-of-day limits
- Segregation of duties per agent identity
- 03Run
Scale the queue, not the headcount.
Retypd Orchestrate hands agents their work from inboxes, folders, queues and APIs — with documents already read by Retypd Extract. Agents run around the clock and in parallel; every field is read back and verified before the next step.
- Parallel agents for month-end peaks
- Read-after-write verification on every field
- Exactly-once execution for irreversible steps
- 04Improve
Get better without getting riskier.
Every exception becomes a lesson. Autofil proposes Playbook changes, replays them against real cases and waits for sign-off in Retypd Governance before anything changes in production.
- Suggested fixes with evidence attached
- Drift detection when screens or data change
- Evidence-based promotion between autonomy levels
Watch an agent work. Then watch it stop.
The first invoice is posted end to end. The second exceeds the auto-post limit — so Autofil prepares everything, holds the irreversible step and asks the controller.
Autofil works the screens. The platform does the rest.
Retypd Extract reads the documents that start the work, Retypd Orchestrate runs the process around it, and Retypd Governance decides what Autofil may do — and keeps the evidence of what it did.
- Unstructured dataRetypd ExtractReads invoices, claims, emails and scans, and returns structured fields with a source for every value.
- Computer agents · this pageAutofilLearns a task from one demonstration and operates any application — browser, desktop, Citrix or green screen.
- Workflow engineRetypd OrchestrateRuns end-to-end processes across agents, APIs and people, with queues, service levels, retries and human tasks.
- Policy, approvals & evidenceRetypd GovernancePolicy-as-code, approvals and five levels of earned autonomy, with tamper-evident evidence for every action.
- Operations analyticsRetypd InsightsShows where the hours go, what agents returned and where exceptions cluster, measured against your own baseline.
- Connectors & credentialsRetypd ConnectPre-built connectors, event triggers and a credentials vault, so agents reach your systems without an integration project.
Built for the screens your people already use —SAP GUIOracle EBSSalesforceWorkdayServiceNowEpicGuidewireCitrix3270 terminalsAS/400
Five levels. Your hand on the dial.
Autonomy is set per workflow in Retypd Governance, earned with evidence and revocable in one action. It is the most important control on the platform — so it is also the simplest to read.
Level 1 of 5 · Shadow mode
Observe
Autofil watches the work, drafts the Playbook and predicts what it would have done. It touches nothing.
- Autofil
- Learns from demonstrations and live sessions; scores its own predictions.
- Your people
- Works exactly as today.
- Typical for
- Week one of every new workflow.
- Exposure
- None — read-only.
Level 2 of 5 · Co-pilot
Suggest
Every field is prepared and staged. A person reviews and presses the button.
- Autofil
- Gathers, keys and validates every field; explains each value.
- Your people
- Reviews and submits — usually in seconds.
- Typical for
- Regulated steps and high-judgement queues.
- Exposure
- Minimal — nothing commits without a person.
Level 3 of 5 · Checkpointed autopilot
Supervised
Autofil runs end to end and pauses for approval on anything irreversible — payments, submissions, deletions.
- Autofil
- Executes the full workflow; holds at policy checkpoints.
- Your people
- Approves at checkpoints and clears exceptions.
- Typical for
- The usual first stage in production.
- Exposure
- Bounded — irreversible actions are gated.
Level 4 of 5 · Within policy
Autonomous
Straight-through processing inside the limits you set. Anything novel, ambiguous or over threshold is escalated.
- Autofil
- Runs unattended; escalates on uncertainty, drift or limits.
- Your people
- Owns exceptions, thresholds and policy.
- Typical for
- Mature, high-volume workflows.
- Exposure
- Governed — continuous controls testing.
Level 5 of 5 · Agent fleet
Orchestrated
Agents hand work to each other across workflows — onboarding to invoicing to payment — under one control plane.
- Autofil
- Coordinates multi-step, multi-system processes.
- Your people
- Sets outcomes, audits samples, tunes policy.
- Typical for
- Shared-service centres at scale.
- Exposure
- Governed — with automatic demotion on drift.
Promotion is evidence-based: an agent moves up only after clearing the bar you set — for example, 500 consecutive runs at ≥ 99.5% field accuracy. Drift triggers automatic demotion.
What leaders ask first.
How is Autofil different from RPA?
RPA replays fixed coordinates and selectors; it breaks when anything moves and needs developers to maintain it. Autofil understands the intent of each step, reads unstructured inputs natively, adapts to interface changes with human sign-off, and runs under Retypd Governance — approvals, policy limits, evidence and autonomy levels — from day one.
Do we need APIs or an integration programme?
No. Autofil works through the same screens your people use, with its own least-privilege credentials. Where a good API exists, a Playbook can call it through Retypd Connect — but nothing waits for one.
What happens when Autofil isn’t sure?
It stops and asks. Low confidence, novel cases, policy limits and irreversible steps route to a human task in Retypd Orchestrate with the screen, the reason and a suggested resolution. Every decision a person makes is recorded and can become a Playbook improvement — after review.
Who builds and maintains the Playbooks?
Your process owners, by demonstration — with a Retypd team alongside for the first workflows (see how we engage). The aim is for your business teams to author and govern new Playbooks on their own.
Where does Autofil run?
In your own cloud account on AWS, Azure or Google Cloud, on-premises, or in a single-tenant environment we manage for you. Customer data is never used to train shared models. See Security for detail.
Bring us the workflow everyone avoids.
We will run Autofil against it in observe mode — on your screens, with your data — and show you the evidence before you commit to anything.