SMB process automation without an IT manager, what actually works

SME process automation without an IT manager: what actually works

Automating business processes in an SME without an in-house IT manager is possible and, in many cases, simpler than you might think. It means identifying the repetitive tasks that consume hours every week, such as managing emails, producing documents or tracking orders, and handing them off to custom-built automated workflows, without having to hire a full-time technician or overhaul the systems already in place.

The Italian SME market is going through a phase of accelerated transformation. According to research by the Osservatori Digital Innovation at the Politecnico di Milano, in 2026 more than 58% of Italian medium-sized companies had launched at least one digital automation project, yet fewer than one in three had a structured internal IT team. This gap between intention and technical capability is the real obstacle holding back growth: not a lack of budget, but a lack of a concrete method for getting started.

Why automation always seems like something for large companies

Business automation is perceived as a privilege of large enterprises because the most visible success stories involve organisations with dozens of in-house developers, multimillion-euro budgets and dedicated infrastructure. For an SME with 20 or 50 employees, that scenario seems out of reach.

The reality is different. Most of the processes that slow an SME down, manual data entry, quote generation, commercial follow-up, collecting documents from suppliers, do not require complex infrastructure. They require clarity about what you want to automate and a technical approach that does not depend on fragile or hard-to-maintain third-party tools.

The problem often stems from a misleading narrative: "digital transformation" is talked about as though it were a monolithic project to be tackled all at once. In reality, automation engineering applied to an SME works through small, measurable modules, each of which delivers a concrete result within a few weeks.

The profile of someone who gets stuck before they even start

Giulia runs a communications agency in Milan with 18 collaborators. She knows her team loses at least 6 hours a week copying data between the CRM and Excel spreadsheets for client reports. She has searched for solutions online and found no-code platforms, but stopped because nobody explained where to start without risking breaking something. Her problem is not technological: it is methodological.

The myth of the IT department as a prerequisite

Many entrepreneurs believe that automating first requires building a solid IT infrastructure, with servers, proprietary databases and in-house developers. In reality, most of the automations that are genuinely useful for an SME plug into systems that already exist, such as the management software, email, website or CRM, without requiring a migration or a technological overhaul. The prerequisite is not having an IT manager: it is having a documented process and a technical partner who can translate it into code.

What automation engineering for an SME actually means

Automation engineering applied to an SME is the discipline that transforms manual, repetitive processes into automated workflows, built to fit the specific characteristics of the business, without imposing standardised solutions that do not adapt to operational reality.

It is not about installing off-the-shelf software and hoping it works. It is about mapping how a process happens today, identifying the friction points, designing an alternative flow and implementing it with code written specifically for that company. This approach, based on pure code rather than third-party platforms, guarantees long-term stability, genuine customisation and independence from external service updates or shutdowns.

A well-designed automation for an SME has three characteristics: it is measurable (you know exactly how many hours it saves or how many errors it eliminates), it is maintainable (it does not require an expert every time something in the process changes), and it is scalable (it can grow with the company without needing to be rewritten from scratch).

The processes you can automate immediately, without touching IT infrastructure

There are categories of business processes that lend themselves to immediate automation because they are already digital, repetitive and well defined: automating them requires no changes to the existing infrastructure and delivers measurable results within a few weeks.

Before listing them, it is worth understanding the selection criterion. A process is a good candidate for automation when it recurs at least once a week, always follows the same steps, requires copying or moving data from one system to another, or frequently generates human errors with concrete consequences such as delays, customer dissatisfaction or data loss.

• Document generation: quotes, contracts, technical data sheets, periodic reports. Automation can produce them from data already held in the management system or CRM, reducing production time from hours to a few seconds.
• Lead qualification and routing: requests arriving from the website or by email can be categorised, enriched with data and assigned to the right sales person automatically, without anyone having to read every message manually.
• Commercial and post-sales follow-up: reminders, update emails, internal notifications. Flows that today depend on one person's memory can become reliable, traceable processes.
• Document collection and verification: supplier onboarding, gathering certifications, updating expiry dates. Processes that currently require dozens of manual emails.
• Data synchronisation between systems: between management software and e-commerce, between CRM and invoicing tools, between spreadsheets and internal databases.
• Monitoring and alerting: automatic notifications when a deadline is approaching, an order exceeds a threshold, or a key indicator deviates from the norm.

