Work
What we've built, and what it changed operationally.
How the work fits together
Two of the cases below come from the same client. Read in order, they show the loop at work.
- First two weeks
A working PoC
02 · Validate PoC & MVP SprintsTwo weeks to a working AI POC. One month of internal testing.
From Spreadsheets and Email to Their Own Platform in 8 Weeks - The workshop
From participant to builder
01 · Train AI Capability ProgramsWeeks after the workshop he was building his own assistants.
7 Own agents in production
From Participant to Builder - Month four
Carriers in production
03 · Build Product DevelopmentBy month four, the main carriers and forwarders — Sinotrans, DHL, Semaco, Triviel — were operating in production.
90 → 30 min Meeting duration
From Spreadsheets and Email to Their Own Platform in 8 Weeks - Today
An internal lab connected to the platform
Today he has 7 agents in production — from logistics problem analysis to API integrations — with new projects connecting his lab directly to iTracker.
From Participant to Builder
From Spreadsheets and Email to Their Own Platform in 8 Weeks
Logística Internacional
Operations / Carrier Management
- Meeting duration
- 90 → 30 min
- Carrier response time (defined SLA)
- < 24h
- Zero to production (vs. 8–12 months industry standard)
- 8 weeks
- 01 The Problem
The team managed carrier issues across Google Sheets, email, and WhatsApp. No history, no traceability, no metrics by carrier. Every issue was resolved in 90-minute meetings with incomplete information and no record of who did what. Measuring carrier performance was impossible.
- 02 What We Built
Two weeks to a working AI POC. One month of internal testing. By month four, the main carriers and forwarders — Sinotrans, DHL, Semaco, Triviel — were operating in production. External development cost estimated at USD 43,000–200,000 with an 8–12 month timeline. McKinsey estimates fewer than 10% of AI projects reach production. This one did in eight weeks.
- 03 The Result
Meetings dropped from 90 minutes to 30. Carrier response time fell below 24 hours with a defined SLA. Asian suppliers now access the platform without VPN. The team has complete history, traceability by carrier, and a full action log for every issue.
"iTracker proved that the team can build high-impact tools in weeks — not months."
The Manager Who Got His Time Back
Leading shipping company (name available soon)
Commercial Management / Communications
- To automate the entire flow
- 1 week
- Per email processed manually
- 5 min → 0
- 01 The Problem
The manager manually processed dozens of emails every day — each following the same logic: check if the information was complete, determine if the response applied, draft the reply. Five minutes per email. High-value time lost to repetitive, low-judgment work.
- 02 What We Built
In one week, we automated the entire flow. The system reviews incoming email, applies the business rules, and generates a ready-to-send draft. The manager reads, adjusts if needed, and hits send.
- 03 The Result
One week of work to recover hours of management time each month. The manager stopped being a typist and went back to being a decision-maker.
"A process that seemed complex had a simple logic. It just needed to be built."
From Participant to Builder
Logística Internacional
Gonzalo, Innovation Analyst
- Own agents in production
- 7
- 01 The Problem
Gonzalo arrived at the workshop not knowing what to expect. Like most people, he was using AI in a basic, unsystematic way — familiar with the tools, not fluent in applying them.
- 02 What Happened
Weeks after the workshop he was building his own assistants. Then Notion tools. Then he proposed creating an internal innovation lab. Months later, unprompted, he launched an app showing the real-time global journey of the company's containers. Today he has 7 agents in production — from logistics problem analysis to API integrations — with new projects connecting his lab directly to iTracker.
- 03 The Result
An analyst who went from passive user to active AI infrastructure builder. Not because he was told to — because the workshop gave him the language, the method, and the confidence to start.
"I thought I knew AI and realized I was behind. Now I'm a machine." — Gonzalo, Innovation, LI
If you're running into a similar operational problem, the first step is usually a process audit — not a tool conversation.