Farmcrowdy
Designing trust for agricultural investment in a category most users had never touched.
Four years growing from founding designer to program and product leadership inside Nigeria's first digital agriculture platform — spanning platform design, brand systems, growth infrastructure, and a cross-functional unit that incubated Farmcrowdy Foods, Grainpoint, and HAPI Insurance.
The product problem was a trust problem.
Before Farmcrowdy, participating in agriculture at any meaningful level usually required land, farm knowledge, local relationships, operational oversight, or enough capital to hire people who had all four. Smallholder farmers had the work and the land, but often lacked consistent access to funding, inputs, equipment, advisory support, and reliable market pathways.
Farmcrowdy compressed that gap into a digital sponsorship model. Sponsors could fund farm units through the platform. Farmers received operational support. Sponsors received farm updates and expected returns after harvest.
How do you convince someone to fund a farm they may never visit, run by people they may never meet, across a farm cycle they do not understand? The answer was not one feature. It was a trust system.
Public-safe figures for the retrospective.
These figures are included as approved retrospective proof points and should remain tied to source review before publication.
- Best AgriTech Solution, AppsAfrica Innovation Awards 2018
- UNIDO Global Disruptive Innovation in Agribusiness award, 2019
Trust was designed as a sequence of answers.
Each product decision answered a different sponsor anxiety: Is this real? What will I earn? Where is my money going? What happens after I pay? How do I know the farm still exists?
Institutional credibility before personal trust
The farm detail screen placed the Leadway insurance badge close to the investment decision. In a category without established trust signals, the badge borrowed credibility from an institution users already understood.
A calculator before checkout
The Harvest Returns tab let users enter the number of farm units they wanted to sponsor and immediately understand projected payback, net profit, and expected return before committing.
Named farms, real locations
Farm listings were concrete: names, crop or livestock types, towns, states, contract periods, and expected returns. Trust increased when the object of sponsorship became specific.
The Farm Shop borrowed the legibility of e-commerce.
The Farm Shop used a familiar browse, cart, and checkout pattern. A purely financial interface would have made the product feel more technical and intimidating. A cart made the action legible without trivialising the sponsorship.
The onboarding framed participation before explaining the system.
The first screens led with rural farmers, food security, and the link between financial return and farmer support. The product was not asking people to speculate on agriculture. It was asking them to join a system where return and farmer support sat together.
The product could not go silent for a full farm cycle.
Once a user sponsored a farm, the waiting period became the experience. Farms Followed and Farm Updates created staged progress: planting, growth, monitoring, updates, and harvest.
The return path had to exist before the return arrived.
The Return After Harvest account setup was not visually dramatic, but it was strategically important. It showed users the product had thought through the end of the cycle, not just the moment of payment.
The early product tried to feel alive between high-stakes moments.
The home experience leaned into posts, farm updates, likes, shares, and invitations. In hindsight, this helped Farmcrowdy feel active, but it also carried operational weight. Feeds require maintenance; a simpler update-and-notification model may have served the core sponsorship experience better.
From designing screens to designing the operating layer.
I joined as the first design hire. The earliest work was product definition: onboarding, sponsor flows, farm listings, farm detail pages, calculator logic, checkout, account setup, and the trust signals that made the experience credible.
As the company grew, my role expanded beyond interface design into brand, marketing systems, growth, product direction, and program development. The work moved from designing the sponsor app to helping build the product layer around a broader agritech ecosystem.
A retrospective has to name the tradeoffs.
- The feed was too expensive to maintainThe social home made the product feel alive, but it also asked Farmcrowdy to behave like a content platform. A stronger notification and farm-update system may have delivered more value with less operational drag.
- The timeline needed stronger health signalsThe Farms Followed timeline showed progress, but sponsors also needed clearer status language for normal, delayed, concerning, or excellent farm conditions.
- The dashboard needed stronger prioritisationThe sponsor dashboard used a grid of actions. That worked early, but a task-based home would have scaled better as product scope grew.
The product helped make agricultural sponsorship concrete, trackable, and credible.
Farmcrowdy was where I learned that trust is not a visual style. It is an operating system.
The insurance badge, calculator, farm locations, cart, farm updates, and Return After Harvest setup were not isolated UX details. They were the product's trust architecture. The product worked because it translated agricultural complexity into a familiar digital journey without pretending the complexity did not exist.