For Diners
Less guesswork about what to eat
Menus change, days get busy, and everyone's needs and preferences are different. Daki is exploring a simple planning and decision layer that helps you see what is available, compare what fits, and plan ahead only when that helps.
Not available yet. Daki is pre-launch and preparing for an initial Harvard-focused experiment.
The problem
A decision you make again and again
Deciding what to eat is rarely one big choice. It is a small decision repeated every day, often while you are short on time, working around a schedule, and keeping track of what you need and what you feel like.
- Changing menus. What is served shifts by day, meal and location.
- Limited time. Many choices happen between classes, practice or work.
- Dietary needs. Allergies, restrictions and cultural or religious practices matter.
- Preferences and goals. Taste, mood, balance and personal goals all play a part.
An analogy
Shopping with a list, or without one
Without a list, you wander, double back, and often leave with whatever was easiest. With one, you still choose at the shelf, but you arrive knowing roughly what you want. Daki is exploring whether meals could work the same way.
Without a plan
Wandering and backtrackingWith a list
A route with purposeWhat Daki is exploring for diners
Each of these is a proposed part of the experience. The experiment will test whether they make food decisions easier, and for whom.
- Hypothesis
See what is available
Current options across the places you can eat, in one view.
- Hypothesis
Compare relevant options
Narrow by what matters to you right now, such as taste, dietary needs or time.
- Hypothesis
Choose with less guesswork
A short, explained set of options instead of every item on every menu.
- Hypothesis
Plan ahead, if you want
Pick a meal for later today, or a few for the week. Or skip planning entirely.
- Hypothesis
Remember meals to try
Save dishes you noticed so they are easy to find next time they are served.
- Future possibility
Fit meals into your schedule
See intended meals alongside classes, practice and meetings.
Planning stays optional
Plan as far ahead as you like
Some people may want to choose meals a week ahead. Others only want help with the next one. Both should be easy, and changing a plan should never be a hassle.
Just help me now
See what fits at the places open soon, then choose.
Sort out the day
Pick lunch and dinner in the morning, then get on with things.
Plan a few days ahead
Choose meals for the days you know will be busy, and leave the rest open.
Someday: meals next to the rest of your day
A longer-term idea is to let people add intended meals to Google Calendar or another schedule, so dinner shows up after practice instead of becoming a last-minute decision.
This is a future concept, not a current capability. It would only be built if early testers find it useful, and with clear controls over what is shared.
What students told us so far
A survey of 158 university students in September 2026, nearly all with a meal plan.
About this evidence. These figures come from one survey of 158 respondents collected September 19–29, 2026. It was a convenience sample, and the answers reflect stated behavior and interest. The survey does not demonstrate repeat use, product-market fit, customer demand or institutional impact.
Design commitments
What Daki should never ask of you
In the survey, 64.6% said a tool that takes too much time would stop them using it, and 38.6% did not want to log what they eat. These commitments follow from that.
- No calorie counting or meal logging required. Useful from the first visit, without a long setup.
- No telling you what you "should" eat. Options are explained, and the choice stays yours.
- Allergen information from verified sources. It should come from the dining location, never be guessed.
- Your history stays yours. Dining teams would see only aggregated patterns, not individual choices.
Be one of the first to try it
Join the waitlist to hear when early testing opens. Tell us where you eat and what makes deciding hard; it shapes what gets built first.
The waitlist is a short Google Form. Joining does not give immediate access; it helps Daki recruit early testers and understand dining contexts for the first Harvard-focused experiment.