All articles
Hackathon2nd place

GestAvi: 2nd place at the first Genuka Hackathon

After Bafoka, the adventure went on — with an app built to modernise poultry farming.

by Vidhal Elame
EventHackathon Genuka 2025 · 1st edition
Date6 Dec 2025
ProjectGestAvi
Result2nd place

The problem

Poultry farmers juggle staff, money, feed, medicine and flocks, usually on paper.

A flock is a batch of birds of the same age, arriving on the same day and leaving on the same day. The whole job turns around it: what it eats, what it costs, how many birds it loses, when it will be ready to sell. In a notebook every number exists, but none of them talk to each other. The farmer knows he bought feed last week. He does not know what this flock really cost him, or whether it pays.

That is the kind of problem that makes a good hackathon subject: it is real, it is precise, and the person living it does not need to be told why it matters.

What we built

GestAvi lets a farmer manage the farm from A to Z:

  • staff and finances;
  • precise stock of feed and medicine;
  • monitoring of each flock to improve productivity.

What holds it all together is the flock. As long as money, stock and birds are tracked separately, you just have three more notebooks. Tracked together, they answer the two questions a farmer cares about: what did this flock cost me, and what did it bring in.

Next.js, to move fast

We built GestAvi with Next.js. In forty-eight hours the first benefit is plain: one project holds the pages and the server side. No second repository, no API to run next to it, no time lost getting two projects to talk.

The app is split the way the trade is: flocks, stock, staff, finances. It is also a practical split for a team: each person can move on their own screen without stepping on a neighbour's, as long as everyone agreed on the shape of the data very early.

Forty-eight hours, in practice

Forty-eight hours of intense code for a real need in agriculture. In this format, three things come back every time.

Start with the data, not the screens. Until the team agrees on what a flock, a stock movement or an expense is, each screen invents its own version, and nothing connects at the end.

Build the demo path first. Create a flock, give it feed, record an expense, see the result. If that path works end to end, the project exists. The rest is comfort.

Talk to the jury in the user's language. A jury remembers "the farmer finally knows what a flock costs" far better than a list of technologies.

Thanks

To the Genuka organisers for this initiative and to the jury for recognising our work.

It was the first edition of the Genuka Hackathon, and our third podium of the year after BAFOKA-Market and the voice WhatsApp bot. What the three projects share: an everyday problem, in Cameroon, handled with simple tools.