Background & Opportunity
Gusti d’Italia’s transformation began with a practical operating problem: its international food and beverage export activity had outgrown a collection of manual routines. Established in 2009 and located in Moncalieri near Turin, the company serves overseas customers with Italian products across branded foods, organic products, condiments, coffee, chocolate, pasta, and preserved foods. It works through supplier relationships and export-management capabilities. CRMpartners describes the business as operating in more than 60 countries. That breadth created a substantial coordination requirement, because international export management involves more than finding customers. It requires handling customer information, product and supplier details, transport activity, after-sales questions, follow-up commitments, and documentation associated with cross-border shipments. Before the project, these activities were not consistently organized in one connected workflow. Leads arrived through the website, Alibaba, and trade shows. Other work involved transport tracking, customer follow-up, after-sales administration, and AEO-related customs documents. The available facts do not suggest that the company lacked capable people. Instead, the process required people to compensate for disconnected information. Staff searched for files, copied information between locations, remembered follow-up actions, and reconstructed the status of a customer or shipment when questions arose. Manual and Excel-based management could support individual tasks, but the overall export process remained dependent on personal effort and repeated administrative intervention. The cost was visible in after-sales work. CRMpartners’ case material says that after-sales administration consumed about 6–8 hours each week before implementation. Transport tracking and customs-file retrieval were also dispersed manual processes. Customs documentation depended on repeated copying and pasting, and the case describes preparation as work that could require a full day. Such work is necessary, but much of it is repetitive rather than relationship-building. When employees spend recurring hours locating information or reproducing data, the organization has less capacity for timely customer response, proactive follow-up, and expansion of international activity. This created a scaling risk. Adding customers, countries, products, or shipments could increase administrative effort faster than commercial value. A manual process may appear manageable at limited volume, but it becomes less reliable as exceptions, follow-up requests, and documentation needs multiply. Management can lose visibility even when employees are working hard. It can also become difficult to distinguish a pending customer action from a transport issue or a document that still requires verification. The issue was therefore not simply speed. It was the absence of a shared operating structure connecting the commercial and administrative parts of export work. Gusti d’Italia responded by adopting Zoho CRM as the central system for export management and integrating it with the existing Zucchetti management software. CRMpartners implemented the project with Gusti d’Italia management participating. The intended solution was not a stand-alone customer database. It was designed to connect activities that already shaped the export process. Leads from the website, Alibaba, and trade shows could enter a common customer-management environment. Customer information could be related to export activity and follow-up tasks. Transport and after-sales information could be handled as part of an ongoing workflow rather than as isolated reminders or searches. The design also included Zoho Campaigns. The verified facts describe its use for customer-care and marketing processes based on customer history or previous purchases. This made follow-up more structured and more relevant to the relationship already established with a customer. For a business offering multiple categories and brands, customer history can help organize the next contact instead of relying on a generic message or employee memory. The case does not provide campaign conversion, response, or revenue figures. The supported conclusion is therefore that the company created a history-based follow-up process, not that campaign activity produced a measured sales increase. The most tangible change occurred in customs-file preparation. After the Zoho CRM and Zucchetti integration, the system automatically populated about 60% of the data required for customs files. This reduced repeated entry and the need to search manually for information already held in company records. It did not mean that all customs work became automatic. Remaining information still required attention, and documentation still required checking. In a cross-border food business, human review remains important because a prefilled field is not automatically a verified field. The achievement was a reduction in repetitive preparation and a better starting point for completing documentation. The reported results show several layers of operational impact. About 60% of customs-file data could be populated automatically. Reporting time decreased by 50%, and CRMpartners reported a 40% improvement in after-sales-management efficiency. The case page also described automated workflows being managed across 65 countries. Together, these figures suggest that the project was applied across the international operating model rather than limited to one local sales team. They also show why integration mattered more than simply installing a CRM. Value came from moving data and tasks through a connected process including customer management, administration, reporting, and customs preparation. The numbers must nevertheless be interpreted carefully. The case materials are a service-provider account of the project. Public sources do not provide independent auditing, original system screenshots, a precise implementation date, a clearly defined measurement period, or the underlying calculation for every percentage. The reported 40% improvement should therefore be treated as a case-reported operational indicator. The 50% reduction concerns reporting time, not necessarily total operating cost. The 60% figure concerns automatic customs-data population, not full customs compliance. None of these figures should be restated as a 40% increase in revenue, orders, profit, or market share. The country figures require the same discipline. The case describes Gusti d’Italia as exporting to more than 60 countries. It separately states that automated workflows were managed across 65 countries. These are different measures. The first describes international reach according to the case material; the second describes the geographical scope of automated workflows. It would be inaccurate to say that the system expanded the company from 60 to 65 countries or that the two numbers measure the same commercial outcome. A careful reading preserves both facts while keeping their meanings distinct. The process advantage created by the project is best understood as reduced coordination friction. A shared system can make it easier to see which customer came from which channel, what follow-up is due, which after-sales issue remains open, and what information is available for a customs file. It can reduce the number of times employees reproduce information already held elsewhere. That creates a more repeatable operating model. Repeatability matters in international trade because customers, destinations, product combinations, transport events, and documentation requirements vary. A common workflow does not remove complexity, but it makes complexity easier to manage consistently. Integration also changes organizational dependence. Under a fragmented process, knowledge may sit with the employee who knows where a file is stored or remembers what happened on a previous shipment. Under a connected process, more knowledge can be represented in records, tasks, and workflows. This does not eliminate experienced people. It allows their judgment to be applied to exceptions and customer decisions instead of routine retrieval and transcription. The effect is especially relevant to after-sales management, where response quality depends on context. A history-based customer record can make a response more informed than a search through disconnected files. Automation is not self-sustaining. Outcome quality depends on the underlying data, the design of the Zoho CRM–Zucchetti integration, and whether employees consistently use the workflow. Fields must be mapped correctly, duplicates controlled, and customer and product information kept current. Tasks must be assigned and closed. Customs data must be reviewed before documents are relied upon. The verified case does not disclose implementation cost, training, maintenance workload, employee count, or payback period. Those remain open questions for organizations considering a similar investment. The business context creates additional strategic considerations. Gusti d’Italia manages Italian food and beverage products through suppliers and serves international customers. Supplier brands and products may be substitutable, while cross-border food compliance and AEO-related processes create operating requirements. Overseas distributors may have negotiating power, and the company may depend on several acquisition channels. Better CRM and operational integration can help retain customer knowledge and improve responsiveness, but it does not eliminate product competition or distributor pressure. The system supports execution; it is not a substitute for a strong portfolio or reliable supplier relationships. The project may create process knowledge that becomes more valuable over time. Correctly managed interactions improve visibility into customer history, follow-up, export administration, and recurring documentation. This knowledge can support more consistent service across countries and channels. CRM software is widely available, so the tool itself is not impossible for competitors to copy. The harder element to copy may be the company-specific configuration, data discipline, workflow learning, and accumulated operating knowledge. That advantage remains conditional on continued use and accurate information. Gusti d’Italia’s official materials also state that the company became a Società Benefit on December 5, 2024. This is a separate governance development and should not be presented as a result of the CRM implementation. It indicates that the company formally included social and environmental impact objectives in its governance framework. Available facts do not identify a connection between that status change and the Zoho project, nor do they provide a quantified environmental or social outcome from the digital workflow. Keeping the developments distinct preserves the credibility of the case. For management, the practical lesson is to define the problem in operational terms before selecting software. The baseline was about 6–8 hours of weekly after-sales administration, full-day-style customs copying and pasting, fragmented transport tracking, and scattered customer information. The solution connected specific activities to those problems. The reported results were similarly operational: about 60% automatic data population, 50% less reporting time, and 40% better after-sales efficiency. Future evaluation should continue measuring those direct effects while separately tracking financial outcomes if they become available. The case therefore offers a measured model for digital export transformation. Start with recurring work that consumes time and creates coordination risk. Connect existing systems rather than creating another isolated repository. Automate repeatable preparation while keeping human review for compliance-sensitive information. Use customer history to make follow-up more structured. Measure time, data population, and workflow efficiency directly. Finally, do not claim revenue or profit growth unless independently supported. Gusti d’Italia demonstrates that a food exporter can make international administration more connected and scalable through CRM and management-software integration. Its strongest evidence is operational, and that is sufficient to show why the decision mattered without overstating what the sources prove.
Original Problem / Model
Gusti d’Italia’s starting point was a fragmented export process. Leads came from the website, Alibaba, and trade shows, while transport tracking, after-sales work, and customs documentation were handled through dispersed manual routines. Excel, file searches, repeated copying and pasting, and remembered follow-ups connected the activities. The result was administrative dependence on individual effort rather than a shared operating view. The case reports that after-sales administration required about 6–8 hours every week. Customs-file preparation could also consume a full day of repetitive work, creating a clear obstacle to scaling international activity without proportionally increasing administrative burden.
Turning Point
The company chose Zoho CRM as the core export-management system and integrated it with Zucchetti. CRMpartners implemented the project with Gusti d’Italia management involved. The design connected customer acquisition, export operations, transport information, after-sales tasks, customs data, and reporting. Zoho Campaigns added history-based customer care and marketing follow-up. The important decision was integration, not merely adding a new CRM. Existing management software became part of a broader workflow intended to reduce searches, duplicate entry, and dependence on personal memory.
Core Decision
Customs documentation was a high-value automation target because it depended on repeated copying and pasting. After integration, the system automatically populated about 60% of customs-file data. Staff still needed to check information and complete remaining work, but repetitive preparation was reduced. This distinction matters: automation improved the starting point for documentation without eliminating compliance responsibility or human verification.
Execution / Model / Acquisition Changes
The reported outcomes were operationally significant. After integration, about 60% of customs-file data could be populated automatically, reducing repetitive preparation and giving staff a more complete starting point for documentation. Reporting and customs-related preparation time fell 50%, according to the case materials, while CRMpartners reported a 40% improvement in after-sales-management efficiency. The case also described automated workflows across 65 countries, a measure distinct from the company’s reported reach of more than 60 countries. These results indicate that the project operated across a broad international context rather than serving only one channel. They should be read as case-reported workflow measures. Public sources do not disclose revenue growth, order growth, margin improvement, implementation cost, a precise measurement period, or independent audit results. The figures therefore support a process-efficiency conclusion, not a guaranteed financial return. Staff still needed to validate data and complete remaining customs work, so automation reduced administrative repetition without removing compliance responsibility or proving broader commercial growth.
Measurable Results
The integration created a more repeatable operating model. Customer history, lead sources, export administration, transport-related information, after-sales tasks, reporting, and customs preparation could be managed in connected records and workflows rather than isolated spreadsheets or employee memory. That structure reduced coordination friction and gave the company a basis for more consistent follow-up through Zoho Campaigns, including customer-care activity based on history or previous purchases. It also made automatically populated customs information available earlier in the preparation process. The capability remains dependent on accurate data, correct system mapping between Zoho CRM and Zucchetti, employee adoption, task discipline, and human review of customs information. CRM software creates potential; disciplined operating use converts that potential into a durable process advantage. The case does not establish that this capability produced revenue, order, margin, or market-share growth, so its demonstrated value remains operational and administrative.
Lessons
The case demonstrates a focused path to digital export management: identify the recurring administrative bottleneck, integrate the systems already used, automate repetitive preparation, and measure direct workflow effects. Gusti d’Italia reported about 60% automatic customs-data population, 50% less reporting time, and 40% better after-sales efficiency. The evidence does not establish revenue or profit growth, so the responsible lesson is narrower and stronger: connected workflows can make international food-export operations more consistent and scalable when supported by accurate data and human oversight.