Accounting, legal, notary, real estate and insurance offices

Bye-bye,the paper stack.

IDs, invoices and contracts land in your register already read. You check only the fields it’s unsure of.

  • Accounting and legal offices
  • Live in 3 weeks
  • Writes into your register
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.

Wednesday, 09:20: a stack, or a register?

Drag the handle

The same Wednesday, after

EXTRACTEDNumberDateTotalSuppliercheck
  1. 09:20Read on arrivalEach document is read as it arrives, photo or scan.
  2. 10:05Ready in secondsName, ID number, dates and amounts land in the register with a confidence mark.
  3. 11:40The unsure fieldThe system flags the IBAN it is not sure about. A person checks one field, not fifteen.
  4. 15:15Found by what it isEvery document is filed by client, type and date. Finding it is a search.
  5. 18:00Done todayThe afternoon's documents are in the register before closing.

A Wednesday, before

Typing it again...05:42to 06:00still typing
  1. 09:20The stackDocuments arrive as photos, scans and paper. Each one waits its turn on a desk.
  2. 10:05Field by fieldName, ID number, address, dates, amounts. Typed by hand, read twice, still sometimes wrong.
  3. 11:40The typoOne digit wrong in an IBAN. Found three weeks later, when the payment bounces.
  4. 15:15Where is it?The contract is somewhere in the shared folder, under a name only its author remembers.
  5. 18:00Still typingThe afternoon's documents wait for tomorrow morning.
BeforeAfter

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

Wednesday’s typing, itemised (example numbers)

The bad day · receipt

  • to type one document by hand6
    an ID card or an invoice with about 15 fieldsminutes
  • for the same document read automatically20
    then a person checks only the unsure fieldsseconds
  • back for an office this size10
    about 100 documents a month × 6 minuteshours a month

The first line, a month300 lei

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

What changes

Read on arrival. A person checks the doubtful fields.

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. 1Upload
  2. 2Read
  3. 3Check
  4. 4Register
  1. 1

    Upload

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

  2. 2

    Read

    Each field is read, with a confidence mark

  3. 3

    Check

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

  4. 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
An honest comparison

Typing, a data-entry hire, or this

  • Cost to startTyping it yourselves:NothingHire a data-entry person:A new salaryThis intake:€3,500, one time
  • Reading an ID cardTyping it yourselves:Typed, read twiceHire a data-entry person:Typed, read twiceThis intake:Read, with a confidence mark
  • A messy handwritten noteTyping it yourselves:You, with a squintHire a data-entry person:A practiced eyeThis intake:Flagged for a person
  • Finding the contract laterTyping it yourselves:Search the shared folderHire a data-entry person:Search the shared folderThis intake:Filed by client, type, date
  • The afternoon’s pileTyping it yourselves:Waits for tomorrowHire a data-entry person:A shorter waitThis intake:In the register by closing
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.

Ops Sprint

€3,500

one-time · live in 3 weeks

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

Running costs (messages, the AI model, hosting) are yours and stated up front. The 2-hour audit is the first step and costs €500, credited in full if you go ahead within 30 days. If you stop there, the written map is yours.

It’s for you if

  • A stack of IDs, invoices or contracts arrives every morning and somebody types it all in.
  • You’ve found a wrong IBAN weeks after the fact, and you’d like that to be rarer.
  • You already keep a register or a program, and you want it filled, not replaced.
  • You can show us a real morning’s stack during the audit.

It’s not for you if

  • You’re a branch, and head office picks the software. We’d be fixing the wrong desk.
  • There are fewer than three of you and little repeated typing. There’s nothing to fix yet.
  • Your clients’ documents have to be processed outside the EU, or you won’t sign a data agreement. We can’t do that.
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.

Some Wednesday soon a new client hands you an ID card, and the fields are in your register before you find a pen.

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

Or pick a time for a free intro call