Mihály Tari.

AI AUTOMATION

If somebody at your company repeats the same manual job every week, that's the part a machine can take over.

In twenty years I've seen why these jobs stay manual, and it's rarely that the work is hard: nobody ever wrote the steps down, and the off-the-shelf tool that almost does the job takes more time to set up and patch than it gives back. So I start with a single process: I write it down, build it in your own account, and hand it over with one page saying what runs, when, and what to do when it stops.

Mihály Tari · 20 years shipping software, web and mobile.

Request a quote ↓

Where the week goes

When I walk through a company's week, the same five jobs turn up almost every time. None of them is hard, which is why nobody complains about them; added together, they take a good part of the week.

  1. 01

    Somebody retypes incoming orders into the invoicing tool.

    Two or three hours a week, and a typo only surfaces when a customer says the invoice came out in the wrong name.

  2. 02

    The same twenty questions arrive by email, and the same twenty answers go back.

    An hour a day, while the work that actually needs thinking waits at the end of the queue.

  3. 03

    Two systems disagree, so somebody reconciles them in a spreadsheet.

    Half a day a week, and a missed order only comes to light two days later.

  4. 04

    A PDF or a scan arrives, and somebody copies the fields out of it into a table.

    Ten to fifteen minutes per document, which by the end of the month is a full working day.

  5. 05

    The same post goes up in three places by hand, resized for each one.

    An hour or two a week, and most weeks the third place never gets done.

What I automate, and what I turn down

One principle sits behind the whole list: the machine does the part that happens the same way every time, and the decision stays where a person is needed. I pick the tool for the job, and I say which one and why.

  1. 01

    Orders and forms into the invoicing tool

    Data from your online shop or your form appears in your Számlázz.hu or Billingo account on its own, and the export your accountant needs comes out of the same run. n8n usually does this part: it's a program that works through the steps in order, and I set it up inside your own account; the same thing can be done with a rented service called Make.

  2. 02

    Incoming email sorted

    Mail lands in the right place by topic, the common questions get a draft reply, and anything a person needs to read is marked as such. You still send the replies yourself.

  3. 03

    Two systems kept in step

    Your customer records, your spreadsheet, your invoicing tool and your online shop's admin screens show the same data, because a change in one moves to the others. Where a difference remains, you get a list of them, and neither side quietly overwrites the other.

  4. 04

    Documents read into a table

    The machine pulls the fields off an incoming invoice, delivery note or contract and writes them into your table. Anything it's unsure about goes into a separate row for a person to look at, and that step isn't optional.

  5. 05

    Content posted from one place

    One text and one image go out to your Facebook Page and to LinkedIn together, through an app registered in your own name with Meta, the company that runs Facebook; Meta requires one for every connection of this kind. I start that approval on day one, because it can take days.

  6. 06

    Answers from your own documents

    A question asked on your site or in chat is answered from your own documentation and your own price list, and the conversation opens by saying it's a machine talking. Anything it can't find there, it hands to a person, with a note on when to expect a reply.

What I turn down

  • Running your processes on my own server The n8n licence doesn't allow that as a service to other companies without a separate, expensive agreement, and it would create exactly the dependency this page argues against. Everything runs in your account, in your name.
  • Running personal profiles and groups by machine Facebook's and LinkedIn's own terms forbid a program logging in and posting as a personal profile, and a locked account is the usual result. I do work with a company page and proper access.
  • Sentiment and personality analysis I don't analyse the caller or the customer beyond what they're actually asking for. That kind of analysis is legally risky, and it draws conclusions from a conversation that you would have to answer for later.
  • Money or signatures without a human step No machine of mine completes a payment, signs a contract or closes a decision with legal consequences on its own. It prepares all of that; you approve it.
  • Building an online shop I don't build online shops, because doing that well is a trade of its own. The admin side of the shop you already have can be one of the connected systems.
  • Work running past roughly six months Above that size a build needs a team where one person dropping out doesn't stop the work; the web application page carries the same limit. At that point I either say no, or I name the people I'd bring in, agreed up front rather than discovered halfway through.

How it starts, and what it costs

There's a fixed-price package for one process, and anything bigger starts with scoping. The listed price is the total, and no VAT goes on top.

First automation

€690

10 business days, fixed price

I take one process end to end, from where somebody starts it by hand today to where they finish it. The n8n or Make account is yours; I work inside it as an invited user, and I remove myself at handover if you want.

  • One process, up to three connected systems
  • In your own account
  • Error handling and one alert you'll actually read (email or Slack)
  • A one-page runbook: what runs, when, and what to do when it stops
  • A recorded handover
  • 30 days of fixes

Scoping

€970

1–2 weeks, fixed price

