The problem
Most kitchen owners know what they charge for a dish. Far fewer know what it **costs** — because to know, you have to price every ingredient in the right unit, account for what is lost in preparation, and redo the sum every time the price of onions moves.
The result is a menu that looks profitable and is not. That mistake never shows up in the bank statement as one line; it leaks away slowly across a few hundred plates a month.
What we observed
Before we wrote any code.
Units are the whole problem.
People buy onions by the kilogram and cook by the gram. Oil is bought by the litre and used by the spoon. A system that makes the user convert will produce wrong costs, and they will not notice until it is too late.
So unit conversion is built into the core rather than bolted on. You record a price in the unit you buy in, recipes use the unit you cook in, and the system is what joins them.
Second: real yield. A kilogram of raw chicken is not a kilogram of trimmed chicken. Yield is a first-class field, not an advanced option.
What we built
CostBuddies (CO$Ty) helps food businesses cost recipes precisely: a preset ingredient library, yield-based costing that respects g-vs-kg units, and analytics that surface true margins. Livewire-powered with a rebuilt admin and usage/traffic analytics engine.
Before vs after
The same job, the old way and the new way.
Before
After
Results
Counted from the production database on 29 August 2026. The system is young — these show real usage so far, not projections.
More like this
Related work
Mobile App
2026
MasjidMG
The mosque community super-app
Mobile App
2026
MyCuciRapi
On-demand home cleaning, booked in seconds
Builtech · BPM Tracker
Construction project management, reinvented
Build something similar
Let's build yours.
Tell us what you're planning. Free 30-minute call, a written scope and a fixed quote — we reply within one working day.