Giving farmers one place to share their data
At Socopro, I led the build of a platform that lets farmers push their data out to multiple catalogs from a single place — instead of re-keying the same information into each one. I owned the architecture, chose the stack, wrote the API documentation, built core parts of the product, and led the team that shipped it.
The problem
A farmer's data has to reach a lot of destinations — catalogs, buyers, registries — and each one tends to want it in its own shape. Done by hand, that's repetitive, error-prone work that scales badly: more catalogs mean more re-entry and more places for the data to drift out of sync. The job was to let a farmer enter and own their data once, and have the platform distribute it everywhere it needs to go.
What we built
I defined the data architecture and selected the technology stack the platform runs on — the decisions that set how far it could scale later. On top of that:
- A scalable back office to manage the data and the distribution logic.
- A Next.js front end on a JAMstack architecture — fast to use, and cheap to serve as usage grows.
- API documentation that made the platform's data usable by the catalogs and services on the other end.

The result is a single source of truth for the farmer, wired to send clean data wherever it's needed.
Leading the team
We managed and mentored a team of four developers through the build — setting the technical direction, keeping the architecture coherent while we moved fast, and bringing the team along rather than just handing out tickets. Shipping a platform like this is as much about how the team works as the code they write.
Why it matters
The value is control. The farmer owns their data and enters it once; the platform handles distribution. That means less busywork, fewer errors, and a foundation that holds up as more catalogs come online — a small, concrete improvement in the day-to-day of people who have better things to do than copy fields between systems.
This is the kind of work we do at Co-Labs: real, shipped software built and owned by senior operators — not a prototype that dies in a drawer.
What the customers says
The implementation of our new website came with its fair share of challenges, whether due to the number of partners involved or the fluctuating scheduling constraints. Daniel’s versatility, experience across various industries, and pragmatic approach enabled us to achieve an optimal solution.
Karl Knobben - Board of Producers


