András Ferencz

Ops Sprint · €3,500 · Accounting, legal, notary, real estate and insurance offices

Document intake: read, not retyped

IDs, invoices and contracts read into the office's register, and a person checks only what is unsure.

The moment

09:20

A new client brings an ID card, three supplier invoices and a rental contract. Each one will be typed into the register, field by field.

Typing it again...05:42to 06:00still typing

An accounting office with five people and a stack of paper every morning. The office is invented, like every name on this page.

The day

A Wednesday, before

09:20
  1. 09:20

    The stack

    Documents arrive as photos, scans and paper. Each one waits its turn on a desk.

  2. 10:05

    Field by field

    Name, ID number, address, dates, amounts. Typed by hand, read twice, still sometimes wrong.

  3. 11:40

    The typo

    One digit wrong in an IBAN. Found three weeks later, when the payment bounces.

  4. 15:15

    Where is it?

    The contract is somewhere in the shared folder, under a name only its author remembers.

  5. 18:00

    Still typing

    The afternoon's documents wait for tomorrow morning.

What a Wednesday like that costs

0

minutes

to type one document by hand

an ID card or an invoice with about 15 fields

0

seconds

for the same document read automatically

then a person checks only the unsure fields

0

hours a month

back for an office this size

about 100 documents a month × 6 minutes

Example figures for an office like this one. The audit measures yours.

The turn

What changes

Documents are read, not retyped. The fields land in the register, and a person looks only at the ones the system is unsure about.

1

Upload

A photo, a scan or a PDF, from email or the office's shared folder

2

Read

Each field is read, with a confidence mark

3

Check

Unsure fields are flagged for a person; the rest is ready

4

Register

The row lands in the register the office already uses

Try it

Try the intake

Pick a specimen document and watch it being read. Hover a field to see where it came from, and check the one the system is unsure about.

live demo, nothing is sent anywhere

Try this

  1. 1Read the specimen ID card
  2. 2Hover a field to see its source on the document
  3. 3Check the field marked for a person
Open full screen
How it gets built

How we build it

The audit, 2 hours

We count with you which documents come in, how many, and where they go.

The build, 3 weeks

Reading for your document types, writing into the register you already use.

Handover

Your team learns the checking screen on a real morning's stack.

The stack

A vision model on your own documents, kept private, writing into the register the office already uses. Documents never train a model.

The package

Live in 3 weeks

Ops Sprint

€3,500

  • A 2-hour operations audit
  • One automation live in 3 weeks
  • Handover and a short training

The packages on my studio's site

The other package

Ops System

€5,000

The 2-hour operations audit, Three automations working together, Team training, 30 days of support. Live in 5 to 6 weeks.

FAQ

Fair questions

What about handwriting and bad photos?

Unclear fields are flagged for a person instead of guessed. The audit tests your real documents before you decide.

Where do the documents go?

They stay in your storage, in the EU, under a written data processing agreement. They are not used to train any model.

Does it replace our software?

No. It fills in the register or program you already use, so nothing about your workflow changes except the typing.

Start with the 2-hour operations audit

We count your documents with you and leave a written map: what to automate, what it saves, what it costs.

The packages on my studio's site
More days to flip

Previous demo

Next demo

??????ask me again

Clinics, offices and any team with written procedures

Ask your business

Ops Sprint · €3,500See the day