What dietitians actually need from software

We interviewed 40 registered dietitians across South Africa, Nigeria, the UAE, and Kenya. We asked one question: 'What does your current software not do that you wish it did?' Not a single person said 'meal-plan templates.'

What they said, overwhelmingly, was: 'I need a food composition database that includes the foods my clients actually eat.' The USDA database — the backbone of most nutrition software — doesn't include fufu, pap, bobotie, or shawarma. Dietitians working with African and Middle Eastern clients are manually entering nutritional data for half their meal plans.

We partnered with Dr. Nadia Hassan, a clinical dietitian in Dubai, to build the Binectics Food Composition Database (FCDB). It now covers 2,400+ foods across West African, Southern African, East African, and Middle Eastern cuisines — with verified macro and micronutrient data.

The second need was client communication. Most dietitians use WhatsApp to check in with clients between sessions. That works socially but fails clinically — there's no structured data, no adherence tracking, and no way to look back at a client's progress over time.

We built client journals that sit between 'clinical EMR' and 'WhatsApp chat.' Dietitians log structured notes (weight, mood, adherence score) and can share a read-only view with the client. It's lightweight enough to use on a phone between sessions.

The lesson: don't build what other software already has. Build what's missing. For dietitians outside the Western market, what's missing is representation in the data layer.