This is for anything larger than one process, whether that's several processes feeding each other, an agent written in code rather than assembled from ready-made steps, a chatbot, or an agent that answers the phone. I walk through your processes, and you get it in writing — what's worth handing to a machine, what isn't, and what the worthwhile part costs.

  • A map of what happens today, step by step
  • What's worth automating, and what isn't
  • The rule per step for where a person has to approve
  • The expected monthly running cost, in numbers
  • The architecture, including what I ruled out
  • A risk list in the sample report's format
  • A fixed quote, valid 60 days

It comes off in full if the build starts within 60 days. The document is yours either way, even if you have it built somewhere else.

Project

from €5 500

4–6 weeks

This is the build after scoping, for when the job is bigger than a single package holds. The real number is the fixed quote at the end of the scoping; the figure here is the point below which a custom build isn't worth it for either of us.

  • Several processes or a custom-code agent, to the plan from the scoping
  • Phase by phase, with something working after each phase
  • The same runbook and recorded handover as the smaller package
The full price list on the consulting page →

Monitoring

€83/mo

no minimum term

After handover somebody still watches whether the process is running, and tells you when it has stopped. Everything keeps running without it; the difference is that nobody reads the alerts for you.

  • Monitoring
  • Failure alerts read by a person on business days
  • Two hours of changes a month
  • One line a month on what ran and what failed

Anything beyond those two hours a month is invoiced from the €70 an hour the consulting page publishes.

What it costs to run each month

The running costs go to accounts in your own name, on your own card, so you never pay them through me. n8n Cloud starts at €20 a month, though it can also run on a small server of your own for €5–12 a month, and Make starts at $9 a month. The language model, the part that reads and writes the text, is billed on how much you send through it, and a phone agent adds a per-minute rate on top. So that month four holds no surprise, both the scoping and the written intake before a build put the expected monthly figure on paper before anything is built.

How it goes

There are four steps, and at the end of each one you know where the work stands; the first costs you nothing. The ten business days only tick on days when I have everything I need: if I'm waiting on access, on data, or on a decision only you can make, the clock stops and I write to say what I'm waiting for.

  1. 01

    A call

    In half an hour you tell me which job comes round every week, and I tell you whether a machine can take it and roughly which package it falls in. If it isn't a job for a machine, I say that too.

  2. 02

    The intake

    I write down which process it is, where the data lives, and whose name each account is in. Where content goes to social platforms, I start Meta's review of your own app on day one, because that's the step that takes longest. Once the intake is complete I ask for 30% of the price as a deposit, and the ten business days start from that day.

  3. 03

    The build

    I build the process in your account, and you watch the test run with me on your real data rather than on an invented example. Anything you see there and don't like, I change before handover. And if the test run shows you it isn't what you expected and you stop the work in writing, I refund the deposit in full.

  4. 04

    Handover

    I hand it over on a screen recording that shows where the process runs, how to start it again, and what the alerts mean. The one-page runbook comes with it, and from then on every credential is in your hands.

What I put in the contract

It's built in your account, it stays in your name, and I hand it over in writing.

The three parts only mean something together: a process running in your account still isn't yours to take over if nobody wrote down what happens in it and why. So the write-up is as much a part of the work as the build.

The account and every credential are yours from day one
The n8n or Make subscription, the mailbox, the invoicing tool and every login are in your name, and I work in them as an invited user. At handover I remove my own access as well, if you want.
Everything is exported and handed over with the runbook
You get the processes exported and the one-page runbook, so if you move the work elsewhere tomorrow, everything the next person needs is already yours. There's no part whose key stays with me.
Stop paying for Monitoring and everything keeps running
The processes run in your account, so they carry on after you cancel; what changes is that nobody reads the alerts for you. That's why there's no minimum term.
A written rule says what the machine may not decide alone
Every automation comes with a rule naming what needs a person: a payment, a quote, a contract, a final answer going to a customer. The machine prepares those; approving them stays with you.
Every chatbot and phone agent says it is AI
The machine says so at the start of the conversation, and it says so about the recording too if you record the call. Beyond that I run no analysis on the caller; only what they're asking for is processed.
Your data reaches the model under your own contract
The process uses the language model through your own account, so the contract with the provider is yours, in your own name, and the terms on that side are yours to set. Wherever I handle personal data during the build, I sign a data processing agreement with you. Which AI tools I use in my own work is written out on its own page. How I work with AI →
The legal entity
I'm a VAT-exempt sole trader in Hungary, so the listed price is the total and no VAT goes on top. The registration number, the tax number and the registered address are in the imprint. Imprint →

The guarantee on a first automation

If the process doesn't do what the one-page runbook says within 30 days of handover, and I don't fix it, I refund the build fee.

