Team AgentX44 Wins the "From Paper to Data" Logistics Challenge by OLTEK Solutions (2026) · Matt Alexius

Team AgentX44 (Gio Illustrisimo, Nathanael Larida, Christian Dave Vilan, and Matt Alexius Merano) won the "From Paper to Data" Logistics Automation Challenge run by OLTEK Solutions Corp., which then picked their solution, Manifesto, for production-level refinement.

On March 23, 2026, Team AgentX44 (Gio Illustrisimo, Nathanael Larida, Christian Dave Vilan, and me) won the "From Paper to Data" Logistics Automation Challenge, organized by OLTEK Solutions Corp. OLTEK also picked our solution, Manifesto, for production-level refinement, which meant they saw it as worth deploying after the competition was over.

The challenge OLTEK set

The competition was about a problem a lot of companies deal with every day. Typing paper logistics documents into digital systems by hand is slow, full of errors, and almost impossible to audit. OLTEK Solutions ran the challenge to find solutions worth actually building, so teams had to bring working systems they could demo.

Our solution: Manifesto

Manifesto pulls the data out of paper logistics documents and turns it into structured digital records automatically. Transcribing by hand takes hours and lets mistakes in. Manifesto does the same job in minutes, and every output can be traced and audited. We designed it around reliability: clean data in, clean data out, in a workflow that a non-technical logistics operator can check and trust.

Selected for production-level refinement

Winning meant a lot. Getting picked for production-level refinement meant more, because it showed OLTEK believed Manifesto could run in a real operation. That led straight to a contract Software Developer role at OLTEK, where the team is still building Manifesto toward production.

What building Manifesto under competition pressure taught us

In a competition build, every feature decision is fast and high stakes. What decided the outcome for us was managing scope, giving each person clear ownership of their part, and shipping something that worked and could be demoed before trying to make it perfect. It also showed us that clear, reliable, testable code matters more when time is short.