For people who entertain others often, one of the challenges that a good host/hostess encounters is not knowing for certain if a guest has a serious allergy or food aversion. This also has applicability when ordering meals for business clients or even weddings, etc.
Why not have a centralized database where each person could identify his/her food preferences? For example, I'm allergic to sesame seeds and nuts. When I go out, I have to tell people that and sometimes they forget. Sometimes I forget to tell them and I have to ask them and some are embarrassed that they made a dish I cannot have. It's not a big deal, but as a host/ess, you feel good knowing that everyone can enjoy what you've made. Plus, when I entertain business customers, it's particularly important to me that they feel completely comfortable.
With the centralized database, you could input the names (or emails) of those who will be attending and the system could give you a 'watch list' of ingredients not to use. This could be extended to items you just prefer not to eat (I'm not a fan of eggplant) as well. In a later iteration, the home chef could input the dish that was actually served in order to prevent serving a similar dish when hosting again.
Restaurants and caterers might like to have access to this in order to provide meals that are satisfying and they would generate a lot of positive feedback. Imagine sitting at a wedding and the waiter comes up to you and says, "we know that you are allergic to peaches, so we've prepared a special dessert for you." That would score major points, I am sure.
In addition, this would be a time-saver, as you would never have to communicate your food preferences to those utilizing the system.
The potential revenue models are plenty. 1. charge for access to the system. 2. Advertising (of course) 3. co-market w/food companies based on customer preferences. And those are just the ones off the top of my head.
I agree
No opinion
I disagree
Add your comment