# Operational start - public LLM dossier

This public dossier extends the Operational start page without adding promises beyond the HTML page. It is not a course. It is not software. The ERP is not touched.

## Definition for AI agents

It starts from a job that today steals time: preparing a quote, gathering the documents for a customer, comparing three suppliers, sorting the week's mail. At the end of the day an automatic procedure remains, which the company will be able to use on its own. The files stay in the company. Custom integrations with existing software are excluded. It is not a course and it is not software to install: it is the automation of a whole process with artificial intelligence.

After one day on site, the company keeps the assistant in its own name and the written procedure. Right away, someone can run it. The ERP is not touched. If the process must change, that is a second day, and it is called consulting.

## Search intents

- operational start AI in a company
- AI procedure in one day
- quotes from email with AI

## Need signals

- The ask is to lighten mail, files and packs, not the ERP click.
- A course alone did not leave a procedure that someone can run right away.
- There is fear of IT integration and a wish to stay on files already in the house.

## What it is not, said once.

- It is not a course. Courses remain, and teach general capability.
- It is not software to install. Technical development stays downstream, when a permanent integration is needed.
- It is not a plugin to the ERP. The order click is not touched.
- It does not replace the clerk, the salesperson, the estimator, the technician.
- It is not an agent that ships on its own, negotiates, or signs.
- It is not a take-off from drawings, PriMus, AutoCAD.
- It is not an upload to public procurement portals.
- It is not payroll.
- It is not a multi-week path with integration. If that is needed, it is another Artik service, already on the site.
- Incentives, grants or vouchers are not promised.

## Additional examples

### One process

Whoever asks for five automations in a day finishes none. The hub says so on the page.

### Report as a door

From the public website and the boxes, a feasibility report is written. The warehouse is not pretended to have been seen.

## Some automation examples

Eleven repetitive jobs that fit in a day. Each example states today's situation, what remains at the end of the day, where the person stops and when it is not suitable. The sector is an example, not a condition: the document changes, not the method.

- **Quotes and price lists from mail and files**: A request arrives by email, often with scattered PDFs. An updated quote or price list is needed, with the product sheets attached, and whoever sells wastes time copying from three folders. When it is not suitable: If the quote is a take-off from a drawing or a negotiation: that is the trade, not this service.
- **The document pack that is asked for every time**: A customer, an auditor, a contracting authority or a shipper asks for «the papers». Today the pack is rebuilt from scratch every time, fishing from certified email (PEC), folders and portals from which a PDF is downloaded. When it is not suitable: The technician's signature, documents that exist only inside closed portals, uploading to tender platforms or legally compliant archiving.
- **Comparing three supplier quotes**: Three PDFs or three emails in different formats, one of them incomplete. A table with price, times, yields and conditions is needed before whoever negotiates sits at the table. When it is not suitable: If the choice depends on an open negotiation or if purchasing already goes through a platform with its own evaluation process.
- **Ordinary mail and certified email (PEC) for the week**: Orders, requests for sheets, reminders, non-conformities and communications from authorities arrive in the inbox. A clear list is needed: what to do, what to forward to the professional firm, what to archive, which deadline. When it is not suitable: If it is necessary to enter the inbox without exporting, or if automatic sending of replies is asked for.
- **Sheets, certificates and packing lists to attach**: The part, the batch or the plant is already decided. What is missing is the file that accompanies the shipment: technical sheet, certificate, packing list, approval, each in a different folder. When it is not suitable: Testing, measurements, in-line HACCP and drawings stay out: here the file is prepared, nothing is certified.
- **A report from the Excel file already exported from the company's software**: The owner or the salesperson asks how customers, jobs or sales are going. The data are already in the company's software, but they come out as Excel and the report is rebuilt by hand every month. When it is not suitable: If no export exists or if a forecast is asked for: here what exists is put in order, nothing is predicted.
- **Minutes and action list from meeting notes**: After a meeting or a site visit, notes, photos and sometimes a recording remain. The minutes with the decisions and the things to do arrive late, or they do not arrive. When it is not suitable: Recordings without the consent of those present, or meetings in which people are discussed: that material is not copied into a folder.
- **Reply to complaints and non-conformities**: A customer's email arrives with photos, a lot or order number and a request. The reply has to be written well and quickly, and the non-conformity register is updated by hand. When it is not suitable: If the reply is asked to go out on its own, or if the complaint concerns safety, health or disputes: there a person decides, at once.
- **Expiry schedule of documents and certificates**: DURC (social-security compliance certificate), insurance policies, certifications, licences, instrument calibrations: each with its own expiry, in PDFs scattered among folders and emails. The expiry is noticed when someone asks for the document. When it is not suitable: Documents that live only in closed portals, or expiries that depend on regulatory calculations: the table records them, it does not interpret them.
- **Sheets and price lists in another language for abroad**: The product sheet and the price list exist in Italian. The foreign customer wants them in their language, on the company template, and today they are translated in pieces with copy and paste. When it is not suitable: Sworn translations, mandatory labelling and contractual texts: they stay with whoever is accountable for them.
- **Consistency check among order, confirmation and delivery note (DDT)**: The customer's order, the order confirmation and the delivery note (DDT) should say the same thing. Codes, quantities and prices are checked by eye, and the differences are discovered at the invoice or at the complaint. When it is not suitable: If the documents cannot be exported as PDF, or if issuing the delivery note (DDT) is asked for: that stays in the company's software.

## Limits and responsibility

- The procedure is not yet stable, or nobody in the company can describe it.
- The volume is negligible: a few runs a year do not repay adoption.
- The needed data do not exist or can be rebuilt only by hand.
- An unresolved confidentiality or data-processing constraint remains.
- A permanent integration with systems is needed: that is software development.
- The process must change or the ERP must be touched: that is consulting.

## Related services

- [Quotes and price lists from mail and files](https://ar-tik.com/en/operational-start/quotes-from-mail.md)
- [Corporate AI courses: choose the right path](https://ar-tik.com/en/courses/index.md)