The working days hidden inside your business

The price of new software is visible in a proposal. The price of the current process is harder to see: a few minutes searching, two calls about an appointment, a report prepared again. These do not arrive as separate invoices. They become part of the working day and eventually feel normal.

The management question is how much of that repetition is unnecessary. Automation becomes a useful investment discussion when you can identify the work it reduces, the conditions needed and what will happen to the time released.

A calculation you can inspect

Consider an illustrative example. Six employees each spend 45 minutes per working day on repeated administration, across 22 working days a month. That totals 99 hours. If redesigning the process reduced the same task to 15 minutes per person per day, the difference would be 66 hours a month. These are assumptions, not measured results from a Nuxa client.

At an assumed fully loaded productive-hour cost of HUF 6,000, those hours represent HUF 396,000 of monthly capacity value. This is not automatic cash saving, revenue or guaranteed profit. Payroll may stay exactly the same after a task becomes faster.

Value depends on what happens next

A team might handle more enquiries promptly, reduce overtime or postpone an additional hire as demand grows. Another company may value more predictable scheduling and faster management visibility. These are different outcomes and need different measures.

Include the proportion of freed capacity that can actually be used. Scattered minutes do not always combine into uninterrupted customer work. Changing how work is organised can matter just as much as the software itself.

Time saving becomes a management outcome when you decide in advance what to do with it.

Bring the full cost into the decision

Alongside development, include data cleaning, migration, training, integration and the temporary effort of running old and new processes together. Later costs can include hosting, subscriptions, support and changes. Leaving these out produces a calculation about only part of the investment.

The OECD’s 2026 D4SME survey identifies time constraints, maintenance costs and skills gaps among implementation barriers. It studied a non-representative sample of more than 2,000 SMEs across twelve countries. Its findings should not be presented as national adoption rates for Hungary. OECD

Start with a bounded pilot

Choose a recurring process with regular steps and relatively few exceptions. Measure the current position. Before building, agree which results would justify continuing, changing course or stopping the rollout. A credible pilot can reveal that an existing tool configured properly is sufficient.

• Working time: how much active effort does a case require?
• Elapsed time: how long does it take from arrival to completion?
• Quality: how often must information be corrected or requested again?
• Adoption: are colleagues actually using the new process?

Compare the results under similar demand and case mix. A quiet month is not, on its own, evidence of improvement. Look at delayed cases as well as averages. A system may create value by making a blockage visible early enough to act.

Keep a short exception log during the pilot. Cases that do not fit the normal path reveal where the design needs flexibility. Ask the people using the system which tasks became easier and which became harder. This makes it possible to distinguish real simplification from work merely moved to another colleague.

A useful investment question is specific

Ask which recurring task could be reduced so the team can do more valuable work, and how you will recognise that result. That answer can support a proportionate development plan. A cautious calculation using your own data is a stronger starting point than an impressive universal percentage.