# The Two Jobs
**Chapter 01**
## Revenue is an output, not a goal
Most restaurants track revenue as the number. Monthly revenue, weekly revenue, same-store sales growth. It sits at the top of every report, and when it goes up people celebrate, and when it goes down people panic.
But revenue is not something you can act on directly. You cannot walk into a kitchen and tell your team to "make more revenue." It is the result of a system working well — or poorly. When you chase the number itself, you end up discounting to fill seats, running promotions that attract deal-hunters who never return, or over-indexing on a single channel because it delivers volume today.
Revenue is an output. It is the consequence of doing two things well.
***
## The two jobs every restaurant must do
A restaurant exists to do two things: **create customers** and **keep them**.
That is it. Every marketing campaign, every menu change, every operational decision, every dollar spent either helps you find new customers or gives your existing customers a reason to come back. There is no third job.
**Creating customers** means making someone who has never eaten with you choose to try you for the first time. It is the act of becoming visible, relevant, and compelling to someone who does not yet know you — or knows you but has never made the decision to walk in, place an order, or make a booking. Creation is about reach, awareness, trial, and first impressions.
**Keeping customers** means making someone who has already eaten with you choose to do it again. Not once more, but repeatedly, over time, without needing to be convinced each time. Keeping is about experience, consistency, recognition, and building a habit.
These two jobs are not "strategies" you choose between. They are the only two strategies. Everything else — loyalty programmes, delivery platforms, social media, menu engineering, reservations systems — is a tactic that lives inside one of them. Some tactics serve both, but every tactic must serve at least one.
***
## Why this framing matters
When you see your business through this lens, the right questions change.
Instead of asking "how do I increase revenue?", you ask:
**Am I creating enough new customers?** Are new people discovering me? Is my reach growing or shrinking? When someone tries me for the first time, is the experience strong enough to make them want to come back?
**Am I keeping the customers I have?** Are the people who have eaten with me coming back? How often? Is that frequency increasing or decreasing? When someone stops coming, do I know? Do I do anything about it?
These are different questions that lead to different actions. A restaurant that is great at creating but terrible at keeping will look busy but never build a stable base — the queue is long but the faces keep changing. A restaurant that is great at keeping but has stopped creating will feel comfortable until the base slowly shrinks through natural attrition, and by the time the decline shows up in the revenue number, it is hard to reverse.
***
## The leaky bucket
This is the most common pattern in restaurants: spending on creation while ignoring retention.
Imagine you spend $5,000 a month on marketing and it brings in 500 new customers. Sounds good. But if only 20% of them ever return, you have gained 100 lasting customers and lost 400. Next month, you spend $5,000 again. Another 500 new faces, another 400 lost.
You are filling a bucket with a hole in it. The marketing spend feels productive because the top line holds, but you are running a treadmill, not building a business. Every month you start from roughly the same place because you are replacing lost customers instead of accumulating them.
Now imagine you fix the bucket. Same $5,000, same 500 new customers, but now 40% return. That is 200 lasting customers per month instead of 100. After six months, you have 1,200 cumulative repeat customers instead of 600. Same acquisition spend, double the base. And repeat customers cost almost nothing to retain compared to the cost of acquiring new ones.
This is the math of why retention compounds and acquisition does not. Every customer you keep becomes part of the base that generates revenue next month without additional spend. Every customer you fail to keep is a sunk cost that you have to replace.
***
## The balance
The goal is not to choose between creating and keeping. You need both. A restaurant that stops creating stagnates. A restaurant that stops keeping never scales.
The question is balance and sequence.
**If you are new**, almost all of your energy goes into creation. You have no customers to keep yet. But even from day one, you should be building the infrastructure to keep — capturing customer data, making strong first impressions, giving people a reason and a mechanism to return.
**If you are established**, the highest-leverage move is almost always improving retention. You already have traffic. You already have people who have tried you. Converting more of them from one-time visitors into regulars is cheaper and faster than finding entirely new people.
**If you are growing**, the ratio shifts as you add locations or channels. Each new outlet needs creation energy, but your existing outlets should be retention machines. The network effect of a multi-location brand comes from keeping customers across the system, not just creating them at each door.
***
## The mental shift
Most restaurants think about revenue as one number going up or down. This chapter asks you to think about it as two numbers: how many customers are you creating, and how many are you keeping?
When you look at your business this way, you will never again be confused about where to focus. One of these two numbers will always be the constraint. Your job is to figure out which one, and then go to work on it.
Everything in this playbook builds on this foundation.
---
# 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/the-two-jobs.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.