AI automation engineer · Poland
The checkerroutine work · the odd ones to a person
I'm Mateusz. I build AI automation, and I do the work myself. If you're here from my email, it named the piece I'd start with.
Already have an email from me? Just reply to it. It comes straight to me.
What I work on
Someone opens a document, finds the numbers, checks them against something else and types the result into another system. The rules are clear; the documents are messy. That's the part I automate. Your team keeps the decisions and gets a short list of what needs a person.
If someone does it the same way each day, it can run on its own.
Anything unusual comes back to a person, with the reason.
Hiring for this? I'll build the first piece while you hire.
Fig. 2 — Work that runs this way
On its own: invoices built and payments applied. Back to a person: short payments and disputes.
On its own: pulling the numbers and sending the report. Back to a person: a number that looks wrong, before it goes out.
On its own: reading each order and entering it. Back to a person: anything unusual, like a part number it doesn't know.
On its own: removing duplicates, filling in the company, assigning it. Back to a person: a lead no rule covers.
On its own: reading, sorting and routing each request. Back to a person: urgent cases, and anything waiting too long.
On its own: records, licences and checklists. Back to a person: missing details and equipment to hand back.
Systems that read documents and images at volume, agents that run around the clock, and tools that answer from a company's own information.
Subject:
Built it, then ran it as a paid service
Steps
Subject:
For a healthtech company
Steps
Subject:
For a travel startup
Steps
I build a small working version on made-up documents shaped like yours and walk you through it on a call. It's free, and you share no data. If it isn't useful, we stop there.
The demoFree · no data needed
How I work
The person on our first call is the person who writes the code and looks after it.
4.1
Scope
We start with one piece: the one from my email, or whichever takes your team the most hours. I build it on your real documents, connected to the tools you already use, usually in about two weeks.
4.2
Checks
Anything it can't match with confidence goes to a person, with the reason. Your team reviews a short list instead of the whole pile.
4.3
Afterwards
When a supplier changes a format or a rule changes, I fix it. Or I hand it to your team with notes on how it works.
Who you'll work with
AI automation engineer · Poland
I've been building AI that runs in production for more than four years, for companies that need it working every day.
It runs in your accounts or mine, your call. I start with read-only access where I can, sign an NDA and a DPA, and never train models on your data.
Book a call
Tell me how the work runs today. I'll tell you whether I'd automate it and what I'd do first. If I wouldn't, I'll say so.
Rather write? Reply to my email, or write to [email protected].