Excel is our system
Three versions of the same file. Nobody knows which one is current. The person who kept it all together has just left.
Automation
No more manual work between systems
We connect ERP, MES, WMS, time and attendance and CRM with the shop floor, machines and spreadsheets — into one flow. We build workflows that keep themselves on track, and we switch off the retyping of data between systems.
Sounds familiar
The company is growing. Manual work is growing faster.
The systems don’t talk to each other
ERP, T&A, WMS, machines. Each has its own data. Someone retypes it by hand. Every day.
I don’t know where the costs are leaking
Materials run out faster than the standards say they should. Tools go missing. Reconciliation? In a month, by guesswork.
People do what the system should be doing
Copying, retyping, reminders, stitching reports together. A dozen or more hours a week. Per person.
Process automation
From retyping to flow
Process mapAudit: observing the process and talking to the people who carry it out. The result is a list of automations — what, how much it costs, what it pays back.
Connecting systemsAPI, REST, SOAP on the business side; OPC-UA, Modbus, MQTT on the shop-floor side. Data flows on its own, without retyping.
WorkflowWorkflows and approvals, RPA where a system has no API, webhooks between tools. The process stops depending on people’s memory.
OversightAlerts and escalations when something stalls. We monitor, improve and add more — automations stay alive instead of rotting after a year.
Physical automation
Where AI presentations end
Most automation companies stop where the screen ends. We go further down — the signal from the shop floor reaches the report with no human in between.
RFID · UHF · tags
Tools, pallets, PPE — the system knows what was taken, when and by whom, without a logbook.
Sensors and IoT
Temperature, humidity, machine status. The reading goes into the data, not into a notebook on the inspection round.
Environmental monitoring (BMS)
Conditions in the warehouse and on the shop floor under control, with an alert before a loss becomes a fact.
Access control
Badges, PIN, entry logging — who, where and when, linked to HR data.
Automated storage
Tools and PPE 24/7, with employee identification and allowances. In real use at our clients’ sites.
Machine / PLC connectivity
Counter, status, alarm from the machine with no manual reading — straight into the shift report.
Integrations
We connect what already works for you — into a single source of truth
We don’t replace systems that work. We connect them.
Business systems
ERP, MES, WMS, time and attendance, CRM — no retyping between them.
Identification and tracking
RFID, UHF, codes, tags — tools, pallets, products.
Access control
Badges, PIN, biometrics, entry logging.
Monitoring and IoT
Sensors, temperature and humidity, BMS, environmental monitoring.
Scattered sources
Excel, SQL, API/REST, files, machines and PLCs — everything that lives separately today.
Standards and protocols
REST, SOAP, OPC-UA, Modbus, MQTT, SQL, webhooks. No closed formats.
What changes
Before and after launch
Today
- Three versions of the same file
- Data retyped by hand between systems
- Reconciliation a month later, by eye
- A dozen or so hours a week spent copying — per person
After the rollout
- A single source of truth
- Systems exchange data on their own
- Stock and costs visible in real time
- People do what they were hired to do
How we work
Done, not planned
Audit — 2–3 weeksA workshop, observation, conversations with the people in the process. A decision document, with no commitment to a rollout.
Pilot — 2–6 weeksOne process — usually the most painful and the easiest to measure. Implemented all the way.
Rollout — 1–6 monthsMore processes, areas and locations. In stages — each stage works on its own.
Support and development — ongoingSystems change, and so do processes. We monitor, improve and add more.
Questions
Before you ask
Our data is a mess — surely it is too early for you?
Quite the opposite. That is exactly when we’re needed. Putting data in order is the first layer of our work, not a prerequisite.
We don’t have an IT department.
Most of our clients have none, or just one person. We work in a way that does not burden your team — we need access and a few hours from people who know the process.
Our previous rollout failed.
The most common cause: too much scope at once and no shop-floor people on the project. That is why we start with one process and talk to the people who carry it out.
How much does it cost?
The audit has a fixed price; the pilot depends on the process. After the audit you know the price range to the last zloty — before any decision on a rollout.
From the blog: automation in practice
Integrations, workflows, apps instead of Excel. No empty promises.
A system instead of Excel: when a spreadsheet stops being enough and how to switch without disrupting work
A spreadsheet is a good tool until more than one person works on it at the same time. How to tell that this moment has passed, and how to move the data into a system without disrupting work.
Process automation in a manufacturing company: which process to start with and how to calculate it
Not the one that hurts the board most, but the one where someone retypes data every day and it can be counted. How to choose the first process and measure the effect without inventing numbers.
Integrating ERP with the shop floor: where to start so as not to sink the budget
The ERP knows what was planned. The shop floor knows what really happened. In between are a spreadsheet, a notebook and a person who retypes. How to close this gap with one process, not a two-year project.
Let’s start with one process
Usually the most painful and the easiest to measure. The audit has a fixed price and does not commit you to a rollout.