# Know Your Customer
**Chapter 02**
## "Everyone" is not a customer
Ask most restaurant owners who their customer is and you will get some version of "anyone who likes good food" or "people in the neighbourhood" or "families and young professionals." These answers feel safe because they exclude no one. But that is exactly the problem.
When your customer is everyone, your marketing speaks to no one in particular. Your menu tries to cover too many occasions. Your pricing sits in an awkward middle — too expensive for value seekers, too cheap to signal quality. Your experience is designed for a generic person who does not exist.
The restaurants that grow efficiently — that create the right customers and keep them — have an answer to "who is this for?" that is specific enough to guide decisions. Not so narrow that it shrinks the market, but specific enough that everything from the decor to the Instagram caption to the delivery packaging feels like it was made for someone.
This is what an Ideal Customer Profile means for a restaurant.
***
## Defining your Ideal Customer Profile
An ICP for a restaurant is not a demographic profile. "Women aged 25 to 35 with household income above $80k" tells you almost nothing useful. You cannot design a menu or a campaign around that.
Instead, think about your ICP through five lenses:
**Occasion.** What is the customer trying to accomplish when they choose you? A quick lunch between meetings? A Saturday night date? A family celebration? A lazy Sunday brunch? A Tuesday night "I don't want to cook" delivery order? The occasion defines the need, the budget, the channel, and the expectations. Most restaurants serve more than one occasion, but the best ones are known for one or two.
**Context.** Where is the customer coming from and what is the surrounding situation? Are they office workers within a 500-metre radius? Are they destination diners who will travel 30 minutes for you? Are they nearby residents ordering from their couch? Context determines your catchment, your discovery channels, and your pricing power.
**Frequency potential.** Can this customer come back weekly? Monthly? A few times a year? A lunch spot for office workers has enormous frequency potential — five days a week, 50 weeks a year. A destination fine-dining restaurant might see the same customer three or four times a year at best. Frequency potential shapes whether your growth comes from deepening a smaller base or widening a larger one.
**Channel preference.** Does your customer prefer to walk in, book ahead, order online, or get delivery? This is not just an operational question. It determines where you invest, what technology you need, and how you capture and retain the customer relationship. A customer who only knows you through GrabFood is a very different customer from one who books through your own reservation system.
**Price sensitivity.** Not just "can they afford it" but "what do they expect for the money?" Price positioning is about the value equation — what quality, quantity, speed, and experience does the customer expect at this price point? Getting this wrong means attracting customers who feel ripped off or customers who undervalue what you offer. Neither group stays.
***
## The three customer states: New, Known, Repeat
Once you have defined who your customer is, you need a way to understand where each individual sits in their relationship with you.
**New customers** have never transacted with you. They may have heard of you, walked past your storefront, seen your Instagram, or been recommended by a friend — but they have not yet made the decision to try you. For you, they are potential. The job is creation: give them a reason and a path to try you for the first time.
**Known customers** have transacted with you at least once. You have some evidence that they exist — a transaction record, an email, a loyalty sign-up, a reservation. They have tried you, but they are not yet loyal. They could come back, or they could disappear and you might never notice. Known customers are the critical middle state. The job is conversion: turn them from trial into habit.
**Repeat customers** come back without prompting. They have made you part of their routine or their regular consideration set. When the occasion arises, you are one of the first options they think of. They may not come every week, but they come consistently over time. Repeat customers are the foundation of a healthy business. The job is reinforcement: keep the experience consistent, recognise their loyalty, and give them no reason to leave.
The ratio between these three groups tells you more about the health of your business than almost any other metric. A restaurant that is 80% new customers every month is a revolving door. A restaurant that is 80% repeat customers with shrinking new customer flow is slowly dying. The healthy pattern is a steady stream of new customers being converted into known, and then known into repeat, with the repeat base growing over time.
***
## Occasions, not demographics
Here is something most restaurants miss: the same person is a different customer depending on the occasion.
A 32-year-old professional might order delivery on Tuesday night (convenience occasion, low effort, moderate spend), bring a date to your restaurant on Friday (experience occasion, high effort, high spend), and grab a quick takeaway lunch on Saturday (speed occasion, low spend). Same person, three entirely different need states, three different menu interactions, three different value expectations.
This is why demographic profiling is weak and occasion profiling is strong. When you understand the occasions you serve, you can:
**Design your menu around them.** A lunch menu that respects the time constraint. A dinner menu that rewards exploration. A delivery menu optimised for travel and reheating.
**Market to the occasion, not the person.** "Your Friday night, sorted" is a better message than targeting 25-to-35-year-olds. People self-select into occasions. Let them.
**Measure by occasion.** If your weekday lunch is strong but your weekend dinner is weak, that is not a revenue problem — it is an occasion problem. And the fix is specific to that occasion, not a general "boost revenue" initiative.
***
## The customer you want vs. the customer you have
Most restaurants have an implicit ICP in their head — the kind of customer they imagined when they designed the concept. But the customers who actually show up may be different.
Maybe you designed a premium casual-dining experience but your most frequent customers are families with young children who come for the kids menu. Maybe you built a delivery-first concept but most of your volume comes from walk-ins in the neighbourhood. Maybe you positioned yourself as a weekday lunch destination but Saturday dinner is where the money is.
None of these are necessarily problems. But they become problems when you keep marketing to the customer you want while ignoring the customer you have. Or when you keep investing in the occasion you designed for while the occasion that actually pays the bills is underserved.
The exercise is simple: look at your data. Who is actually coming? When are they coming? How are they ordering? How often do they return? Compare this to the customer you thought you were building for. Where the two align, double down. Where they diverge, you have a decision to make — adjust your concept to match reality, or adjust your strategy to attract the customer you originally wanted. But do not ignore the gap. The gap is where revenue leaks.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://www.oddle.me/docs/guides/how-to-think/know-your-customer.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.