Digital transformation: from strategy to working systems
Digital transformation works when you change one process at a time, not everything in one programme. Pick the process with the most manual work, digitise it on the systems you already run, and measure before choosing the next.
Most digital transformation programmes do not fail on technology. They fail because they try to change everything at once, start with a new ERP as if that were the transformation, or bring the IT partner in after the plan is written. This page is about the opposite approach: one process at a time, on the systems you already have, with a measured result before the next step.
Last updated: 5 November 2026
Digital transformation means changing how a process runs, not only putting it into software. Digitisation turns paper into data, digitalisation automates a step, and transformation changes the process itself, often with AI where judgement used to be manual. The approach that works for an organisation with an existing IT landscape is process by process: pick the one with the most manual work, set a baseline, build a working version on your current systems, and measure. Crux Digits does the AI and software part of that; your ICT partner keeps the infrastructure.
Digitisation, digitalisation and digital transformation
| Term | What changes | Example |
|---|---|---|
| Digitisation | Paper becomes data. | Scanning work orders into PDFs. |
| Digitalisation | A step is automated. | Work orders flow from the app into the ERP without retyping. |
| Digital transformation | The process itself changes. | Planning is done by a model that reads the work orders, with a planner approving it. |
Where digital transformation programmes stall
- Everything at once. A programme across nine processes produces a roadmap and no working system for a year.
- A new ERP as the transformation. Replacing the system of record is a migration, not a transformation; the process often stays the same.
- No baseline. Without measuring how long the process takes now, nobody can show it improved.
- The ICT partner arrives late. Access, hosting and change rules come up after the build, and the project waits.
- Adoption as an afterthought. The people who run the process were not involved, so they keep the spreadsheet next to the new system.
How to choose the first process
| Question | Good first process | Leave for later |
|---|---|---|
| How much manual work? | Hours a week, every week, across several people. | An occasional task one person does. |
| How rule-based? | Mostly the same steps, with clear exceptions. | Every case is a judgement call. |
| Is the data there? | In your ERP, CRM or mailbox, reachable through an API. | In people's heads or on paper only. |
| Is there an owner? | One person who answers for the result. | Shared by three departments. |
| Can you measure it? | Lead time, error rate or hours are countable today. | Nobody knows how long it takes now. |
A digital transformation strategy, one process at a time
| Step | What happens | Typical length |
|---|---|---|
| Choose | Pick the process with the most manual work and a named owner. | part of the audit |
| Baseline | Measure lead time, error rate and hours per week as it runs today. | part of the audit |
| Working version | Build the new way of working on your current systems, tested with the real users. | 4 to 6 weeks |
| Production | Roll out to everyone, with monitoring, documentation and handover. | from 8 to 12 weeks |
| Next process | Reuse the integrations and the approach for the next process. | repeat |
Who does what: you, your ICT partner, Crux Digits and BLIK
| Area | Who |
|---|---|
| Infrastructure, workplace, hosting, licences and service desk | Your ICT partner, unchanged. Crux Digits does not take this over. |
| AI, custom software, integrations and data | Crux Digits, built on the interfaces your ICT partner manages. |
| Business case, process change and adoption | Your organisation, or BLIK Consulting when you want a partner for that side. |
| Ownership of the result | Your organisation: code, documentation and data stay yours. |
What a transformed process looks like
From our case studies: a national occupational-health platform where AI decision support standardises medical-fitness assessments with the clinician signing off; demand forecasting and production planning for a €235M manufacturer; and predictive maintenance that flags failures before they stop a plant. Each started with one process. All 13 are on our case studies page.
What it costs
| Step | What you get | Price (excl. VAT) |
|---|---|---|
| AI audit and strategy | Where to start, in which order, with the first build priced. | €2,500 |
| Production-ready MVP | The first process working on your real systems. | €20,000 |
| Production | Rolled out, monitored and handed over. | from €50,000 |
Frequently asked questions
What is digital transformation?
How do you start a digital transformation?
Does Crux Digits replace our ICT partner?
Do we need a new ERP first?
What does a digital transformation cost?
Which process should change first?
Tell us which process costs your people the most manual work and which systems it runs on. We tell you where to start and what the first step costs.
Book a free consultation →