AI Automation
AI automation for one measured process at a time, such as document handling, support triage or data entry. Priced against the hours it saves you.
Where AI automation pays
The demos you see are chatbots and content generation, because they look good in a five-minute video. The money is usually somewhere duller. Picture a person who spends nine hours a week copying figures from PDFs into a spreadsheet, and gets two per cent of them wrong.
You can measure the cost of that work, how often it goes wrong and how soon automating it pays off. So that's where we start, and our first question is about your week, before any technology.
How we choose what to automate
A short audit of where the hours go. Which tasks repeat, how long they take, how often they go wrong, and what happens when they do. Usually it's a few days of asking people what they spend Monday morning on.
Then the sums, before we build anything. What it costs now, what it would cost to automate and run, and when the savings catch up. If that takes longer than a year, we say so. We've talked clients out of automation for exactly that reason.
Then the smallest useful version. One process, live and measured. A result people can point to wins more support inside a company than any roadmap.
What we build with
Whatever fits and whatever you can keep running. Sometimes an AI model does most of the work. Often it does one small part, such as reading a messy document, and the rest is ordinary integration work that will still make sense in two years. What matters is the hours you get back.
What people underestimate
Exceptions are most of the work. The normal case is a small part of the job. Most of it is what happens when an invoice arrives in an unexpected language, a service is down, or two records match equally well. Handling those is what keeps automation working after the demo.
People need to trust it. Staff work around a tool they don't trust, and at first they're usually right to. We build in the review step, show the reasoning, and let trust grow.
When we'll tell you not to
If the process changes every month, you'd be updating the automation every month. If it runs twice a year, it will never pay for itself. And if the process itself is broken, automating it just gives you wrong answers faster. Often fixing the process is the whole job, and it costs less.
If you're in Hungary
The same team offers a local version from Budapest, on Central European Time: AI consulting in Hungary. It covers automation, chatbots and assistants, and the assessment that tells you which of them you need.
How it works
- One process, measured before and after
- We start with a process whose cost you already know: hours per week, error rate, backlog. We automate that one thing, then measure the same numbers again. Without a starting figure you can't judge the result, and that's how companies end up with six tools and no idea whether any of them helped.
- The dull jobs save the most time
- Handling invoices and documents. Moving data from email into a system. Sending support tickets to the right person. Checking that two lists match. Nobody shows these off, but they're where the hours go, so we look for them first.
- A person checks the costly decisions
- Anything touching money, contracts or a customer relationship gets a review step. The person reviewing sees how confident the system is and why, so they can decide quickly. Full automation suits some tasks and is reckless for others. Knowing which is most of the skill.
- Built on the systems you already use
- We connect your existing systems. We won't sell you a platform that everything else then has to work around. If a scheduled script and one integration does the job, that's what you get, and it will still be running in three years.
- Clear costs, including running costs
- AI model usage is an ongoing cost, and it grows with volume. We work it out from your real numbers before you commit. If the sums don't work, we'll tell you before we start. Some jobs really are cheaper done by a person.
Projects like this
What's included
Included
- An audit of where your repetitive hours go
- A written payback calculation for each process we look at
- One process automated end to end, live and measured
- A human review step wherever mistakes are costly
- Handling for the exceptions, which is most of the real work
- Handover documentation, or ongoing monthly support
Not included
- Fixing a broken process underneath (we'll point it out)
- AI model and third-party API usage, billed to your account
- Staff training beyond the team using the automation
- Automating processes where the sums don't work
What we build with
- Python
- n8n
- TypeScript
- PostgreSQL
- OpenAI
- Anthropic
- Docker
What should we automate first?
How do you know it will pay for itself?
What does it cost to run?
Will it make mistakes?
Do we need a new platform?
When would you tell us not to bother?
Also in AI & automation
Tell us about your project.
Get in touch ↗