A poultry operation, in one app.
A Kenyan poultry producer with a farm and retail outlets. The client’s name is withheld until they approve, and every screen and figure on this page uses sample data.
Production on the farm, sales at the outlets, and nothing joining them.
The farm recorded production and the outlets recorded sales and stock, but in different places. Getting a true picture of the week meant collecting numbers from several people.
The client was weighing two off-the-shelf products, one for books and one for inventory. That would have meant two subscriptions, two logins and the same stock typed twice.
One system, modelled on the app the team already knew.
Rather than adapt the business to two generic tools, we designed one app around the way the team already worked. It followed the logic of the poultry-management app they were using, so there was less to relearn.
Prototype first. We built and agreed a working prototype, then the production version on a low-code business platform.
Each role sees its part of the day.
- Role-based screens for farm, outlet and owner
- Stock tracked as it moves from the farm to each outlet
- Notifications when something needs attention
- Reports, with spreadsheet exports for the accounts
Handed over. Now in pilot.
The first release was handed over in November 2026. The pilot runs to January 2027, and the client’s team is using it on real work while we fix what they find.
The client has asked for invoicing and payment-gateway integration as the next phase.
Results after the pilot, not before.
We haven’t published time saved or error rates, because the pilot hasn’t finished. Once it has, and with the client’s written permission, we’ll add what changed, in their words and with their numbers.
Running something similar on paper?
Farms, distributors and multi-outlet shops share the same problem: stock in one place, sales in another.
Sketch your system Start a project