How deployment
works
What happens between signing and a running operation, what we do and what we need from you. No surprises, and no need for an IT department of your own.
7 days Standard deployment for small and mid-sized operations. Up to 30 days for complex ones.
Fixed scope The date and the handover criteria are signed up front, on Day 0.
No IT of your own Setting the system up is our job. Your people do not have to be technicians.
This guide is for you if…
- you run an operation — production, warehousing, logistics, an online shop or distribution,
- part of your processes still runs on paper, in spreadsheets or in people's heads,
- you have already lived through a project that dragged on and ended differently than planned.
Guide · ERP → ERI erios.sk · erios.cz
Guide · Deployment
Why we do the deployment
Until now the project risk sat with
the party that did not cause it.
For decades it has worked the same way: you pay up front, you wait months, sometimes years — and only then find out it is not what you needed.
We do it differently. We spent years building and tuning ERIOS in live operations, not on paper. That is why we can show it to you working before you sign, deploy it in 7 days and quantify the benefit in advance. The risk does not move to you — it stays with us.
Scope Fixed What will be delivered is a list signed on Day 0 — not something to argue about later.
Date Fixed The go-live date does not move. Plan your people and your jobs around it.
Handover Measurable The criteria are defined up front and verifiable. Either they are met or they are not.
Most projects drag on because the parties keep negotiating what was supposed to be built. We agree it at the start and sign it: what will be delivered, by when and how it will be verified. That is exactly why we can quantify the return rather than promise it.
We do not sell modules. We sell a return.
That is why day one is not about configuration but about mapping your real flows. The return calculation comes out of those — from your own figures, not an industry average.
What we do
- We map the real flows in your operation.
- We set the system up around them — roles, stock, orders, production and records.
- We train your people and go live.
- We advise which devices suit your operation — and if you want, we supply them.
What we need from you
- One person who knows the operation and can give us an hour a week.
- Access to the workplaces while we map.
- A decision on where we start — we will help you make it.
Guide · Deployment2
Guide · Deployment
Timeline
What happens when
The same timeline you see on the website. We stick to it.
Two paths, the same steps. Standard deployment for small and mid-sized operations takes 7 days. For more complex briefs — several sites, atypical production, heavier integration — the same steps spread across a maximum of 30 days. Which path is yours is clear right after the flows are mapped — not somewhere mid-project.
Day 0 Standard · Day 0 Complex · Day 0
Signature and acceptance protocol
The handover criteria are defined up front and signed. The scope is fixed — it is not up for later negotiation.
Step 1 Standard · Day 1 Complex · Week 1
Mapping the flows
We walk your operation and map the real flows — not the ones from the manual. This is where the return calculation comes from, and where it becomes clear which of the two paths we take.
Step 2 Standard · Day 2–5 Complex · Week 2–3
Configuration by our team
We do the configuration: roles, stock, orders, production and records, based on what we saw in the operation. Meanwhile your people carry on working.
Step 3 Standard · Day 6–7 Complex · Week 4
Training and go-live
We train your people and go live. You add another device later yourself by scanning a QR code — without us and without waiting.
Standard — small and mid-sized operations (SME) Complex operations — 30 days max
You do not get a presentation. You get a running operation.
From go-live, data is created at the point of work — not typed into a spreadsheet in the evening. The system is 100% paperless and every step leaves a digital trail.
Guide · Deployment3
Guide · Deployment
What you can count on
What you can rely on
Four properties that matter once the system is running for real.
Works offline too
The system runs without a connection and syncs once it is back. An outage does not stop the operation.
Fast recovery
After a failure you restore a device by scanning a QR code and carry on. You add another device the same way.
Full traceability
Append-only — nothing is deleted. Every step leaves a digital trail: who, when, what and where. You have an auditable history as well as a plan.
Runs without depending on IT
It needs almost no attention. The system does not need an administrator of its own — and when something needs doing, that is on us.
Frequent questions
What people ask us most
The answers that usually only come up at the third meeting. Here they are up front.
We already have a system. Do we have to throw it out?
No. We start where the biggest loss happens — usually between the order, the warehouse and production. We can run alongside the rest and connect to it through the data.
What does it cost?
The price follows the size of the operation — how many workplaces, devices and processes we take on. We deliberately do not publish a price list: until we have seen your flows it would only be a number. After the mapping you get the price and the return calculation in one document — and only then do you decide.
Is it for our industry too?
ERIOS is built for operations-driven companies in general — production, warehousing and logistics, e-commerce and fulfilment, FMCG and distribution, and technical operations. What matters is whether goods, material or tasks pass through several steps.
What if you miss the deadline?
The date and the handover criteria are part of the protocol signed on Day 0. If we do not meet them, that is our problem, not yours — which is exactly what the sentence at the start of this guide is about.
Do we need an IT department for this?
No. Our team does the configuration, you add another device by scanning a QR code, and when something needs doing, that is on us. That is precisely why deployment takes days rather than months.
Guide · Deployment4
Guide · Deployment
The next step
Two ways to start
Both are without obligation. Pick the one that fits the time you have right now.
Live demo · 20 minutes online
I want to see it first
We show you the system running on data that resembles your operation. We enter one order, change a date — and you see the whole flow and the delivery time recalculate.
Nothing to prepare on your side.
A no-obligation analysis · on your own figures
I want to know what it will bring
We walk your operation and tell you where we would start, what it will bring and what it will cost — or we honestly say it does not make sense yet.
The output is a document, not a presentation.
What happens when you get in touch
1We get back to you within 24 hours and arrange a short call about where it pinches most.
2If it makes sense, we come for a site visit and map the real flows.
3You get the return calculation and the price in one document. Only then do you decide.
What the analysis gives you
01 A map of your flows Exactly where the loss, the waiting and the retyping happen — in your operation, not in a model.
02 The return calculation What the current state costs you a year and how long the investment takes to come back.
03 Price and timeline A specific figure and date — with a scope ready to sign.
You do not pay us to try.
The analysis is without obligation and its output stays with you — even if you decide not to go ahead. Proven in enterprise operations in the EU and the USA.
Guide · Deployment5