CRM Consultant, Italy

Use the gestionale's CRM module or bring in a separate CRM?

This is usually the first real decision for an Italian company. The software house that supplies the gestionale often offers a CRM module or an agent app of its own. It shares the customer and item master, it already knows your price lists, and the supplier relationship is familiar. A separate CRM may offer better pipelines, mobile use, marketing tools and reporting, but it needs an integration and a clear rule about which system owns what.

I compare the two routes on your own scenarios rather than on brochures:

• Can an agent record a visit, check a customer's open orders and propose a new order from a phone in a few steps?
• Can a key account manager plan a retail chain negotiation with contacts at several levels?
• Can service history on an installed machine become a sales opportunity automatically?
• Can management see the pipeline by agent, region and product line without exporting to a spreadsheet?

Standalone options I typically score include Zoho CRM, HubSpot, Salesforce, Odoo CRM and Dynamics 365, depending on size and the systems already in place. Sometimes the module from the software house wins, and the project becomes one of process discipline rather than new software. Either way, the comparison is documented so owners can see why.

Agenti, orders and what the office needs back

Italian companies selling through agenti face a practical tension. The agent wants a tool that is quick to use between visits and protects their customer relationships. The company wants complete visit records, accurate orders and data it keeps when an agent leaves.

The design I propose separates three things:

• Visit and opportunity records belong in the CRM, entered by the agent on mobile, with short mandatory fields and voice or photo notes where useful.
• Order proposals from the agent are checked by the office for price, discount and credit status before they become confirmed orders in the gestionale or ERP.
• Commission statements and any contributions your advisor says apply are calculated in the ERP or by your commercialista, not in the CRM, which only supplies the sales data.

Agents see their own customers and products, plus open invoices and deliveries for those customers so they can answer questions on the spot. When an agent changes, history stays with the account and moves to the successor. I also define what the office sends back each week, such as new prices, stock alerts and overdue balances, because that flow is what persuades agents the CRM is worth using.

Retail chains, distributors and sell-out data

Italian food and consumer goods producers often sell to national and regional retail chains and to buying groups, alongside distributors for the foodservice channel and importers abroad. Each of these needs a different CRM view.

For retail chains, the CRM holds the yearly agreement, the listed products, the promotion calendar and the contacts at head office, regional buying centers and key stores. Opportunities cover new listings and promotional slots rather than single orders, since replenishment orders arrive through electronic order exchange or the gestionale and are not sales activity.

Distributors and importers are modeled as accounts with their own territories. Where they share sell-out data, I plan a regular import so management can compare what you sold in with what they sold on. The comparison is only as good as the product codes, so I agree a mapping table between your codes and theirs before the first report is built.

Reports then answer the questions an Italian sales director tends to ask: which chains grew, which listings were lost and why, which agents bring new customers rather than reorders, and which export markets justify more support. Companies in food and beverage and wholesale will recognize these reports.

Installed machines, service visits and the next sale

For Italian machinery and equipment makers, the most valuable sales signal is often in after-sales. A customer who calls for spare parts every few weeks, a line that is near the end of its useful life, or a plant that adds a shift are all opportunities, yet they usually sit in the service team's records and never reach sales.

I design an installed base model in the CRM:

• Each machine or system is a record linked to the customer site, with model, serial number, installation date and configuration notes.
• Service visits and tickets link to the machine, so sales can see its history before visiting.
• Spare parts and consumables orders are summarized per machine from the ERP.
• Triggers create a task for the account owner when a machine reaches an agreed age, when service calls cluster or when a contract approaches renewal.

Foreign dealers who install and service your machines abroad can be given limited access to update installation and service details for their customers. That fills a gap many exporters have: knowing what is actually running in each market. The rules on what dealers may see are written into the dealer agreement by your lawyer, and the CRM follows them. Manufacturing companies gain the most from this design.

PEC, consent and getting the data right from the start

Italian customer records carry details a generic CRM template ignores. The PEC address is one: it is a registered email channel with legal value, used for formal notices and, for some customers, for receiving electronic invoices. I store it in its own field, separate from ordinary email, so it is never added to a marketing list by mistake and is available to finance when needed. VAT number, tax code and recipient code are captured with format checks, because the invoicing system will need them later.

Consent follows the GDPR as interpreted by your data protection lead. The CRM records the source of each contact, the channels they agreed to, the date and the wording shown. If your team phones consumers or sole traders, ask your advisor how numbers must be checked against the national opt-out register; the CRM can store the check result and block calls without it.

Migration from the gestionale, agent spreadsheets and trade fair lists then follows agreed matching rules on VAT number and tax code, with sales managers reviewing a trial import. The work runs remotely, with sessions in hours that suit Italian teams and visits by arrangement. The system side of the order handoff is on my system integration consultant page for Italy, and the Italy overview lists the other services available to Italian companies.