Everything from one team
Design, build and operations with the same team, from the first call to launch.
A company AI audit that ends in a working system.
Everyone is asking what your company's AI plan is. The audit names the one process where the most manual hours disappear at your place, and it says so when this is not your next step yet. Whatever it recommends, the same team builds it and takes it live. For companies of 5 to 50 people with no dedicated IT team.
12+ projects delivered
every one on deadline, in production
Fixed price and deadline
in writing, and if we slip, the next payment waits
Reply within 24 hours
on working days, to every enquiry
In writingAfter the assessment
Two stages, two prices: the assessment first, then the build.
Why AI has not started at your company
Everyone is asking what your AI plan is.
The honest answer is that there isn't one, and saying that out loud has become uncomfortable.
The same figure gets typed into three systems.
They disagree with each other, and at the end of the month somebody sits down to work out which one is right.
There was an attempt, and it produced a demo.
It looked good in the room, then nothing changed. Asking for the budget a second time is harder.
You do not know where the data would go.
Who sees it, how long it is kept, and who answers for it if something goes wrong. Until that has an answer, every idea stalls.
Our answer to each of those
Eurostat's 2025 survey puts AI use at roughly a fifth of EU enterprises, and at 17% among small ones. Three of your four competitors are exactly where you are. So we start with one process: the one carrying the most manual hours.
One process, named
The assessment walks how you work today and names the single process eating the most manual hours. That is the answer you give the next time somebody asks what your AI plan is.
The work we take over
Fields read out of an invoice or an order, inbound email sorted with a first draft of the reply, a quote drafted from your own price list, and the management report assembled out of the systems you already run. All four run on data you already hold.
The assessment is allowed to say no
If it does not pay off at your size yet, the document says so, with the reasoning. A vendor living on pilots has no reason to write that down; we do, because the next piece of work comes from the same person.
The data path is written down first
Which step data leaves the company at, what the model sees, how long it is kept and how it is deleted. Where the data is sensitive we cut it out of the flow before anything moves.
What holds companies back
70.9%
Of EU companies that considered AI and did not adopt it, this share name missing expertise as the first barrier.
"We have nobody who understands AI"
You do not need one. You know the process, we know the AI. Your team learns to use the system; running it stays with us, under monthly maintenance.
52.5%
This share are held back by legal uncertainty.
"What about the legal side?"
There is a concrete rule now and we build to it: since 2 August 2026 the EU AI Act requires an AI answer and AI-written content to be labelled. We build to that transparency rule wherever the system runs, because it is the strictest regime we work under. The high-risk tier that gets the press starts at the end of 2027 and does not touch a typical SME process.
48.8%
This share name data protection as the obstacle.
"Where does our data go?"
Where the proposal says. We record which model sees what and configure it so the provider does not train on your data. Every AI step is logged, so it can be traced afterwards.
Eurostat's 2025 EU enterprise survey. Industry research, not our own measurement. The same survey finds only a fifth of companies call AI irrelevant to them, so the barrier is expertise, and expertise is what you are buying.
Where it pays off first
Three kinds of work come up over and over, and all three run on manual hours. The assessment names the one costing you the most.
Translation
Multilingual communication and customer replies.
Documents
Inbound paperwork read, sorted and summarised.
Drafting
Copy a person approves before it goes out.
Ordered by industry surveys of AI adoption, not by our own measurement.
What we have already built
Gloster Content Engine
We built an internal AI content platform for a software company, and it runs in production. It drafts from a brief and from research, in several languages, and a person decides what goes out.
There is no figure beside it on purpose: the return is measured by the client on their own data, and we do not claim what we did not measure.
Companies we've built for
Gloster
Palm Group
Habibi
The Garage
Design Glass
Kék Padlizsán
Jungle Burger
D+D Solar
Fawa
On every project
Your goal sets the bar
The first call is about what you want to achieve; if less will get you there, we say so.
Tested before it goes live
We measure what we hand over before launch, and watch the first week with you, measurements included.
What each role gets
For the owner
A written monthly figure: the hours the system replaces, and what it cost. The return is a number you track, and the system belongs to the company, credentials included.
For office and finance
Invoices, requests and email arrive pre-processed, ready for a decision. Typing and copying leave the day, and the decision stays with you.
For whoever does the routine work
The system writes the first version: the reply, the summary, the translation. You read it over, and the decision about what goes out stays yours.
A worked example of a built process
An inbound quote request, once we have automated it for you
The steps are the ones you run today. Fewer of them go through a person.
Inbound email
The enquiry arrives in the shared inbox, exactly as it does now.
Extract
The system pulls out who is asking, what for, and in what quantity.
Draft quote
An itemised draft is assembled from your own price list, in your usual form.
Approval
A person reads it, corrects it, and decides what goes out.
Send
The approved quote goes back to the sender and is filed with the thread.
Who AI automation pays off for, and who it does not
This fits you if
- One process eats a lot of manual hours every week.
- The data the work runs on already sits in a system you own.
- You expect a measurable result, counted in hours.
We would point you elsewhere if
- The process runs a few times a month. Automation costs more than it returns there, and we say so.
- You want a chatbot on the website. That rarely pays for itself on its own.
If the process needs a system before it needs AI, this is where we would start.
The package
First process
- One chosen process, assessed and built
- A clickable preview on your own data, at every stage of the schedule
- A monthly written measurement: the process's hours, before and after
- Human approval on the sensitive steps
- Labelling and logging built to the EU AI Act standard
- The system and every credential are yours
If an off-the-shelf workflow would serve your process, we say so on the call.
In writing
After the assessment
How many steps the process has and how many systems it touches. Email triage costs less than document processing wired into invoicing.
Then: maintenance and growth
A monthly plan with a fixed response time: monitoring, model and prompt updates, the next process. With a rented AI tool the fee runs per user, and it runs for as long as the company uses it. This fee is set in the first proposal and it is optional: the system is yours, credentials included, and runs without us.
Request a process assessmentWhat happens after launch
When the process changes on your side, the system changes with it. That is most of what monthly maintenance means here.
First month
A clean handover, a watched launch
Source code, credentials and documentation in your hands. We watch the first week with you, measurements included.
Every month
Maintenance that keeps it moving
Updates, fixes, extensions, and the measurements watched as your product grows.
If something breaks
You write, we answer
A first reply within 24 hours on working days, to every enquiry.
How much does AI automation cost?
The price list says the price comes after the assessment, and two things decide the number: how many steps the process has, and how many systems have to be touched. The assessment is its own stage with its own price, so the build is a decision you make afterwards.
Two separate products. The free audit answers one question: is your company ready for AI today, and is it worth starting at all. You get a short written answer to that, and an offer of a call. The assessment is the paid stage and it is the full walkthrough: which process burns how many manual hours, what has to be connected to it, and what order to take them in.
About 40% of enterprise AI projects that start ever reach production (Gartner data, via Portfolio.hu's 2026 summary). That is what the assessment is for: it names the process, the integration points and the hours you can expect to save before anybody writes code. What gets built after that runs in production, not in a demo.
If you have the capacity and the experience, build it in-house, that is the cheapest route. A 2025 MIT study found that externally purchased AI solutions succeed about 67% of the time against roughly 33% for internal builds. In-house work sits alongside the day job, and urgent tasks tend to take the time back. We take it through at a fixed price and a stated deadline, then hand it over so it runs without us.
One week. We walk the processes, find where the manual work goes, and check which step has usable data behind it. You end up with a written document: what is worth automating, in what order, and what it costs. The build after the assessment typically takes 2 to 4 weeks, on the schedule the proposal sets.
The company is, the same as today when a colleague sends the email. So the system is built to keep that manageable: at a step that goes outside, a person approves it, and there is a written trace of what went in, what the model returned, and who let it through. When something does go out wrong, that trace is what shows where to fix it.
It is the most common situation there is, and it is not the team's fault: nobody gave them an approved route to work on. The first step of a rollout is that route. One process where it is written down which model sees what, where the decision stays with a person, and what never leaves the company at all.
The material is yours either way, and it is written so somebody else can work from it: which step connects where, what data it needs, in what order. There is no pre-contract behind it, and nothing to pay to take it with you.
Start with the assessment
Thirty minutes, and we pick the process where the most manual hours disappear. Including the case where this is not your next step yet.