Making your company smarter without replacing your ERP
In Türkiye 28.3% of enterprises use ERP, but only 6.5% use business intelligence. Data is recorded, not read: the intelligence gap is not a systems gap.
Representative photo · Alejandro Escamilla / Wikimedia Commons, CC0In Türkiye, 28.3% of enterprises with 10 or more employees use ERP software, 12.0% use customer relationship management (CRM) software and only 6.5% use business intelligence (BI) software 4. Companies that record their data in an ERP outnumber those that analyse it with BI software by more than four to one. What is missing is not the record — it is a way to make your ERP smarter by reading what it already holds.
- ERP
- 28.3%
- CRM
- 12.0%
- Business intelligence (BI)
- 6.5%
Source: TÜİK (2025)
Europe is further ahead, but the pattern is the same: 46.45% of EU enterprises use ERP 2, while 20.0% use AI technologies 1. The scopes are not identical — since 2025 TÜİK also counts the financial sector, Eurostat does not — but the message holds on both sides: the data sits in the system and never reaches the decision-maker’s desk.
AI is spreading, value is lagging
Adoption is accelerating. In Türkiye, the share of enterprises using AI rose from 7.5% to 14.0% in a single year 3; in the EU it climbed from 13.5% in 2024 to 20.0% in 2025 1. But using AI and profiting from it are not the same thing.
Source: McKinsey & Company (2026)
In McKinsey’s 2026 survey, nearly nine in ten respondents report regular use of AI in at least one business function, yet only 37% say it has contributed positively to EBIT — essentially unchanged from a year earlier 5. The share reporting that AI is scaling across the enterprise rose from 38% to 44% 5; more than half still cannot say so.
The intelligence gap is not a systems gap
Put these two pictures side by side and the problem becomes clear. What companies lack is not another system: orders, invoices, payroll and production records already live in the ERP. What is missing is that this data is read every day and turned into a simple message for managers: “this is what needs your attention today”. When AI is set up as a separate project, it stays disconnected from daily operational data; the pilot looks good, the decisions stay the same.
That is why the first reflex — “let’s replace the ERP” — is usually the wrong question. The ERP is the system of record: accounting, inventory, purchasing and payroll run on it. Replacing it shakes every process at once and resets the codes, rules and habits built into it over the years — while the problem is not in recording but in reading. The right question is: how do you build an intelligence layer on top of the existing record that reads it every day?
One morning, two companies
Consider a fictional example: two manufacturers in the same sector, of the same size, running the same ERP. Both keep complete records of orders, shipments, payroll and machines. In the first company, the managing director receives last month’s report on the tenth: revenue slightly below target, collections slightly longer, overtime slightly up. The report is accurate but late; behind every “slightly” is a story that began three weeks earlier, and by now only its consequences can be discussed.
In the second company, the same manager sees a short list every morning: three customers whose order intervals have stretched beyond the usual, a line losing efficiency on the night shift, two receivables past due and approaching the next threshold, a team whose absences have been rising for two weeks. Every line has an owner and a date. This company does not collect more data or run a more expensive ERP; it simply reads the same data every day. The difference is not in the system but in the rhythm of reading: one manages the past, the other manages today.
Five habits of the intelligent company
- Read without touching the source. Data stays in the ERP; the intelligence layer accesses it with read permission. No migration project, no double entry.
- Give every number one definition. If “revenue” is calculated one way in sales and another in finance, align the definition first; dashboards come second.
- Stop asking for reports, start receiving signals. A month-end report describes the past. A customer going quiet, collections stretching out, a machine losing efficiency should reach you every day on their own.
- Tie every alert to an owner and a date. An alert without an owner is noise; an alert with an owner and a deadline is work.
- Measure the loss before you invest. Before deciding on a new machine, new hires or new software, show with your own data where existing capacity is being lost.
Where to start making your ERP smarter: the first 30 days
You do not need a large transformation programme. In week one, pick a single decision you make every week — which customer to visit, say, or which order to prioritise — and write down which data you look at for it today. In week two, find where that data lives in the ERP, set up read access and align the definition of the number behind the decision with the departments involved.
In week three, set up the first daily signal for that number: decide which threshold puts it in front of whom. In week four, look back: how often did the signal arrive, how often did someone act, did the decision change? If yes, move on to the second decision; if not, the problem is usually not the data but the owner of the signal. At the end of the month you have not a dashboard but a working habit — and carrying it to the next area is much easier than the first.
The management style of a new era
Managing with data is not a software purchase; it is a management habit. Every morning the manager asks the same question — “what changed yesterday, and who needs to act on it?” — and the answer comes from data flowing out of the ERP, payroll and the shop floor. Absence and attrition signals in HR, order intervals in sales, equipment effectiveness in manufacturing, receivables ageing in finance, slow-moving items in inventory: all are faces of the same principle. In the coming weeks we will take these areas one by one, with sourced data.
Making a company smarter does not require tearing it down and rebuilding it. The data is already there; what is missing is the eye that reads it every day. The ERP keeps the record; intelligence turns the record into decisions.
Sources
- [1]Eurostat (2025). 20% of EU enterprises use AI technologies — accessed 9 November 2026
- [2]Eurostat (2025). Digital economy and society statistics – enterprises — accessed 9 November 2026
- [3]TÜİK (2026). Yapay Zeka İstatistikleri, 2026 (Sayı 62066) — accessed 9 November 2026
- [4]TÜİK (2025). Girişimlerde Bilişim Teknolojileri Kullanım Araştırması, 2025 (Sayı 54012) — accessed 9 November 2026
- [5]McKinsey & Company (2026). The state of AI in 2026: On the road to ROI — accessed 9 November 2026