A guarantee is worth as much as the document it can be measured against. That's why every automation comes with a one-page runbook naming what starts it, what goes in, what comes out, and which failures it handles on its own. The 30 days run from the day of the recorded handover, because that's when you saw what you got.

What it doesn't cover

  • A third-party service changing or withdrawing the connection point the process works through.
  • A credential or password you change without telling me.
  • Incoming data that turns out not to match what the intake described.

Questions

Why does one company quote a small monthly fee and another quote a full project?
Because they're selling two different things. The monthly fee is usually rent on a finished product that solves a general problem in a general way; if your process looks like everyone else's, that's the right buy, and you don't need me. The project price is a team's work over several months, across several processes, in custom code. What you're reading here sits between the two: one process, at a fixed price, in your own account, and the result stays yours after the work ends.
How long until it runs?
For one process, ten business days to handover, at a fixed price. The clock only ticks on days when I have every credential and every piece of data; if I'm waiting on something, it stops and I tell you what for. For anything larger, scoping comes first — one to two weeks — and at the end you can read how long the build itself takes.
Does it speak my language, and does the voice sound natural?
In writing, yes: email, chat and answers drawn from your own documents work well, and I can show you that. Voice is a different question. Machine speech is still recognisable as machine speech, so I only take on a phone agent through the scoping, and you hear how it sounds before you decide. The platform cost of a phone agent runs roughly $0.10–0.35 a minute, on your own account and on top of the build. I don't promise anything you haven't heard.
Where does my data live, and what does the AI Act require?
The data stays in the system it's in today, and only the fields the process needs move anywhere. The process uses the language model through your own account, so the contract with the provider is yours, in your own name; and wherever I handle personal data during the build, I sign a data processing agreement with you. The relevant rule in the EU AI Act has been in force since 2 August 2026: a person talking to a machine has to be told so, and every chatbot and phone agent I build says it at the start of the conversation.
Do I need a developer or an IT team for this?
No. What I build runs in your own account, and using it day to day takes somebody reading the alerts and knowing what to do when a process stops, which is what the one-page runbook is for. If you'd rather not watch the alerts yourself, that's what Monitoring is for, and it's optional.
Do I have to replace the software I use now?
No. Billingo, Számlázz.hu, MiniCRM, Shoprenter and Unas all stay where they are; the process connects to them and moves the data between them. If one of your systems has no usable connection point, I say so on the first call or in the scoping, before I take anything on.
What happens when the AI gets it wrong?
That's where the design starts. Every automation carries a written rule on what it may not decide alone: it sends no payment, quote, contract or final customer answer without approval. Where it's unsure, it stops, puts the case in a separate row, and raises a flag. That way the mistake shows up while it can still be fixed.
Is there a minimum term?
No. The first automation is a one-off piece of work at a fixed price, and you can cancel Monitoring at the end of any month. If you cancel it, the processes keep running, because they're in your account; what changes is that nobody reads the alerts for you.
How do I pay?
For a first automation, in two steps: I ask for 30% of the price, €207, as a deposit once the intake is complete, and the remaining 70% at handover. At the test run on your real data you can stop the work in writing; then I refund the deposit in full and there's nothing more to pay. After that the deposit stays, and silence isn't a stop. The 30-day guarantee after handover stands either way. Scoping works the same with a €291 deposit, and the stop point is the draft you get halfway through; on a project the deposit is 30% of the fixed price, credited against the phase invoices. Monitoring is a monthly fee with no deposit, and you can cancel it at the end of any month. I'm a VAT-exempt sole trader in Hungary, so the listed price is the total and no VAT goes on top.
What does it cost to run each month?
The accounts are yours, so you pay the running costs to the providers directly. For one process that is usually one subscription plus language model usage, which follows your traffic; the exact figure goes in writing into the scoping and into the intake before a build. The itemised version is above, under the packages. The monthly running costs ↑
Do you have references?
I only talk about client work with written permission, and I don't have that permission for any of it yet, so I can't give you names. What you can look at is the shape of my written work: I published a complete, unredacted audit report on my own codebase, including the flaws it found. The scoping risk list and the automation runbooks come out in the same format. The sample report →
I think what I actually need is an application.
That happens too: if the job needs its own screens, its own users and its own permissions, then it's an application rather than data moving between systems you already have. The web application page describes how that goes, with the same kind of scoping at the start. Custom web application →

Request a quote

Tell me in a few sentences which job comes round every week and what systems sit behind it. I reply within two business days: whether a machine can take it, which package it falls in, and if it isn't a job for me, that too.

or email me directly: contact@mihalytari.com

or call me: +36 30 179 8852

Before sending, please read the privacy notice .