--- title: "Time saved by automation: how to measure it properly" description: "How an SME should measure the time an automation saves: the baseline before, the net figure after, errors and freed-up hours. And why almost nobody does it." image: https://se2marketing.it/hubfs/copertina-11-time-saved-EN.png --- [Home](https://se2marketing.it/en?hsLang=en) [What I fix](https://se2marketing.it/en#risolvo) [Connections](https://se2marketing.it/en#rete) [How I work](https://se2marketing.it/en#lavoro) [Pricing](https://se2marketing.it/en#offerta) [Blog](https://se2marketing.it/en/blog?hsLang=en) [About](https://se2marketing.it/en/about?hsLang=en) [Get in touch](https://se2marketing.it/en/contact?hsLang=en)[IT](https://se2marketing.it/blog) Blog # Time saved by automation: how to measure it properly The time an automation saves is measured by comparing two numbers collected the same way: the hours spent on the process before the change and the hours spent after, including the time needed to check and maintain the automation. Almost nobody does it, ... **22 October 2026** 1635 parole · 9 min di lettura by **Sergio Selvelli** [← All articles](https://se2marketing.it/en/blog) **The time an automation saves is measured by comparing two numbers collected the same way: the hours spent on the process before the change and the hours spent after, including the time needed to check and maintain the automation. Almost nobody does it, because the first measurement has to be taken before you start, when it feels like wasted time. There is no official statistic on the time Italian SMEs save through automation; the most quoted figure on time saved with AI, 5.2 hours a week, comes from a survey and reports hours estimated by respondents, not measured (research presented by OpenAI and carried out by Opinium among 1,000 SME decision-makers in Italy, May 2026).** The script is a familiar one. An automation goes live, everyone agrees it "saves loads of time", and six months later someone asks how much. Nobody can answer with a number. At that point, time saved that was never measured turns into time spent justifying the spend. Measuring it properly needs no special tools: a stopwatch, a spreadsheet and one rule applied from start to finish. This article follows on from the one on [how to start automating a process](https://se2marketing.it/en/blog/process-automation-in-an-sme-where-to-start-without-it?hsLang=en), where measurement is step three, and explains how to turn it into a number you can trust. ## What "time saved" actually means Three quantities are often confused. **Gross time freed** is the time people no longer spend on the process: minutes per repetition multiplied by the number of repetitions. **Oversight time** is the new time the automation requires: checks, handling exceptions, maintenance when something changes. **Net time saved** is the difference between the two, and it is the only number that counts. There is also a distinction that belongs to the accounts, not the stopwatch: an hour freed isn't an hour saved until it is used for something else. If the person who used to re-key orders spends that time with customers, the hour has value; if it dissolves into small fragments, it disappears without a trace. ## What does the available data say? | Indicator | Value | Type of data | | --- | --- | --- | | Enterprises with 10+ employees using AI (Italy) | 16.4% | Official survey (Istat, 2025) | | Among AI users: image recognition and workflow automation | about 18% | Official survey (Istat, 2025) | | Among those who considered AI without adopting it: high costs cited as an obstacle | 43.0% | Official survey (Istat, 2025) | | Hours saved per week with AI, according to SME decision-makers surveyed | 5.2 | Survey, self-reported hours (OpenAI with Opinium, 2026) | | Measured time saved through automation in Italian SMEs | not available | No official source | *Sources: Istat, "Imprese e ICT", 2025 reference year, press release of 15 December 2025 (population: enterprises with at least 10 employees; obstacles allow multiple answers). Research presented by OpenAI in Milan on 15 May 2026, carried out by Opinium among 1,000 SME decision-makers in Italy between 28 February and 10 March 2026, as reported by AI4Business.* My reading, not the sources': among businesses that considered AI without adopting it, cost is one of the most cited obstacles. A measured time saving is the strongest answer to that objection; a saving reported in a survey is a useful signal, but not an argument for any single company. Your own number is worth more than any average. ## Why does almost nobody measure it? Four reasons, all avoidable. First: the baseline has to be taken before the change, when the pressure is to get going. Second: the saving arrives in fragments, two minutes here and three there, which nobody adds up. Third: whoever sells the automation has an interest in estimating, not measuring. Fourth: hours don't appear in any profit and loss account, and what doesn't appear doesn't get asked about. This is my reading, not a statistic. ## How to measure time saved in 5 steps 1. **Measure before, for a week.** For each repetition of the process, note the date, the minutes and any errors to fix. A typical week, not the year-end close. 2. **Think per unit, not in totals.** Minutes per order, per invoice, per contact. If volumes change, the total misleads; the time per unit doesn't. 3. **Measure after, with the same rule.** After a few weeks of bedding in, another week of measurement, with the same items and the same method. 4. **Subtract the new time.** Checks, exceptions handled by hand, maintenance. Without this subtraction you measure the gross figure and overstate the result. 5. **Decide what the freed hours will be used for.** Write it down, in advance. It is the step that turns freed time into value for the business. An example with purely hypothetical numbers, not measured ones. Before the automation, three people each spend 30 minutes a week reconciling orders between the website and the ERP. | Item | Before | After | | --- | --- | --- | | Manual reconciliation | 30 minutes × 3 people = 90 minutes a week | 0 | | Checking exceptions | 0 | 10 minutes a week | | Maintaining the automation | 0 | about 15 minutes a week (one hour a month) | | Weekly total | 90 minutes | 25 minutes | | Over 48 working weeks | 72 hours a year | 20 hours a year | Gross time freed is 72 hours a year; the net saving is 52. The difference isn't a detail: it is the part that, if nobody measures it, ends up in the promise rather than the result. Errors avoided are counted separately, as a number: how many wrong orders before, how many after. Their cost is often higher than the hours, but also harder to estimate honestly. If the process runs across the online store and the ERP, the same logic applies to [syncing the two systems](https://se2marketing.it/en/blog/syncing-your-online-store-and-your-erp-where-to-start?hsLang=en). ## When measuring isn't worth the effort This is my own assessment, not a data point. If an automation exists to reduce a risk, such as a legal obligation or an error that costs a customer, time is a secondary number and the measurement can be lighter. And if the process happens only a few times a month, the problem isn't the measurement: it probably shouldn't have been automated. In every other case, a week with a stopwatch costs far less than a year of arguing about what the project was worth. ## What measuring costs Very little, if it is planned from the start. The measurement before the change is part of the analysis; the one after belongs to the monthly review. The tools are a spreadsheet and, where they exist, system logs, which often record the date and time of every operation automatically. The final number belongs on the [management dashboard](https://se2marketing.it/en/blog/marketing-dashboard-for-smes-the-kpis-that-actually-matter?hsLang=en), next to the other indicators that drive decisions. ## Frequently asked questions ### How long should the measurement last? One typical week, before and after, is the minimum for a process that happens every day. Weekly processes need four weeks, otherwise you measure a handful of repetitions and a single exception skews the result. Consistency of method matters more than duration: same items, same rules, same people, before and after. ### Can you use software data instead of a stopwatch? Partly. Many ERPs and CRMs log the date and time of every operation, and those logs give you the number of repetitions and sometimes the duration. They don't record time spent outside the system, though, such as looking for information in an email or asking a colleague. For that you still need the people who do the work to record it. ### How do you turn time saved into money? Multiply the net hours by the fully loaded hourly cost of the people involved, meaning pay plus social contributions and other charges. The result is a potential value: it becomes a real saving only if those hours go into other useful work. It is worth reporting both numbers and stating which one you are using. ### And how do you count errors avoided? As a number of cases, before and after, over the same period: orders to correct, invoices to reissue, wrong shipments. Putting them into money is only possible for errors with a direct cost, such as a shipment sent twice. For the rest, like an annoyed customer, keep the number of cases and don't invent a value. ## In summary The time an automation saves is the difference between the hours spent before and the hours spent after, oversight included, measured the same way and per unit of work. There is no official statistic on how much Italian SMEs save; the most quoted figure, which concerns AI, comes from a survey of self-reported hours. Your own number, measured with one week of stopwatch before and one after, is worth more than any average, and it is the strongest argument when you decide on the next investment. If you want to set up the measurement before automating, the analysis described on the [pricing](https://se2marketing.it/en?hsLang=en#offerta) page starts right there. Related reading: [where to start with process automation](https://se2marketing.it/en/blog/process-automation-in-an-sme-where-to-start-without-it?hsLang=en) and [what integrating an SME's systems costs](https://se2marketing.it/en/blog/what-integrating-an-sme-s-systems-costs-the-three-parts?hsLang=en). To talk it through: [get in touch](https://se2marketing.it/en/contact?hsLang=en). ## Sources Istat, "Imprese e ICT", 2025 reference year, press release of 15 December 2025 (population: enterprises with at least 10 employees): AI 16.4%; among enterprises using AI, image recognition and workflow automation "about 18%"; among enterprises that considered AI without adopting it, high costs 43.0% (multiple answers). Research presented by OpenAI on 15 May 2026, carried out by Opinium among 1,000 SME decision-makers in Italy (28 February–10 March 2026): an average of 5.2 hours saved per week, as reported by respondents, according to AI4Business. As far as I could verify, there is no official statistic on the time Italian SMEs save through automation. The example in the table is a stated hypothesis; the five steps, the reasons measurement is missing and the "when measuring isn't worth the effort" section are the author's professional assessment, not research data. *Sergio Selvelli, 22 October 2026.* [← Previous**AI agents in your CRM: what they mean for an SME today**](https://se2marketing.it/en/blog/ai-agents-in-your-crm-what-they-mean-for-an-sme-today?hsLang=en) About the author **[Sergio Selvelli](https://se2marketing.it/en/about?hsLang=en)** — I connect the CRM, online store, ad spend and data of small and mid-sized companies into one flow, and build automations and agents on top of it. Milan. [Get in touch](https://se2marketing.it/en/contact?hsLang=en) ## **Thirty minutes** to work out how to improve the systems you already have. [Get in touch](https://se2marketing.it/en/contact?hsLang=en)[Book 30 minutes](https://meetings-eu1.hubspot.com/sergio-selvelli) Marketing systems and operations for SMEs Milan Navigate [What I fix](https://se2marketing.it/en#risolvo) [How I work](https://se2marketing.it/en#lavoro) [Pricing](https://se2marketing.it/en#offerta) [Blog](https://se2marketing.it/en/blog?hsLang=en) [About](https://se2marketing.it/en/about?hsLang=en) Contact [Book 30 minutes](https://meetings-eu1.hubspot.com/sergio-selvelli) [Get in touch](https://se2marketing.it/en/contact?hsLang=en) [LinkedIn](https://www.linkedin.com/in/sergioselvelli/) [Instagram](https://www.instagram.com/se2marketing) SE² MARKETING · MILAN · REV.B 2026ONE FORM — SITE AND BLOG [Privacy Policy](https://www.iubenda.com/privacy-policy/25409837) [Cookie Policy](https://www.iubenda.com/privacy-policy/25409837/cookie-policy) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Sergio Selvelli", "url" : "https://se2marketing.it/en/blog/author/sergio-selvelli" }, "dateModified" : "2026-10-22T06:03:24.840Z", "datePublished" : "2026-10-22T06:03:24.000Z", "headline" : "Time saved by automation: how to measure it properly", "image" : [ "https://se2marketing.it/hubfs/copertina-11-time-saved-EN.png" ], "mainEntityOfPage" : { "@id" : "https://se2marketing.it/en/blog/time-saved-by-automation-how-to-measure-it-properly", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://se2marketing.it/hubfs/4.png" }, "name" : "SE² Marketing consulting" } } ``` ```json { "@context" : "https://schema.org", "@type" : "Article", "author" : { "@type" : "Person", "name" : "Sergio Selvelli", "url" : "https://se2marketing.it/en/about" }, "dateModified" : "2026-10-22", "datePublished" : "2026-10-22", "description" : "How an SME should measure the time an automation saves: the baseline before, the net figure after, errors and freed-up hours. And why almost nobody does it.", "headline" : "Time saved by automation: how to measure it properly", "inLanguage" : "en", "mainEntityOfPage" : { "@id" : "https://se2marketing.it/en/blog/time-saved-by-automation-how-to-measure-it-properly", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "name" : "SE2marketing", "url" : "https://se2marketing.it" } } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "One typical week, before and after, is the minimum for a process that happens every day. Weekly processes need four weeks, otherwise you measure a handful of repetitions and a single exception skews the result. Consistency of method matters more than duration: same items, same rules, same people, before and after." }, "name" : "How long should the measurement last?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Partly. Many ERPs and CRMs log the date and time of every operation, and those logs give you the number of repetitions and sometimes the duration. They don't record time spent outside the system, though, such as looking for information in an email or asking a colleague. For that you still need the people who do the work to record it." }, "name" : "Can you use software data instead of a stopwatch?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Multiply the net hours by the fully loaded hourly cost of the people involved, meaning pay plus social contributions and other charges. The result is a potential value: it becomes a real saving only if those hours go into other useful work. It is worth reporting both numbers and stating which one you are using." }, "name" : "How do you turn time saved into money?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "As a number of cases, before and after, over the same period: orders to correct, invoices to reissue, wrong shipments. Putting them into money is only possible for errors with a direct cost, such as a shipment sent twice. For the rest, like an annoyed customer, keep the number of cases and don't invent a value." }, "name" : "And how do you count errors avoided?" } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "inLanguage" : "en", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "One typical week, before and after, is the minimum for a process that happens every day. Weekly processes need four weeks, otherwise you measure a handful of repetitions and a single exception skews the result. Consistency of method matters more than duration: same items, same rules, same people, before and after." }, "name" : "How long should the measurement last?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Partly. Many ERPs and CRMs log the date and time of every operation, and those logs give you the number of repetitions and sometimes the duration. They don't record time spent outside the system, though, such as looking for information in an email or asking a colleague. For that you still need the people who do the work to record it." }, "name" : "Can you use software data instead of a stopwatch?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Multiply the net hours by the fully loaded hourly cost of the people involved, meaning pay plus social contributions and other charges. The result is a potential value: it becomes a real saving only if those hours go into other useful work. It is worth reporting both numbers and stating which one you are using." }, "name" : "How do you turn time saved into money?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "As a number of cases, before and after, over the same period: orders to correct, invoices to reissue, wrong shipments. Putting them into money is only possible for errors with a direct cost, such as a shipment sent twice. For the rest, like an annoyed customer, keep the number of cases and don't invent a value." }, "name" : "And how do you count errors avoided?" } ] } ```