The team wants fewer spreadsheets. The owner wants better visibility. Someone suggests new software. These may all be reasonable wishes, but none yet explains which piece of work needs to improve. A smaller starting point makes it easier to see whether a digital change actually helps.
Choose one piece of recurring work
Pick a task that happens often enough to observe: preparing a quotation, collecting job information or handing a completed assignment to invoicing. Describe where it starts, where it ends and who is involved. Avoid beginning with “digitalize the company”.
In an illustrative service business, quotation preparation slows down because site details arrive in separate messages. The first improvement might be a shared job record and a short preparation checklist. Replacing the entire customer system is not automatically necessary.
Understand the delay before automating it
Watch a few real cases. Note where someone waits, copies information or asks again for a missing detail. Talk to the people doing the work. An apparently slow employee may be waiting for a decision nobody owns.
Fix responsibilities and required information before adding automation. Otherwise you can move incomplete work faster without making it usable. A reminder is helpful only when the recipient knows what decision or action is expected.
Use what you already have, where it is suitable
Check whether existing tools can support the agreed process. A shared record with a responsible person, clear access and a consistent status may be enough for the first test. Keep customer information out of uncontrolled personal accounts.
Simple does not mean careless. Decide who may read and change the information, where it is stored and how it is recovered. Where sensitive data or legal obligations are involved, obtain appropriate advice rather than improvising a solution.
Set a practical test of improvement
Define success before the change. For a quotation task, compare the time spent assembling information, the number of missing details and the rework needed. Use comparable jobs and record exceptions so a single easy case does not tell the whole story.
Do not promise a percentage saving before you have evidence. Ask whether the work is easier to complete and whether the people involved can rely on the result. If the test fails, adjust the process rather than buying more features to cover it up.
Expand only after someone can maintain it
A useful test still needs an owner. Decide who updates fields, resolves mistakes and introduces new colleagues to the agreed process. Without that responsibility, even a small improvement can decay into another inconsistent spreadsheet.
Once the first task works reliably, consider the next handoff. Extend the solution where the evidence supports it. The aim is not to accumulate tools. It is to make ordinary work dependable enough that the business does not need constant personal intervention.
What should improve first in your business?
Start with your actual situation. The free Digital Readiness Check helps prepare a conversation about a practical next step.
Start your free Digital Readiness CheckSources and editorial references
Original editorial analysis by Hasan Hasić, prepared on November 9, 2026 for this retrospective monthly series. The edition month is not a historical publication date. Examples are illustrative, not measured client outcomes. No external studies or statistics are used. Any third-party rights remain with their owners.
Hasan Hasić
Hasan Hasić is the founder and a Business Advisor at wis.dom|bridge™. He helps established businesses connect clear responsibilities, reliable workflows and practical digital improvements.
