Retypd, Inc. — The AI company for the work between systems.

Talk to us
§ 00Retypd, Inc.

The AI company for the work between systems.

The enterprise,retyped.

Retypd takes on the copying, keying, checking and chasing that sits between enterprise systems — with computer agents that work under the same controls as your people, at a scale no team could match.

Talk to usHow we engage

Fig. 0 The Retypd mark, set in the work our agents do.

Agent log
  • 07:42:13CLAIMS INTAKECLAIM CLM-20931 FILEDPOLICY FNOL-4OK
  • 07:42:19PRIOR AUTHPRIOR AUTH SUBMITTED — PAYER 17/31POLICY PA-2OK
  • 07:42:26FREIGHT AUDITCARRIER INVOICE DISPUTED — €312POLICY FA-9OK
  • 07:42:31VENDOR MASTERBANK DETAIL CHANGEPOLICY VND-3HELD FOR APPROVAL
  • 07:42:38KYCKYC FILE REFRESHED — 4 DOCS VERIFIEDPOLICY KYC-11OK
  • 07:42:44BILLINGMETER EXCEPTION RESOLVED — REBILLTARIFF RULE T-7OK
  • 07:42:51ORDER MGMTORDER FALL-OUT REPAIRED — RESUBMITTEDPOLICY OM-6OK
  • 07:42:57ACCOUNTS PAYABLEINVOICE INV-48210 POSTED — 3-WAY MATCHPOLICY AP-12OK
§ 01The problem

Your most expensive integration is a person.

Every large organisation runs on systems that were never designed to talk to each other. The connective tissue is skilled people, retyping.

Every day, your best people copydecide, re-keyreview and chaseresolve — across applications that will never share an API.

  • Invoices keyed from PDFs into SAP, then checked by someone else.
  • Claims re-entered from email into Guidewire, one field at a time.
  • Patient details copied between Epic and a dozen payer portals.
  • Shipment records reconciled across carrier sites and the TMS.
Fig. 1.1A shared-services floor at 8:40 a.m. Most of these screens are open to copy from one another.
§ 02What Retypd does

Three commitments. One accountable firm.

  1. I

    We build the agents.

    One platform that reads your documents, operates your applications and runs the process end to end — across browser, desktop, Citrix and mainframe.

    The platform
  2. II

    We put them to work.

    Retypd engineers sit with your operators, map where the hours go and take agents into production — inside your controls, on your timetable.

    How we engage
  3. III

    We answer for every action.

    A tamper-evident record of what each agent did, why it was allowed and who approved it — written for your risk team, auditors and regulators.

    Security
§ 03The Retypd platformThe platform

Read it. Do it. Run it. Prove it.

Six components cover the whole of the work between systems — from the document that starts it to the evidence that closes it.

123Work layerExtract · Autofil · OrchestrateControl layerGovernance · InsightsConnection layerConnect → SAP · Epic · 3270
  1. 1Work layer — Extract · Autofil · Orchestrate
  2. 2Control layer — Governance · Insights
  3. 3Connection layer — Connect → SAP · Epic · 3270
Fig. 3.1 The Retypd platform, exploded. Actions flow down; evidence flows up.
§ 04Autofil — computer agentsInside Autofil

Show it once. It’s handled for good.

A process owner does the task once. Autofil turns the recording into a plain-language Playbook the business can read, sign and govern — then runs it at enterprise scale.

Recorded once · AP clerk, 63 seconds

00:00:02OPENOutlook › Invoices inbox
00:00:09READINV-48210.pdf · Halvorsen Freight AS
00:00:15SWITCHSAP GUI › MIRO
00:00:21TYPEVendor 100442
00:00:31TYPEReference HF-2291-08
00:00:38TYPEPO 4500018842
00:00:44CHECKGR 5000913 · qty 1 · ok
00:00:52TYPEAmount 48,210.00
00:00:57SAY“Over fifty thousand goes to the controller.”
00:01:03CLICKPost
Playbook · AP-12 · Invoice postingSigned off · v3
  1. 01Read each new invoice in the AP inbox and extract supplier, reference, PO and amount.
  2. 02Confirm the supplier and bank details match the vendor master.VND-3
  3. 03Three-way match against the purchase order and goods receipt.
  4. 04Key the invoice in SAP MIRO; read every field back before continuing.
  5. 05If the amount exceeds $50,000, prepare everything and hold for the controller.AP-12
  6. 06Post, attach the source document and seal the record in Retypd Governance.

Autonomy: Level 4 — within policy · Over-limit invoices held for approval

Any application
Browser, desktop, Citrix and 3270 green screens — no APIs or integration project required.
Readable by the business
Playbooks are written in plain language and signed by the people who own the process.
Autonomy earned in 5 levels
Every workflow starts in observe mode and is promoted only on evidence you define.
§ 05Where we startUse cases

Four places to start. One kind of problem.

We focus where errors are costly, evidence is mandatory and the work between systems is measured in hours, not minutes.

  1. 01BankingKYC, lending operations, payment exceptionsTemenos · FIS · Fiserv
  2. 02InsuranceFirst notice of loss, submissions, policy servicingGuidewire · Duck Creek · Sapiens
  3. 03HealthcarePrior authorisation, eligibility, denialsEpic · Oracle Health · athenahealth
  4. 04LogisticsFreight audit, customs, order entrySAP TM · Oracle OTM · CargoWise
§ 06Design partnersThe design partner programme

Six weeks to production. Then it compounds.

We work with a small number of design partners at a time. A Retypd team sits inside your operation from week one; the first agent is in supervised production by week six, and your people own it from there.

PhaseW1W2W3W4W5W6W7W8W9W10W11W12M6
Map the hoursShadow operators; baseline volume, time and error
Prove in observe modeAgent predicts; people work as usual
Supervised productionAgents run; irreversible steps held for approval
Hand over and expandYour team authors Playbooks; more work follows
§ —Next step

Bring us the work no one wants.

Name one process your people dread. In a single working session, our engineers will show you what agents would take on — and what they would refuse to touch without a person.

Talk to usHow we engage