The most expensive ingredient in Iya Ruka’s buka wasn’t the meat or the rice. It was the space between her pot and the customer’s plate—a gap filled with hesitation, wrong guesses, and the quiet hiss of food growing cold.
Her spot under the tree was famous for her Ofada stew. Yet, some days, she’d watch a pot of jollof rice sit until the oil gathered in a dull, orange film. She’d end up eating it herself, a meal that tasted like lost profit. Other days, the stew would finish by 1 PM, turning away the loyal construction workers who came at 2. Her solution was to cook more of everything. Her waste grew. Her stress thickened like the bottom of a poorly stirred pot.
Her conversations followed a weary script. A customer would point at a pot: “Wetin be this?”
“Rice.”
“Which rice?”
“Just rice. With stew.”
“Which stew?”
“Normal stew.”
The customer would pause, look at the next stall, and drift away. Iya Ruka would mutter about indecisive people.
The shift didn’t come from a decision to “use AI.” It came from a single, defeated Thursday. Facing two full pots of unsold food, she did something that felt silly. She opened her phone notes and typed a raw, tired diary of the day:
“Cooked big pot of jollof. Finished small pot of stew by 1. Jollof no finish. Beans for 3pm people no plenty. Man in blue van always comes 12:30 for eba and soup. Forget today.”
For a week, she kept this up. No analysis. Just confession. “Egusi finished fast. White rice nobody touch. Rush for small chops around 4pm.”
At the week’s end, she selected the chaotic notes and pasted them into an AI. Her prompt was a sigh: “Make sense of this food matter for me.”
The response wasn’t a strategy. It was a reflection.
It grouped her chaos.
*“Pattern 1: Stew/Egusi finishes early (before 2pm). Jollof/White rice often remain.*
“Pattern 2: A ‘4pm rush’ exists, but for snacks, not main dishes.
“Pattern 3: A specific customer (blue van) relies on consistent availability at 12:30.”
It asked a simple question her worry had never allowed: “What if the problem isn’t the food, but the timing and the name?”
She didn’t change her recipes. She changed her mirrors.
First, the names. She typed her menu into the AI: “Rice. Stew. Beans. Jollof.” She asked it to make them clear, not fancy. It suggested: “White Rice & Fresh Tomato Stew.” “Spicy Jollof Rice.” “Soft Beans with Palm Oil.” She started saying these names aloud. The hesitant questions from customers reduced by half.
Then, the timing. Using her notes, she saw the “4pm rush” was real, but people wanted quick, handheld food. She started making a small, fresh batch of meat pies for that window. They sold out.
Most importantly, she saw the “blue van man” not as one customer, but as a pattern of reliability. She began to keep one portion of eba and soup back for that 12:30 window. He never asked. He just got his food, faster. His loyalty became a silent anchor in her day.
Iya Ruka’s story isn’t about a robot running a kitchen. It’s about a vendor getting a quiet place to think outside the heat, the noise, and the pressure of the fire. The AI didn’t tell her what to cook. It showed her the rhythm she was already living but was too busy to hear.
The goal was never to attract a crowd. It was to close the gap—between the pot and the plate, between a vague name and a quick decision, between her memory and her customer’s habit. Profit didn’t surge; it just stopped leaking. And in the food business, that is the difference between surviving and thriving.
The method for finding this rhythm is a process of quiet observation. The guide How Food Vendors Use AI to Increase Daily Sales provides the steps. It’s not about becoming a tech expert. It’s about becoming a calm observer of your own business, so you can cook less, sell more, and waste nothing.