An order arrives by email. You open the attachment, copy the references into your software, file the document then notify a colleague. The treatment seems short. Repeated every day, it ends up occupying slots that you would have devoted to a client or a more complex file. To automate the repetitive tasks of a small business, start with a specific path: information that enters, a few known rules and a verifiable result. You will thus be able to measure the usefulness of the device before extending it.
A real experience: emails transformed into orders at Tri-Énergie
In Bouaye, in Loire-Atlantique, Tri-Énergie operates in roofing and photovoltaics. In a testimony published by France Num in January 2026, its director Pierre Fruneau describes automation built with n8n and artificial intelligence functions.
The system locates orders in Outlook, extracts lines from PDF attachments and creates an order in the commercial software. It then classifies the message with an indication for processing. The manager and his collaborator report free time for construction sites, quotes and technical questions.
This feedback documents concrete use. The hourly volume announced in the transcription contains an ambiguity indicated by the source; we therefore retain the qualitative benefit, without repeating this figure. Read the France Num testimony, updated March 13, 2026.
Choose a task for which you already know the rules
For a week, note the repeated operations: downloading documents, transferring contact details, creating a file, updating a table. For each task, note the frequency, time spent and errors to correct.
The first candidate should be frequent, sufficiently stable and easy to control. A rare operation or one where the rules change depending on each client will be more difficult to make profitable.
Then describe the expected operation in one sentence: “When a document arrives in this file, prepare this sheet with this information. » If this sentence requires many exceptions, simplify the starting scope.
Prepare exceptions before connecting tools
An automation must also know how to stop. An unknown reference, an illegible attachment or a missing amount must produce a verification request. Have a clear list of items to review and designate the person who consults it.
At startup, have the recordings prepared before validation. Compare them with the original documents. This check makes it possible to discover real variations: different names for the same customer, duplicates, incorrectly presented quantities or modified orders.
Also define how to recognize a document that has already been processed. The same email forwarded twice should not create two orders. Keep a link to the source and a log of what happened.
Check that the time saved remains a gain
On a first batch, measure the total time: preparation, control and corrections included. Compare it to manual processing of similar documents. Also note incomplete recordings and necessary interventions.
These results will help you decide whether to continue, adjust a rule, or keep a manual step. Add to the balance sheet the cost of tools and their maintenance. A few minutes saved lose their value if the device requires disproportionate monitoring.
Once this first path has stabilized, you can consider the next one with concrete data on your activity.
Does your team spend too much time copying and filing? Present a recurring task and the relevant tools to ISS Agency to study automation adapted to your operation.
Transform reading into action.
An audit allows you to transform this idea into priorities adapted to your situation.
Automation: organize the follow-up of your requests →
Request the audit