Operations first. Software second.

Zanatello Acosta Consulting is new, so the proof comes from before ZAC: four results from prior operating roles. Each case shows the context, the friction, the intervention and the measured outcome, and each is labelled by where the work was done.

CASE.01Prior role · Amazon Spain

National capacity planning

Context: A national hub delivery network of about 2,500 partner stores, planned centrally.
Friction: Network planning had no reliable view of which partners would be available, so plans broke and compliance varied by site.
Intervention: A rostering process with a compliance mechanism designed with Legal, and a capacity and volume forecast built on top of it.
Adoption: Rolled out in phases, with partner training, plain communication and weekly KPI tracking.

85 → 97%Partner roster compliance

Read the case

CASE.02Prior role · Amazon Spain

Route optimisation

Context: Route planning for a national delivery network, with vans, delivery windows and driving-time limits.
Friction: Routes were configured by hand, node by node, with no way to test alternatives before changing them.
Intervention: A Python model that groups stores into routes and sets the number of routes per node within van, time and window constraints.
Adoption: Used to test scenarios before each change, node by node, then built into a standard weekly planning routine.

+27%Route efficiency (stops per route)

Read the case

CASE.03Prior role · Amazon Spain

Reverse-logistics launch

Context: A fulfilment centre taking over a returns process from another site, with a week's notice.
Friction: No adapted line, no flow, no trained people and no standards, and the volume was already on its way.
Intervention: A seven-day launch sprint: line adaptation, a reversed flow, training material, sortation areas and flows.
Adoption: Instructors and associates trained during the sprint; layout, audits and reporting improved in the months after.

7 daysFrom notice to live operation

Read the case

CASE.04Prior role · Amazon Spain

Standards that travelled

Context: Returns and inbound operations with hundreds of associates across shifts.
Friction: The same quality errors kept returning, coaching was ad hoc, and good practice stayed on the shift that found it.
Intervention: A quality school with tracked performance, targeted coaching and a wall of real examples, plus daily routines for team leads and a support-staffing calculator.
Adoption: Run with the learning team and the team leads, documented, then presented to other sites and adopted across Europe.

EU-wideAdopted by sites across Europe

Read the case

A similar problem?

These were built inside large operations. The same method works at smaller scale: map the system, pick the smallest intervention that matters, build it and hand it over.

Discuss a problem See the approach