Digitalisation in SMEs: where to start, why it stalls

Example scenario: Picture a packaging supplies firm in Gaziantep. Sales runs on WhatsApp, quotes in Word, collections in Excel, attendance on a device, and files in a shared folder. One day management decides to digitalise, and one more piece of software is bought. Each tool does its own job, and none knows about the others. The clutter does not shrink; another layer is added on top.

The second reason becomes clear from the team's point of view. Instead of making the work easier, the software has added one more task: first reply to the customer on WhatsApp, then enter the same information into the system. A few weeks later nobody enters anything, because the second entry has got in the way of the real work. What looks like a lack of training is really a design problem.

The third reason is the order of decisions. Software is chosen at a trade fair, on an acquaintance's recommendation, or during a promotion, and which task it should solve is considered afterwards. When the tool arrives before the problem is defined, the team does not know what to use it for either.

The company that tries to change everything at once and the company that never starts end up in the same place: a stalled project and a tired team. The better path is to choose a single flow. These questions help with the choice:

• Which task repeats the same way every week?
• Which task loses a customer or money when it is forgotten?
• Which information is written in two separate places today?
• Which question does the manager ask everyone, one by one, every morning?

What the questions have in common is finding the task that repeats every week and loses a customer or money when it is forgotten. In most companies these questions lead to quote follow-up: a price question comes in, a quote goes out, a reply is awaited, and the follow-up depends on someone remembering. If you plan to tackle quote follow-up on its own, we set out the criteria for choosing software in how to choose quote tracking software.

For a salesperson, the easiest record is the one they never enter separately. If replying on WhatsApp files the conversation on the card, sending the quote updates the opportunity, and passing the device records attendance, the team has nothing new to learn; they just do their work.

The manager's role changes too. Instead of asking in the meeting whether everyone has entered their data, they look at the same list as everyone else each morning. If the list is right, the team trusts it, and it keeps the list it trusts up to date. A team does not take to a system on a training day; adoption comes with that mutual trust. A suggestion: do not add the second flow until the first has settled. A habit forms quickly but breaks easily; if two new flows arrive at once, the team half-uses both.

At some point in any digitalisation conversation the questions arrive: whose server will the data sit on, where will the personal data of staff and customers go, what happens to the records if the software company changes? When the answers stay vague, the decision stays vague, and the project is put off. That is why hosting, backups, updates, and data export should be written into the contract from the start. Guides for companies that process personal data are published on the guides page of Turkey's Personal Data Protection Authority; looking at it before sitting down to the contract sharpens the list of questions.

You can read about the difference between the cloud and your own server, and where personal data sits, in cloud or your own server under KVKK (Turkey's data protection law); here we only draw attention to timing.

In Corex360, WhatsApp and Instagram are gathered in one inbox, and company email and phone calls link to the same customer card. The quote and the contract sit on the same customer card; the signed document stays tied to the record in Corex Drive. The attendance device connects to the core; leave and advance requests go through an approval flow.

The start is a single rule. X AI follows the rule-bound work, and when a rule breaks it opens a task and assigns an owner. For the first rule, the questions that look for work that repeats and costs money when forgotten point to quote follow-up in most companies; once the habit settles, the second rule follows. Every morning X AI gives you one list of what it did, what is waiting, and what it is asking you; on decisions about money, contracts, and people it stops and asks.

Back to the packaging firm in Gaziantep. Quote follow-up is chosen as the first flow. A price question from WhatsApp lands on the card and the quote is prepared there; if no reply comes, X AI puts a reminder at the top of the list and it goes out with the salesperson's approval. The manager looks at the same list each morning. Accounting and HR records join the same core once this flow has settled.

We move your existing customer and contact list over together with you. Setup runs in a company-specific space on Corex360 Cloud or on your own server; the same security layer applies in both cases.

Not every company needs business software today. In a business where the owner talks to customers directly, sends invoices to an outside accountant, and has a team of a few people, a well-kept ledger or spreadsheet can do the job. If scattered records are not the problem, digitalisation does not solve anything; it creates new work.

One more point: digitalisation is not a project that is done once and finished. Once the first flow settles, the second follows, and then the third. At every step the question is the same: which information is still being written in two places?

Where processes cannot be described, a conversation comes first. Who approves a quote, who holds discount authority, whom is leave requested from: if these are not written down, software only speeds up the uncertainty. If the answers are clear, in the demo we list together the tools you use today and the information you write twice, and set up the first flow on screen with your own data.