The case of Roberto, owner of a construction company

Roberto runs a construction company in Brescia with 35 employees. Before automating, drawing up a quote required 8 hours of work covering data collection, calculations and formatting the final document. After implementing a custom system, the same quote is generated in 5 clicks, with all the data already populated from the management software. The saving is not just in time: it is also in errors, because the calculations are carried out consistently every time.

How to implement a pure-code automation without an IT manager

Implementing a pure-code automation without an in-house IT manager requires a structured, phased method, where the entrepreneur's role is to describe the process and validate the result, while the technical partner takes care of everything else.

The typical process unfolds in four phases, each with a concrete, verifiable output. The first phase is mapping: the process is documented as it happens today, with all the steps, exceptions and systems involved. This phase, even if brief, is the most important because it defines the scope of the work.

The second phase is designing the automated flow: the process is redesigned by eliminating unnecessary manual steps and the logic the code will need to follow is defined. The third phase is development and testing: the code is written, tested against real cases and validated by the entrepreneur before going into production. The fourth phase is monitoring: during the first few weeks, the flow is checked to ensure it works as intended and adjustments are made.

1. Phase 1 (Mapping): document the current process with all its steps, the people involved and the systems used.
2. Phase 2 (Design): redesign the flow by eliminating redundant manual activities and define the automation logic.
3. Phase 3 (Development and testing): write the code, test it against real scenarios and validate it with the operational team.
4. Phase 4 (Go-live and monitoring): put the automation into production and monitor results during the first few weeks.

According to the Politecnico di Milano, Osservatori Digital Innovation 2026, SMEs that adopt custom automation solutions report an average 35% reduction in time spent on repetitive administrative activities within the first six months of use.

What the entrepreneur actually needs at this stage

The entrepreneur does not need to know how to code, nor to understand the APIs of the systems involved. They need to be able to describe the process in their own words, indicate what the starting data is and what the final result should be. Everything else, choosing the architecture, writing the code, integrating with existing systems, is the technical partner's responsibility. This is the model that works for SMEs: a clear division of roles, continuous communication and verifiable results at every stage.

Mistakes to avoid when implementing automation in an SME

The most common mistakes in SME automation are not technical but methodological: starting from the tool rather than the process, automating activities that are not yet standardised, or choosing a solution that is too rigid to adapt to the company's specific characteristics.

The first mistake is automating a chaotic process. If an activity is carried out differently by different people, or changes every week depending on circumstances, automation does not solve the problem: it amplifies it. Before automating, you need to standardise, at least in its essential lines.

The second mistake is relying on third-party no-code platforms that appear simple but create dependencies that are difficult to manage over time. When the platform provider changes its pricing, modifies features or shuts down the service, the automation stops working and the company has to start from scratch. Pure-code solutions avoid this risk because the code belongs to the company and can be maintained by any developer.

The third mistake is wanting to automate everything at once. The SMEs that achieve the best results start with a single high-impact process, measure the results and then expand. This approach reduces risk, keeps the team motivated and allows for progressive learning.

• Automating without standardising: an automated chaotic process produces chaos more quickly.
• Depending on third-party platforms: updates, shutdowns or pricing changes can bring the entire automation to a halt.
• Starting with an overly ambitious project: a small automation that works is better than a large project that never gets off the ground.
• Not involving the people who use the process every day: operational staff know the exceptions that no manager is aware of.
• Not measuring results: without clear metrics, you cannot tell whether the automation is delivering real value.

Measurable results: what to expect in the first 30 to 90 days

In the first 30 to 90 days after implementing a well-designed automation, an SME can expect concrete, measurable results: a reduction in the time devoted to the automated process, fewer operational errors and, in many cases, an improvement in the quality of service as perceived by customers.

