Case Study: Inventory Software for a Catering Business
Sip n Scoops Society was doing syrup, purée, and ice math by hand before every event — worse in weeks with five events at once. Here's the recipe-and-yield calculator Kairos built to replace it.
The client
Sip n Scoops Society caters events across the Wake Forest area as an authorized operator of two separate mobile-cart brands — Sodabox for drinks and Mama Birds Ice Cream for ice cream — plus a hot chocolate cart the owner created herself for winter and holiday parties. Every booking is its own small logistics problem, and now it's one that can span all three lines at once: a guest count, a lineup of recipes pulled from whichever brands the event calls for, and a shopping list of syrups, purées, ice, and dairy that has to add up to enough — without so much surplus that it goes to waste.
The problem
Before every event, the owner sat down and worked out the ingredient math by hand, separately for each brand: how many drinks a bottle of a given syrup or purée would yield, how many bottles that meant for the guest count and recipe mix she'd chosen, and how much ice or dairy to bring. It was arithmetic she could do — the problem was doing it correctly, from scratch, for every single event and every brand involved, including weeks where five events landed at once. Any recipe change, any shift in guest count, meant redoing the whole calculation by hand, under time pressure, with real money riding on getting it right. Over-order and it's wasted inventory. Under-order and it's a scramble the day of the event.
This is a pattern worth recognizing in any operation: a calculation that is simple in isolation but repeated constantly, under deadline, by one person who is also running everything else. That combination is exactly where a spreadsheet or mental math quietly becomes the most fragile part of the business — the subject of when to replace your spreadsheets with custom software.
What we built
The fix wasn't a bigger spreadsheet — it was moving the two numbers that actually drive the math into a system that could do the arithmetic instantly and consistently:
- A recipe library organized by brand — Sodabox, Mama Birds Ice Cream, and her own hot chocolate line — each drink recorded once with every ingredient it needs
- A yield value per ingredient — how many servings one purchasable unit produces (a bottle, a tub, a sleeve)
- An inventory calculator that takes a guest count and a set of chosen recipes, across any combination of brands, and outputs exactly how many units of each ingredient to buy
- Automatic rounding up to real purchasable pack sizes, so the output matches what a supplier actually sells rather than a fractional bottle
- A pickup and prep list generated straight from that calculation, ready to shop and pack from
- Login-gated access, built from day one to extend to future employees rather than staying locked to one person’s knowledge
None of the individual steps are exotic — it is the same yield-ratio math the owner was already doing. What changes is where that math lives: once, in a system, instead of being re-derived by hand for every event.
The outcome
The weekly ritual of sitting down and calculating ingredient needs by hand — brand by brand, recipe by recipe, bottle by bottle — is gone. The owner enters a guest count and a recipe lineup, drawn from any combination of Sodabox, Mama Birds Ice Cream, and her own hot chocolate line, and gets back a purchase list, whether it's one event that week or five running at the same time. And because the tool doesn't depend on the owner personally doing the math, it's built to bring on future employees without losing the process that makes the numbers come out right.
How we approach this
Brad Walker has spent more than twenty years building operational software for small businesses from his base in Wake Forest, NC. Projects like this one start the same way every time: find the calculation someone is doing manually and repeatedly, understand exactly what it depends on, and turn those inputs into a system that produces the same answer instantly and correctly every time — instead of a bigger spreadsheet or a generic tool that only covers part of the problem.
Engagements are fixed price, with the scope agreed before development starts. You know what you are getting, what it costs, and when it lands.
Frequently asked questions
How does custom software calculate catering inventory from a guest count?
It starts from two numbers that already exist in the business: how many servings a recipe needs to produce, and how many servings a single unit of each ingredient yields — a 1-liter bottle of syrup might supply 135 drinks, a bottle of purée might supply 256. Once those yields are stored once, the software can take any guest count and any combination of recipes and work backward to exactly how many units of each ingredient are needed, then round up to whatever pack size the ingredient is actually sold in. The owner stops redoing the arithmetic and starts just entering the event.
Is a custom app worth it for a small catering or events business?
It depends on how repetitive and error-prone the manual version already is. A business doing one event a month can usually get by on a spreadsheet. A business doing several events a week, each with its own guest count and recipe mix, is redoing the same yield-ratio math over and over under time pressure — exactly the kind of repetitive, rule-based calculation that is cheap to get wrong by hand and straightforward to get right in software. The threshold to watch for is not revenue, it is how often the same calculation gets repeated and how much it costs when it is off.
If your team is redoing the same calculation by hand before every job, that is usually fixable in less time than it feels like. Start the conversation. The first step is a discovery call to map exactly what you calculate manually today and what depends on it.
Ready to talk about your project?
Tell us what you're building. Brad reviews every submission personally.
Start Your Project