What companies ask before they invite anyone in. Including the cases where the right answer is "do not do this yet".
Ask four things. First, what happens when the engagement ends — who owns the data, who owns the code, and who can take it over. Second, whether they will also tell you what not to build: a supplier who answers every problem with a new system will sell you one. Third, whether they can work with what you already have instead of replacing it. Fourth, whether you get a fixed price and a date before the building starts.
The one that runs most often and has clear rules — for most firms that means quotes, invoicing or order records. Do not start with what hurts most; start with what repeats most. The saving comes from frequency, not from irritation, and the first finished thing is also what decides internally whether there will be a second.
Then do not automate it yet. Automated chaos is just faster chaos, and it adds a system nobody trusts to the problem you already had. If every second case needs an exception, the rules have to settle first — and that is your work, not a supplier's. We will tell you so even when it means there is no project in it.
We do not price from a rate card but from the scope that comes out of the initial diagnosis — how many processes, how many systems have to be connected, and what has to be finished before it can be used in production. The diagnosis is free and without obligation; a fixed price and date follow it.
We will not promise you a percentage. The payback figures circulating online are averages from other people's companies and say nothing about yours. In the diagnosis we count how many hours a given process swallows today and how many would be left — you work the return out from that, at your own rates. Be wary of anyone who quotes you one before they have seen your data.
For the first usable part, weeks rather than months — we deliberately build so that something can go live before everything is finished. The time usually goes not into development but into data: cleaning it, agreeing what each value means, and connecting to a system that would rather not hear about it. The date becomes fixed once the scope is clear.
We do not do grant consulting and will not pretend otherwise. Digitalisation programmes exist, but they aim at larger capital projects and their conditions and deadlines change with every call — the current state is at optak.gov.cz. If a grant matters to you, start from the scope: that is what shows whether you fall inside a call's parameters at all.
No. We do not replace your Helios, Money or ABRA. We build the layer around them — portals, workflows and reports the ERP does not have, or would handle awkwardly. Your data stays where it is today.
Often yes, and it tends to be the cheapest route. If you already pay for the tenant, you have paid for the automation too: Power Automate connects Outlook, SharePoint, Teams and Excel, and SharePoint gives documents one home and a version history. Where that route stops working is set out on When what is enough — there is no point building another system beside your tenant while the tenant still does the job.
You do. You get the source code, the documentation and the data, and the contract says so explicitly — including the right to have the system modified by someone else. Without that, vendor lock-in appears even where nobody intended it: handing over the code is not enough if you have no licence to change it. Ask every supplier this, not only us.
We build systems so that permissions are enforced at database level, access is encrypted and the scope of personal data is decided during design. Credentials live in environment variables, never in code. How we handle data from this website is described in our privacy policy.
Eteron Group (Eteron Systems s.r.o.) is based in Valašské Meziříčí and works with firms across Czechia. We build custom automation, dashboards, internal tools and data foundations — in Moravia, Silesia and Bohemia alike.
Firms where administration already costs real money but an in-house IT department does not yet pay for itself — most often manufacturing, wholesale and distribution, and companies running a dealer or service network. Headcount is not what decides it; the hours swallowed by manual work are.
Yes — manufacturing, alongside wholesale and distribution, is our most common sector. Typically: order records and their status, inputs for production planning, goods in and out, complaints and service call-outs, and the reporting somebody currently assembles by hand from several exports. We do not replace the production system or the ERP — we build what is missing around it.
We answer enquiries within two working days. You do not need a finished brief for the first conversation — describing what is not working is enough.
Both. The initial diagnosis and the rollout we do in person at your site. Development and ongoing consultation run remotely, so distance is not the constraint — we work across Czechia.
Whichever suits you. Either someone on your side takes the system over — in which case documentation and training are part of the handover, not an extra charge for it — or we keep running and extending it. What matters is that you can still change your mind later: that is the difference between a supplier and a dependency.
And how many hours sit in them. We walk through your operation, pick three concrete processes and work out the time and money tied up in each. Free, no obligation.