Timescales vary depending on the complexity of the process and the quality of the initial mapping phase. A document automation, such as the automatic generation of quotes or contracts, can be up and running within 30 days and deliver immediate results. A more complex automation, such as integrating a CRM, management software and invoicing system, typically takes 60 to 90 days to become fully stable.

Carla runs a food distribution company in Bologna with 45 employees. Her sales team used to spend every Monday morning manually compiling weekly reports for area managers, an activity that took around 3 hours per person. After automating the reporting process, those reports are generated and sent automatically every Sunday evening, with data updated in real time. The 3 hours per person per week have been redirected to direct sales activities.

According to McKinsey Global Institute, in 2026 companies that implemented automations on administrative and document-based processes reported an average return on investment within the first 12 months, with particularly marked efficiency gains in organisations with fewer than 200 employees.

How to measure the return on an automation

The simplest and most reliable metric is the time saved per unit of process. If a quote previously required 8 hours and now requires 0.5, the saving is measurable in hours per week, multiplied by the hourly cost of the person involved. To this you add the value of errors avoided, such as rework, complaints and delays, and in some cases the improvement in response speed to the customer, which has a direct impact on the commercial conversion rate.

How Leomat helps SMEs automate without overcomplicating things

Leomat supports Italian SMEs in automating their business processes with an approach based on pure code and custom solutions, with no dependencies on third-party platforms and no requirement for an in-house IT manager on the client side.

The starting point is always the entrepreneur's concrete problem, not the technology. With 15 years of experience in the sector and 10 custom platforms delivered, Leomat has developed a method that begins with process mapping, designs the most suitable solution and implements it in pure code, guaranteeing long-term stability and full ownership of the solution by the client.

Among the documented results: a company in the parapharmaceutical sector reduced document generation times by 85% in 90 days, and a construction company transformed quote preparation from 8 hours to 5 clicks in 30 days. These results were not achieved with off-the-shelf tools, but with automations designed specifically for those companies' processes.

Leomat also offers the development of custom ERP systems for companies that need a management platform built around their own processes, not the other way around. For SMEs that want to understand where to start without immediately committing to a complex project, the first step is a direct conversation with the team: you can find all the information at leomat.it.

This post was created with AI

Frequently asked questions about process automation in SMEs

How much does it cost to implement an automation in an SME without an IT department?

The cost depends on the complexity of the process and the number of systems involved. In general, an automation covering a single well-defined process, such as automatic document generation or commercial follow-up, is affordable even for SMEs with limited budgets. The most important variable is not the initial cost but the return: an automation that saves 10 hours a week pays for itself within a few months. It is always advisable to start with a process analysis before evaluating any investment.

Is it possible to automate processes without changing the management software or other tools already in use?

In most cases, yes. Well-designed automations integrate with existing systems via APIs or direct database connections, without requiring migrations or replacements. The goal is to add intelligence to the flows already in use, not to overturn the infrastructure. This is one of the reasons why the pure-code approach is preferable to off-the-shelf platforms, which often impose constraints on compatible systems.

How long does it take to see the first results of a business automation?

For simple, well-documented processes, the first concrete results arrive within 30 days of the project starting. For more complex automations involving multiple systems or intricate conditional logic, the typical timeframe is 60 to 90 days. The initial mapping phase is decisive: the clearer and more standardised the process, the faster and more stable the implementation will be. There are no shortcuts, but with the right method the timescales are predictable.

How do I work out which of my company's processes are worth automating?

The simplest criterion is to look for activities that recur at least once a week, always follow the same steps and require moving data from one system to another. To these you can add activities that frequently generate errors or that depend on a single person's memory. A useful exercise is to ask your team members which activities they find most tedious and repetitive: these often turn out to be exactly the best candidates for automation.

Does automation put employees' jobs at risk?

The experience of SMEs that have implemented automations paints a different picture from the one that is feared: the hours saved are almost always redirected to higher-value activities, such as client relationships, business development or handling exceptions that require human judgement. Automation eliminates the most mechanical and frustrating part of the work, not the skills and relationships that make every company unique. For specific conditions relating to personnel management, it is always useful to consult a labour consultant.