NutriSync

What it is

NutriSync is the business side of easyChef Pro. The same engine that scores food for consumers is sold to organisations three ways: white label under their own brand, brown label as a co-branded product, or as documented, versioned APIs and licensed nutrition data with no interface at all.

It is built for organisations that create, track and monitor people against nutrition goals - professional sports teams managing athletes, healthcare providers managing patients, and enterprises applying the same standard across a population or a catalogue.

The engineering problem

Internal code and a public interface are not the same thing. Internally you can change a field name on a Tuesday. Once another organisation has integrated, that change is an outage in their product.

So the work was mostly about boundaries: what to expose, defining the contract before building against it, versioning so existing consumers keep working, authentication and rate limits, and documentation good enough that somebody can integrate without asking us a question.

One codebase serves the consumer application and the business customers. Letting it fork into two would have doubled the maintenance permanently, and the second copy is always the neglected one.

Why the scoring model made this sellable

A score is calculated at the ingredient level across more than 30 nutritional factors, over 800,000 USDA-verified products, and the same inputs always produce the same output. That is what a dietitian can put their name to and what a buyer can be shown when they ask where a number came from.

The engine scores against eight profiles - General Wellness, Heart Health, Metabolic, Digestive, Inflammatory Balance, Performance, Keto and Anabolic - and custom profiles are built to a customer specification. The goal changes the weights, not the underlying data.

That is also why the same product serves a strength coach and a cardiac ward. Performance weights protein density and recovery micronutrients; Heart Health weights sodium, saturated fat and potassium. Nothing about the data layer changes between them.

Why it is relevant to client work

Turning existing capability into something other companies can build on is a common request and an underestimated one. The technical work is real, but the decisions that matter are commercial: what you expose, what you promise to keep stable, and whether the customer wants your brand on it or theirs.

We have been on both sides of that - the team exposing an interface, and the team depending on one.