The work below spans operating a moving company, building inside a customs brokerage, and trying to connect businesses with different systems. Each experience raised a different question about getting something useful into practice.
In use at Agencia Stein · AI-assisted development
Port Operations System
Following an arrival across customs files, cargo, and delivery.
My role: partner at Agencia Stein; workflow design, application development with AI, and integration with the firm's existing systems.
The problem
Agencia Stein's existing customs system organized work around individual customs files. At the port, people also needed to follow a vessel and its cargo. Understanding an arrival meant piecing together information across files, screens, spreadsheets, and messages.
The design decision
I built an application that brings these views together. A vessel visit connects shipping documents, customs files, containers, and loose cargo. The customs file remains the regulatory unit; operators can see the work around it.
Those relationships matter. One container can belong to several customs files. A file may cover only part of a shipment. Documents and cargo can arrive in the system before the vessel is assigned. The application keeps these connections visible as the information changes.
My work with ONE Record informed this design: distinguishing physical cargo from the documents that describe it and the events that happen to it.
Following an arrival through delivery
Operators can start with a vessel visit and follow its cargo, linked customs files, pending tasks, and delivery documents. This brings the work for an arrival into a shared view, including cargo spread across several files. Delivery updates connect back to the existing customs and document systems.
A related service reads pickup schedules published by the STI terminal and connects them to the right containers and customs files. Its starting point was an automation built by a port operator; I reworked it into a shared service integrated with the application.
One arrival, connected views
Vessel visitThe arrival that brings the work together
Shipping documentsWhat is moving, and for whom
Physical cargoContainers and loose cargo
Customs filesLinked to the documents and the cargo they cover
↓
Tasks & deliveryPending steps, exceptions, documents, and progress
A simplified view of how the application connects the operation. A container can be linked to more than one customs file.
Building on the same information
Other workflows need these definitions and connections too. A delivery update, for example, needs to refer to the same cargo and customs file wherever it is used. Our development team is working on shared capabilities that new workflows can use.
Records in the system for arrivals from January 1 to September 24, 2026. Checked September 25, 2026.
About these figures
Counts cover vessel calls with linked customs files in the operational database, using recorded arrival dates in Chilean time. Customs files include partial declarations and exclude deleted records. A vessel call is a visit, so the same ship can appear more than once. These figures describe the scope of records held in the system; they do not measure completed deliveries or time saved.
More work & experience
Ongoing work · Customs brokerage
Making the next change easier
Working on the capabilities behind individual applications.
As a partner at Agencia Stein, I currently lead the firm's digital transformation, including business architecture, product design, and governance. I work with our development team while continuing to build applications with AI.
The aim is for each application to refer to the same cargo, documents, and events, so adding a workflow does not require inventing a separate version of the operation. This means agreeing on definitions and responsibility for information while keeping existing systems running. How much can be reused or configured remains work in progress.
Past executive role · Decapack
Connecting financial information to decisions
Cash forecasting, financial reporting, and management routines.
I was Decapack's Managing Partner (Chief Executive) from March 2010 to March 2019. The company provides international moving, fine art logistics, and relocation services.
In 2011, one priority was to give management a shared view of the company's cash needs and performance. Our team introduced a daily cash forecast and regular financial reporting.
The forecast helped us anticipate cash needs and plan customer collections and supplier payments. The board also set a routine for reviewing financial information and following up on commitments.
I also formed an internal team to build operational applications. Some became part of the operation; others were replaced or never adopted. That experience informs how I evaluate fit, maintenance, and adaptability.
Logistics data models · IAM pilot
Modeling logistics across systems
A shared understanding of cargo, documents, and events.
Logistics companies work with many of the same things: cargo, locations, movements, and documents. A domain model makes those things and their relationships explicit. Shared definitions give companies a basis for exchanging information across different systems.
Consider a move split across several deliveries. If a system records only one status for the whole move, staff need another way to track what remains. A model that represents the items and their delivery events can support that distinction.
I led a pilot for the International Association of Movers (IAM) exploring IATA ONE Record, an air-cargo data-sharing standard. It combined data mapping, technical trials, and coordination between moving companies. The pilot did not continue into sustained use. I applied ideas from that work in our Port Operations System and in the domain model for Agencia Stein.
A useful idea that did not become a sustainable venture.
I founded TrackMove to bring cargo tracking information from different sources into one product. We developed an MVP, but the venture did not succeed.
The experience left me with questions I still bring to a new product: who needs it enough to commit, what it takes to deliver it, and whether the business can sustain that work.
Have a process you want to improve? Let's look at where it gets stuck and what a useful next step could be.