DIGITAL TRANSFORMATION — DIAGNOSE · SEQUENCE · EFFECT
Not by buying a system. By asking what exactly has to stop hurting — and in what order it can be fixed so the company keeps working along the way.
Digital transformation is a change in how a company works with information. Systems are a consequence of that change, not its substance.
That sounds like a platitude until you see how many companies own five systems and have zero digital maturity. There is an ERP, a CRM, a warehouse package, a payroll tool — and a person walking between them with a spreadsheet, typing the same data for the fourth time. The money was spent, the tools are in place, and on Monday the company still doesn't know what it sold on Friday.
So we don't measure transformation by the number of systems deployed. We measure it by three things: whether data is entered once, whether decisions are made on current numbers rather than on instinct, and whether a process survives the holiday of the person who keeps it in their head. Those three questions separate a digitally mature company from one that merely bought software.
A note on vocabulary, because the question comes up on nearly every first call: digitisation, digitalisation and digital transformation are used interchangeably in practice and it isn't worth arguing about. If you must separate them: digitisation turns paper into files, transformation changes who decides what and when, because the data is finally available. The first without the second gives you a company with a tidy PDF archive and the same problems.
The second thing worth saying plainly: digital transformation is not a project with an end date. It is a change in how people work, and it continues — which is why we don't sell it as a turnkey rollout after which we part ways. We sell a plan for a year, broken into quarters, and company through executing it.
And the third, least popular: sometimes the answer is „not now". If a company has a margin problem or a people problem, no system will fix it — at best it adds a second problem. We say that on the first call, before anyone signs anything.
Companies of 20–200 people usually land on level 1 or 2 — and most often don't realise how close to the next threshold they are. Jumping two levels at once almost never works, so the plan is built around one step up, not around the end-state vision.
What the company knows lives in people's heads and in email. A spreadsheet is the main system and its author is the only administrator. Every question about numbers starts with „give me a day".
You'll know it by: one person's holiday visibly slows a department down.The tools exist — accounting, warehouse, sales — but each lives alone. The integration is a human: exporting from one, pasting into another, fixing date formats. Data exists in three versions and none is obviously the true one.
You'll know it by: the same record is entered in at least two places.Systems exchange data without a human in the middle, and repetitive work — invoice flow, orders, reports — runs by itself. Data is entered once. Month-end stops being an event. This is the level at which most companies of this size can realistically operate and where the payback is highest.
You'll know it by: a report arrives in minutes rather than days — and you trust it.Numbers stop being about reporting and start running the company: you see the profitability of a job while it is still running, not a quarter later. This is where reaching for AI makes sense — there is something to learn from and something to ask. How that looks in practice: reporting and data.
You'll know it by: a disagreement about numbers is settled by a query, not by seniority.Thirty minutes is usually enough to place you on the ladder and identify the nearest sensible step. No slides, no commitment.
The status quo has a price, it just doesn't come with an invoice — which is why it wins every comparison against a proposal that does. Below are numbers from our audits. Not to frighten anyone, but so that there is something to put on the other side of the scale.
It isn't choosing the wrong system. It is deciding to replace everything at once — usually after a year of putting it off, in the belief that if you're going to do it, you may as well do it properly. The result: several months in which the company works worse than before, the team loses faith in the project, and the first measurable outcome arrives so late that nobody remembers why it started.
The alternative is duller and more effective: one process goes into production, starts saving time, and that saved time funds the nerve for the next step.
Three companies, three different starting points. None went through transformation „as a whole" — each began with the one process that hurt most.
Starting point: level 1. Warehouse, production and customer service ran in separate tools and orders were re-typed between them — with a delay the customer experienced as „let me check and call you back". We joined the three areas into one flow, starting where sales meets production, because that is where most of the time and most of the orders were lost.
Starting point: level 0 for documents. The e-invoicing mandate was the trigger, but the real problem was a paper invoice flow. Instead of bolting one more requirement onto an old process, we reorganised the document's whole journey — from arrival to posting. Three accountants reclaimed three hours each per day. Details: electronic document workflow.
The opposite case: transformation as continuity rather than as a project. From an MVP for credit brokers to the tool an entire partner network of a bank uses daily. Four years of development in quarterly steps show what a one-off rollout cannot — that digital maturity grows when somebody stays with the system after launch.
The common thread: one process first, then the next. If you already know which one hurts most, look at process automation or AI delivery. If you don't — that is what the IT audit is for.
A change in how a company works with information — not a software purchase. The test isn't the number of systems deployed but three questions: is data entered once, are decisions made on current numbers, and does a process survive the holiday of the person who keeps it in their head.
A company can own five systems and have zero digital maturity if those systems don't talk to each other. The reverse is also true — a company with two well-connected tools is often more mature than one with ten.
By counting what the current state costs — not by choosing a tool. Without that number every proposal looks expensive, because there is nothing to compare it against. Once you know a given process eats three weeks of work a month, a quote starts to mean something.
We do this as a 14-day fixed-price audit: a process map, a list of quick wins and the cost of the status quo. After it you can see whether the first step is document workflow, system integration, or simply order in the data.
First measurable effects in two to three months; a sensible planning horizon is a year. We plan in quarters, because over a year a company changes its mind about priorities at least once and the plan has to survive that.
It is worth knowing that the end date is a convention. After a year what usually changes is the character of the work, not the fact of it: from building to developing.
No, and it is usually the worst possible decision. Replacing everything at once means several months in which the company works worse than before with nothing to show for it — and that kills support for change faster than any technical failure.
A frequent audit finding, incidentally, is that 30–50% of problems are solved by configuring tools the company already owns and pays for. Replacement is sometimes necessary, but it is rarely the first step.
Because the measures are agreed before the start, not after. Every stage gets a number you can check: hours reclaimed in a process, time from order to dispatch, the number of places the same record is entered.
If after a quarter the number hasn't moved, that is a conversation about what went wrong — not another slide about progress. We would rather have that conversation after a quarter than after a year.
WE REPLY WITHIN 24 HOURS
A free 30-minute consultation. No commitment and no sales rep — you talk to the person who will run your project.
JET LARK SP. Z O.O.
3 MAJA 22 / 2C
40-096 KATOWICE, POLAND
Your message has taken off. We'll get back to you within 24 hours — check your inbox (spam folder too, sometimes).