# Part II — What to Do

- [What to Do When](https://www.oddle.me/docs/guides/what-to-do/situation-playbooks.md): Situation playbooks for specific moments in a restaurant's life. Each one maps back to the thinking tools in Part I and translates them into a sequence of actions.
- [Launching a New Store](https://www.oddle.me/docs/guides/what-to-do/launching-a-new-store.md): The hype fades. What you build during the launch wave determines whether the business sustains after the novelty wears off.
- [Going Digital](https://www.oddle.me/docs/guides/what-to-do/going-digital.md): The real transition is not from analogue to digital. It is from invisible to visible.
- [Planning an Expansion](https://www.oddle.me/docs/guides/what-to-do/planning-an-expansion.md): Expansion is not doing what you already do, again. It is building a system that can do what you do, without you.
- [Revenue Has Flatlined](https://www.oddle.me/docs/guides/what-to-do/revenue-has-flatlined.md): Flat is not fine. A flatline hides two opposing forces that are exactly balanced — and one of them will win.
- [Platform Dependency](https://www.oddle.me/docs/guides/what-to-do/platform-dependency.md): The difference between renting your revenue and owning it. How to build a direct channel alongside marketplace dependency.


---

# 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/what-to-do.md?ask=<question>
```

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.